unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Timothy Sample <samplet@ngyro.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 39771-done@debbugs.gnu.org
Subject: bug#39771: [core-updates] 'guix pull' and './pre-inst-env' produces different derivations
Date: Mon, 02 Mar 2020 18:11:56 -0500	[thread overview]
Message-ID: <87pnduwdvn.fsf@ngyro.com> (raw)
In-Reply-To: <87d09ujykb.fsf@devup.no> (Marius Bakke's message of "Mon, 02 Mar 2020 21:23:32 +0100")

Hi Marius,

Marius Bakke <mbakke@fastmail.com> writes:

> Marius Bakke <mbakke@fastmail.com> 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

  reply	other threads:[~2020-03-02 23:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24 21:33 bug#39771: [core-updates] 'guix pull' and './pre-inst-env' produces different derivations Marius Bakke
2020-03-02 18:14 ` Marius Bakke
2020-03-02 20:23   ` Marius Bakke
2020-03-02 23:11     ` Timothy Sample [this message]
2020-03-08 20: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=87pnduwdvn.fsf@ngyro.com \
    --to=samplet@ngyro.com \
    --cc=39771-done@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    /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).