GNU bug report logs - #42298
Nonexistent Git commit referenced from current Guix package

Previous Next

Full log

Message #16 received at 42298 <at> debbugs.gnu.org (full text, mbox):

From: Marius Bakke <marius <at> gnu.org>
To: Ludovic Courtès <ludo <at> gnu.org>, Leo Famulari
 <leo <at> famulari.name>
Cc: Mathieu Othacehe <othacehe <at> gnu.org>, 42298 <at> debbugs.gnu.org
Subject: Re: bug#42298: Nonexistent Git commit referenced from current Guix
 package
Date: Sun, 12 Jul 2020 00:35:05 +0200

[Message part 1 (text/plain, inline)]

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

> Hi,
>
> Leo Famulari <leo <at> famulari.name> skribis:
>
>> The current Guix package points to a Git commit that does not exist,
>> which breaks the ability to build the package.
>>
>> The current package version is '1.1.0-16.d3eee3c'.
>>
>> That commit d3eee3c [0] is the commit that updated the Guix package
>> previously, to '1.1.0-15.03deb1e'.
>>
>> However, there is no commit 03deb1e [1].
>
> Yes, it was a mistake, and that’s why 1.1.0-16 was committed minutes
> later:
>
>   https://git.savannah.gnu.org/cgit/guix.git/commit/?id=b919d4048e72f8e5740606cdb3dac0592de21f36
>
> Someone who encounters this bug should run ‘guix pull’.

If you create an installer with todays Guix, 'guix system init' will
fail because it tries to build the broken 1.1.0-15.  Running 'guix pull'
inside the constrained installation environment is not a great solution,
particularly if substitutes are unavailable, so I created a new snapshot
in 6680880f9b8dceb4f2f3f91bd2b13c659b53835e.

(I had already encountered this today when reinstalling a machine.)

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.