From: Maxime Devos <maximedevos@telenet.be>
To: "Vagrant Cascadian" <vagrant@debian.org>,
zimoun <zimon.toutoune@gmail.com>,
"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: Sat, 29 Oct 2022 16:42:25 +0200 [thread overview]
Message-ID: <c4d12e61-a64f-0baf-f9e4-9e092de65165@telenet.be> (raw)
In-Reply-To: <87zgdfd7ee.fsf@contorta>
[-- Attachment #1.1.1: Type: text/plain, Size: 772 bytes --]
On 28-10-2022 22:23, Vagrant Cascadian wrote:
>[...]
>> Maybe that's a clue pointing to the crufty .cache directories?
>
> Well, after removing ~/.cache/guix/checkouts/ I haven't had the problem
> again, with several successful pulls.
>
> This suggests to me that guix should make sure to not use a dirty
> checkout to prevent this in the future ... either exporting the guix
> tree it's working with to a temporary location, or something like
> running "git clean -dfx" before using the checkout...
>
A (similar) problem was reported previously but I couldn't find it
anymore. A proposed solution was to use temporary git worktrees ("git
clean -dfx" wouldn't be sufficient in context of concurrent "guix
time-machine").
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-10-29 14:43 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 [this message]
2022-11-02 11:02 ` zimoun
2022-11-02 18:40 ` Vagrant Cascadian
2022-11-03 8:48 ` zimoun
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=c4d12e61-a64f-0baf-f9e4-9e092de65165@telenet.be \
--to=maximedevos@telenet.be \
--cc=47949@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=roel@gnu.org \
--cc=vagrant@debian.org \
--cc=zimon.toutoune@gmail.com \
/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).