From: "Ludovic Courtès" <ludo@gnu.org>
To: 55521@debbugs.gnu.org
Subject: bug#55521: ‘guix shell --export-manifest’ can yield incorrect results
Date: Thu, 19 May 2022 13:52:03 +0200 [thread overview]
Message-ID: <87wnehzqn0.fsf@gnu.org> (raw)
In-Reply-To: <871qwp21fp.fsf@inria.fr> ("Ludovic Courtès"'s message of "Thu, 19 May 2022 13:42:50 +0200")
Ludovic Courtès <ludovic.courtes@inria.fr> skribis:
> $ guix shell texlive-base rubber --export-manifest
> ;; 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)
> $ guix describe
> Generation 214 May 02 2022 21:44:14 (current)
> guix 6b588da
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: 6b588da368c77cde82ea2f22ca315116228777ad
Actually it looks like this was fixed in the meantime:
--8<---------------cut here---------------start------------->8---
$ guix time-machine --commit=2f170893719e6e9fc8e19cc5f0568e20a95d92b4 -- 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"))
--8<---------------cut here---------------end--------------->8---
I’m not sure what happened, but it’s a good surprise. :-)
Closing!
Ludo’.
next prev parent reply other threads:[~2022-05-19 11:56 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 [this message]
2022-05-19 13:00 ` Dominic Martinez
2022-05-21 16:33 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnehzqn0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=55521@debbugs.gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.