From: zimoun <zimon.toutoune@gmail.com>
To: "Vagrant Cascadian" <vagrant@debian.org>,
"Ludovic Courtès" <ludo@gnu.org>, "Roel Janssen" <roel@gnu.org>
Cc: 47949@debbugs.gnu.org
Subject: bug#47949: Failed to produce output path for guix-package-cache
Date: Thu, 03 Nov 2022 09:48:21 +0100 [thread overview]
Message-ID: <861qqke84q.fsf@gmail.com> (raw)
In-Reply-To: <87sfj1ci97.fsf@contorta>
Hi Vagrant,
On Wed, 02 Nov 2022 at 11:40, Vagrant Cascadian <vagrant@debian.org> wrote:
>> I do not know if “git clean -dfx” would help because here the error is
>> probably between the repositories src/guix and src/guix-master and Guix
>> manages them under 2 unrelated directory checkouts.
>
> I had the impression that it uses git to copy the branches (rather than
> cp -r or something), otherwise the --branch=master argument would be
> meaningless (e.g. --branch=master does not mean whatever happens to be
> in the working directory), so I would assume the state of the local
> working directory wouldn't matter, only what's in the specified branch
> as git sees it.
From my understanding, this
guix pull --url=/home/vagrant/src/guix --branch=master
creates one directory under ~/.cache/guix/checkouts/ and then this,
guix pull --url=/home/vagrant/src/guix-master --branch=master
creates another directory under ~/.cache/guix/checkouts/ and these both
directory does not have the same name because their url is different.
IIUC, you were at generation 139 (using a clone of
/home/vagrant/src/guix living under say
~/.cache/guix/checkouts/maboosgggz6g6va54rikfxrsdsxhe363jri7g5dhcqb57odwklaa)
--8<---------------cut here---------------start------------->8---
# First version where I noticed failures:
Generation 139 Oct 22 2022 13:07:08
guix bb2701b
repository URL: /home/vagrant/src/guix
branch: master
commit: bb2701b9111a3d82a82ceaaf2b22b51ecd8ac21f
# Failed to pull from 139, successfully pulled from 138:
Generation 140 Oct 24 2022 13:19:21
guix 8663be6
repository URL: /home/vagrant/src/guix-master
branch: master
commit: 8663be6da7f13a8eeea71dc1f493f7adc5b7672a
--8<---------------cut here---------------end--------------->8---
and then you had difficulties, but note that “guix pull” generating 140
created another clone from /home/vagrant/src/guix-master living under
~/.cache/guix/checkouts/ie7tn3i564wpt5i2dqqm7ixzqfxwpp2ns6rqkyqn4z55d4kqujuq.
Generation 140 did not updated the checkout used by generation 139.
Somehow, the state of
~/.cache/guix/checkouts/maboosgggz6g6va54rikfxrsdsxhe363jri7g5dhcqb57odwklaa
and the state of
~/.cache/guix/checkouts/ie7tn3i564wpt5i2dqqm7ixzqfxwpp2ns6rqkyqn4z55d4kqujuq
require some compatibility, no?
Well, I have lost the topic of the initial bug report. :-)
BTW, I agree that “guix pull” and “guix time-machine” are requiring too
much resource (especially bandwidth) when we could imagine more resource
shares between various accounts and root. Well, I do no know if
guile-git provides the git-worktree feature. Or we could also imagine a
more automated workflow using only one local clone as you are doing.
Cheers,
simon
next prev parent reply other threads:[~2022-11-03 10:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 11:38 bug#47949: Failed to produce output path for guix-package-cache Roel Janssen
2021-04-28 21:38 ` Ludovic Courtès
2021-04-29 7:01 ` Roel Janssen
2021-04-29 7:56 ` Ludovic Courtès
2022-10-25 19:50 ` Vagrant Cascadian
2022-10-26 8:10 ` zimoun
2022-10-26 16:57 ` Vagrant Cascadian
2022-10-26 19:58 ` zimoun
2022-10-26 23:25 ` Vagrant Cascadian
2022-10-28 20:23 ` Vagrant Cascadian
2022-10-29 14:42 ` Maxime Devos
2022-11-02 11:02 ` zimoun
2022-11-02 18:40 ` Vagrant Cascadian
2022-11-03 8:48 ` zimoun [this message]
2022-11-03 18:35 ` Vagrant Cascadian
2023-04-28 16:47 ` Maxim Cournoyer
2023-04-28 17:41 ` Maxim Cournoyer
2023-05-03 16:44 ` Simon Tournier
2023-05-04 12:53 ` Maxim Cournoyer
2023-05-04 18:05 ` Simon Tournier
2023-05-05 14:23 ` Maxim Cournoyer
2023-05-03 19:25 ` Ludovic Courtès
2023-05-04 12:55 ` Maxim Cournoyer
2023-05-04 12:59 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=861qqke84q.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=47949@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=roel@gnu.org \
--cc=vagrant@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).