From: zimoun <zimon.toutoune@gmail.com>
To: "(" <paren@disroot.org>,
Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>,
help-guix <help-guix@gnu.org>
Subject: Re: Error starting a guix shell
Date: Thu, 21 Jul 2022 17:34:04 +0200 [thread overview]
Message-ID: <861que5vkj.fsf@gmail.com> (raw)
In-Reply-To: <CLJV0SOEL2C9.2OX706T8759OY@guix-aspire>
Hi,
On Tue, 19 Jul 2022 at 19:55, "(" <paren@disroot.org> wrote:
> Good ol' #56545 strikes again.
Well, #56545 is duplicated of #56441 already fixed. :-)
http://issues.guix.gnu.org/issue/56441
Indeed, using a Guix revision from the range:
4ff12d1de7cd617b791996ee7ca1240660b4c20e Fri Jul 1 23:29:16 2022 +0200
c9fbd40785a99e13a59d8e530830ce85220a9871 Fri Jul 8 23:58:11 2022 +0200
cannot work. It means that going from one commit to this range to one
commit before 4ff12d1de7cd617b791996ee7ca1240660b4c20e fails.
If you Guix pull, then it is fixed.
Else, run
guix time-machine --commit=c9fbd40785a99e13a59d8e530830ce85220a9871 \
-- time-machine -C channels.scm \
-- <command> [options]
where channels.scm is whatever you would like to go. :-)
“Just” 319 revisions are impacted by this bug.
--8<---------------cut here---------------start------------->8---
$ git log --oneline 4ff12d1de7cd617b791996ee7ca1240660b4c20e^..c9fbd40785a99e13a59d8e530830ce85220a9871 \
| wc -l
319
--8<---------------cut here---------------end--------------->8---
Cheers,
simon
prev parent reply other threads:[~2022-07-21 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 18:45 Error starting a guix shell Zelphir Kaltstahl
2022-07-19 18:55 ` (
2022-07-21 15:34 ` zimoun [this message]
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=861que5vkj.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=paren@disroot.org \
--cc=zelphirkaltstahl@posteo.de \
/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.
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).