From: "Ludovic Courtès" <ludo@gnu.org>
To: Dominic Martinez <dom@dominicm.dev>
Cc: 55521@debbugs.gnu.org
Subject: bug#55521: ‘guix shell --export-manifest’ can yield incorrect results
Date: Sat, 21 May 2022 18:33:56 +0200 [thread overview]
Message-ID: <87sfp2u9or.fsf@gnu.org> (raw)
In-Reply-To: <87v8u1d62n.fsf@dominicm.dev> (Dominic Martinez's message of "Thu, 19 May 2022 09:00:25 -0400")
Hi Dominic,
Dominic Martinez <dom@dominicm.dev> skribis:
> I think this issue is sporadic, rather than fixed. I've had it happen
> and then fix itself, even with the same list of packages on the same
> Guix commit. For instance, I don't encounter the issue with the commit
> you were on:
>
> $ guix time-machine --commit=6b588da368c77cde82ea2f22ca315116228777ad
> -- shell --export-manifest texlive-base rubber
> ;; What follows is a "manifest" equivalent to the command line you
> gave.
> ;; You can store it in a file that you may then pass to any 'guix'
> command
> ;; that accepts a '--manifest' (or '-m') option.
>
> (specifications->manifest
> (list "texlive-base" "rubber"))
Uh, weird. I do encounter it like this:
--8<---------------cut here---------------start------------->8---
$ guix time-machine --commit=6b588da368c77cde82ea2f22ca315116228777ad -- shell --export-manifest texlive-base rubber
;; What follows is a "manifest" equivalent to the command line you gave.
;; You can store it in a file that you may then pass to any 'guix' command
;; that accepts a '--manifest' (or '-m') option.
(concatenate-manifests)
--8<---------------cut here---------------end--------------->8---
> Maybe we could keep this bug open?
Yes, done. That’ll need some investigation…
Thanks for the heads-up!
Ludo’.
next prev parent reply other threads:[~2022-05-21 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 11:42 bug#55521: ‘guix shell --export-manifest’ can yield incorrect results Ludovic Courtès
2022-05-19 11:52 ` Ludovic Courtès
2022-05-19 13:00 ` Dominic Martinez
2022-05-21 16:33 ` Ludovic Courtès [this message]
2022-06-16 21:59 ` Ludovic Courtès
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=87sfp2u9or.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=55521@debbugs.gnu.org \
--cc=dom@dominicm.dev \
/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).