Re: `guix package -u` upgrades packages to themselves

[Ludovic Courtès]

Hello,

Pierre Neidhardt  skribis:

> Sorry if I was confusing:  the output remains the same after upgrade.

There’s also one case that’s currently handled suboptimally: packages
with propagated inputs are systematically upgraded.  See
.

Clearly we should do better, probably by recursively checking whether
said propagated inputs would be upgraded.

Ludo’.

Re: `guix package -u` upgrades packages to themselves

[Pierre Neidhardt]

Chris Marusich  writes:

> I think this is a bug.  I've reported it here:
>
> https://bugs.gnu.org/31142

Thank you! :)

-- 
Pierre Neidhardt

A team effort is a lot of people doing what I say.
-- Michael Winner, British film director


signature.asc
Description: PGP signature

Re: `guix package -u` upgrades packages to themselves

[Chris Marusich]

Ricardo Wurmus  writes:

> Hi Chris,
>
>> Ricardo Wurmus  writes:
>>
>>> That’s because the package version itself is insufficient.  In Guix
>>> we’re dealing with package “variants”.
>>
>> Where is the concept of a package "variant" defined?  I briefly grepped
>> in the source but only found some ad-hoc stuff for Python and OCaml,
>> which actually do some kind of stuff with the package-properties.
>
> What I meant is that the version string alone is insufficient.  You can
> have multiple variants of a package with the same nominal version, but
> the differences are in the closure of the package.  When Guix is
> upgraded in between two invocations of “guix package -u” seeing the same
> “version” of a package to be upgraded to is a common occurrence.
>
>> How can the inputs have changed if Pierre is just running "guix package
>> -u" repeatedly?
>
> That bit of information was not available to me when I composed my
> initial response.  If Guix is not changed in between then this behaviour
> seems to be a bug.

I think this is a bug.  I've reported it here:

https://bugs.gnu.org/31142

-- 
Chris


signature.asc
Description: PGP signature

Re: `guix package -u` upgrades packages to themselves

[Ricardo Wurmus]

Hi Chris,

> Ricardo Wurmus  writes:
>
>> That’s because the package version itself is insufficient.  In Guix
>> we’re dealing with package “variants”.
>
> Where is the concept of a package "variant" defined?  I briefly grepped
> in the source but only found some ad-hoc stuff for Python and OCaml,
> which actually do some kind of stuff with the package-properties.

What I meant is that the version string alone is insufficient.  You can
have multiple variants of a package with the same nominal version, but
the differences are in the closure of the package.  When Guix is
upgraded in between two invocations of “guix package -u” seeing the same
“version” of a package to be upgraded to is a common occurrence.

> How can the inputs have changed if Pierre is just running "guix package
> -u" repeatedly?

That bit of information was not available to me when I composed my
initial response.  If Guix is not changed in between then this behaviour
seems to be a bug.

--
Ricardo

Re: `guix package -u` upgrades packages to themselves

[Chris Marusich]

Ricardo Wurmus  writes:

> That’s because the package version itself is insufficient.  In Guix
> we’re dealing with package “variants”.

Where is the concept of a package "variant" defined?  I briefly grepped
in the source but only found some ad-hoc stuff for Python and OCaml,
which actually do some kind of stuff with the package-properties.

> Guix will never upgrade a package to the same variant, but it can
> happen that there are different variants for the same version of a
> package.
>
> That’s usually because inputs to these packages have changed, which
> results in a new package output in the functional package management
> model.  The version stays the same, but since the inputs have changed,
> the output will be different and thus end up in a new directory.

How can the inputs have changed if Pierre is just running "guix package
-u" repeatedly?

-- 
Chris


signature.asc
Description: PGP signature

Re: `guix package -u` upgrades packages to themselves

[Martin Castillo]

On 11.04.2018 11:40, Pierre Neidhardt wrote:
>
> Sorry if I was confusing:  the output remains the same after upgrade.
>
> I can repeat the command indefinitely, it keep "upgrading" the same set
> of packages as per the output (but it does not actually do anything).
>

I see the same on 792ddfdc76147d494052fa93ecbfdbee7e72be68.


-- 
GPG: 7FDE 7190 2F73 2C50 236E  403D CC13 48F1 E644 08EC
[13:56:45]pi@pi:~/code/updapr$ guix package -u
guile: warning: failed to install locale
warning: failed to install locale: Invalid argument
The following package will be upgraded:
   guile2.2.3 -> 2.2.3  
/gnu/store/nb39n4ia25fdmzcfm628il1jqdkipf7s-guile-2.2.3

substitute: guile: warning: failed to install locale
substitute: warning: failed to install locale: Invalid argument
nothing to be done
[14:19:21]pi@pi:~/code/updapr$ ll ~/.guix-profile/bin/guile
lrwxrwxrwx 5 root root 65 Jan  1  1970 /home/pi/.guix-profile/bin/guile -> 
/gnu/store/nb39n4ia25fdmzcfm628il1jqdkipf7s-guile-2.2.3/bin/guile*
[14:20:29]pi@pi:~/code/updapr$ guix package -u
guile: warning: failed to install locale
warning: failed to install locale: Invalid argument
The following package will be upgraded:
   guile2.2.3 -> 2.2.3  
/gnu/store/nb39n4ia25fdmzcfm628il1jqdkipf7s-guile-2.2.3

substitute: guile: warning: failed to install locale
substitute: warning: failed to install locale: Invalid argument
nothing to be done
[14:21:18]pi@pi:~/code/updapr$ ll ~/.guix-profile/bin/guile
lrwxrwxrwx 5 root root 65 Jan  1  1970 /home/pi/.guix-profile/bin/guile -> 
/gnu/store/nb39n4ia25fdmzcfm628il1jqdkipf7s-guile-2.2.3/bin/guile*


signature.asc
Description: OpenPGP digital signature

Re: `guix package -u` upgrades packages to themselves

[Ricardo Wurmus]

Pierre Neidhardt  writes:

> I can run the following command as much as I want it will keep updating
> a bunch of packages to themselves.

That’s expected if you’ve upgraded Guix since installing the packages.
(If you haven’t then it’s probably a bug.)

That’s because the package version itself is insufficient.  In Guix
we’re dealing with package “variants”.  Guix will never upgrade a
package to the same variant, but it can happen that there are different
variants for the same version of a package.

That’s usually because inputs to these packages have changed, which
results in a new package output in the functional package management
model.  The version stays the same, but since the inputs have changed,
the output will be different and thus end up in a new directory.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net