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: Wed, 26 Oct 2022 21:58:21 +0200 [thread overview]
Message-ID: <86o7tybbmq.fsf@gmail.com> (raw)
In-Reply-To: <87eduule00.fsf@contorta>
Hi Vagrant,
On Wed, 26 Oct 2022 at 09:57, Vagrant Cascadian <vagrant@debian.org> wrote:
> It is consistently the same errors in the log, though on further looking
> i discovered a branch in ~/.cache/guix/checkouts/ that had old removed
> files in it (including wicd.scm/wicd.go) ... *maybe* that was somehow
> related. I did remove all the evidence, so so if stale checkouts is
> somehow the issue, it will be hard to reproduce again... oops.
Hum, what does “guix describe” say?
> I did manage again to use an old commit to pull up to a more recent
> master (a0751e3250dfea7e52468c8090e18c3118d93a60), and see there are new
> commits now so will try again. Will see.
What is your hackish workflow? You do,
guix pull --commit=<old> && guix pull
right? From your recent pull, does this
guix time-machine --commit=<new> -- help
work? where <new> is newer than your current revision.
Cheers,
simon
next prev parent reply other threads:[~2022-10-26 22:55 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 [this message]
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
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=86o7tybbmq.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).