bug#55521: ‘guix shell --export-manifest’ can yield incorrect results

bug#55521: ‘guix shell --export-manifest’ can yield incorrect results

[Ludovic Courtès]

‘guix shell --export-manifest’ behaves in a strange way:

--8<---------------cut here---------------start------------->8---
$ guix shell 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.

(specifications->manifest (list "rubber"))
$ guix shell texlive-base --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.

(specifications->manifest (list "texlive-base"))
$ 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
--8<---------------cut here---------------end--------------->8---

Something breaks when combining ‘rubber’ with other packages.

Ludo’.

bug#55521: ‘guix shell --export-manifest’ can yield incorrect results

[Ludovic Courtès]

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’.

bug#55521: ‘guix shell --export-manifest’ can yield incorrect results

[Dominic Martinez]

[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]


Ludovic Courtès <ludo@gnu.org> writes:

> Actually it looks like this was fixed in the meantime:
>
> $ 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"))
>
> I’m not sure what happened, but it’s a good surprise.  :-)
>
> Closing!

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"))

Maybe we could keep this bug open?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

bug#55521: ‘guix shell --export-manifest’ can yield incorrect results

[Ludovic Courtès]

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’.

bug#55521: ‘guix shell --export-manifest’ can yield incorrect results

[Ludovic Courtès]

Hi,

Ludovic Courtès <ludo@gnu.org> skribis:

> Uh, weird.  I do encounter it like this:
>
> $  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)

Turns out the problem occurs if the given environment has been cached by
a previous invocation (thanks to Marek Felšöci for putting me on the
right track!).

Fixed in 925a57c5d04553ff6c514867348e7d3c5c22ca66.

Ludo’.