[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#39771: closed ([core-updates] 'guix pull' and './pre-inst-env' produ

From: GNU bug Tracking System
Subject: bug#39771: closed ([core-updates] 'guix pull' and './pre-inst-env' produces different derivations)
Date: Mon, 02 Mar 2020 23:13:02 +0000

Your message dated Mon, 02 Mar 2020 18:11:56 -0500
with message-id <address@hidden>
and subject line Re: [core-updates] 'guix pull' and './pre-inst-env' produces 
different derivations
has caused the debbugs.gnu.org bug report #39771,
regarding [core-updates] 'guix pull' and './pre-inst-env' produces different 
to be marked as done.

(If you believe you have received this mail in error, please contact

39771: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=39771
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: [core-updates] 'guix pull' and './pre-inst-env' produces different derivations Date: Mon, 24 Feb 2020 22:33:08 +0100

There is a strange bug on the core-updates branch: if you 'guix pull
--branch=core-updates', everything from around 'guile-bootstrap@2.0' in
the package graph will have different derivations from what you get in
the git checkout:

On my local fork of core-updates:

./pre-inst-env guix build -d bash

After 'guix pull -p /tmp/core-updates --url=/my/checkout
--branch=core-updates', on the same commit:

/tmp/core-updates/bin/guix build -d bash

I believe this is a recent regression (probably the wip-bootstrap
changes?), as I've pulled (and reconfigured) on the branch before.

Any idea what is going on here?

Attachment: signature.asc
Description: PGP signature

--- End Message ---
--- Begin Message --- Subject: Re: [core-updates] 'guix pull' and './pre-inst-env' produces different derivations Date: Mon, 02 Mar 2020 18:11:56 -0500 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
Hi Marius,

Marius Bakke <address@hidden> writes:

> Marius Bakke <address@hidden> writes:
>> I've tracked this down to 'gash-boot'.  Namely the use of ,(version): it
>> evaluates to '2.2.6' when run with ./pre-inst-env and "3.0.0" after
>> 'guix pull'.
>> I suspect both are wrong, and that it really intends to use the version
>> of gash here.  Timothy, can you confirm?

Definitely wrong!  I think I had somehow convinced myself that the
version of Gash was available when inheriting but delayed via a thunk.
The fact that it happily returns the current Guile version means that I
never noticed how wrong I was.  Sorry!

>> Currently trying to 'guix pull' with a hard coded "2.2.6" version to
>> see if other instances need changing.
> This patch solves the problem without triggering a full rebuild:
> [...]
> I have another full-rebuild commit in the pipeline (bzip2 currently
> keeps a reference to the Mes toolchain), so we might as well fix it
> properly.
> Waiting for confirmation from Timothy as to what the proper fix is,
> though.

It should be using “package-version” to get the versions from the parent
packages.  Fixed in 0b870f7915f5da43758753fd088a22033936dc50.

-- Tim

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]