bug#58927: closed (guix --version is 0)

[GNU bug Tracking System]

Your message dated Mon, 14 Nov 2022 12:33:06 +0100
with message-id <87mt8tpy8d.fsf@gnu.org>
and subject line Re: bug#56290: Guix is at version 0, according to "guix 
--version"
has caused the debbugs.gnu.org bug report #56290,
regarding guix --version is 0
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
56290: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56290
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> guix --version is 0
>
>
>
>
> Date: 
>
> Mon, 31 Oct 2022 14:30:47 +0100
>
>
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#56290: Guix is at version 0, according to "guix --version"
>
>
>
>
> Date: 
>
> Mon, 14 Nov 2022 12:33:06 +0100
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
>
>
>
>
> Hi,
>
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
> > I've hunted this down using 'guix time-machine' and it looks like the
> > first commit where the version string returns 0 is
> > 076e825dc5d585943ce820a279fffe4af09757fb. On that
> > commit 'guix time-machine --commit=076e... -- --version' returns 0 and
> > on the commit before that 5996aab354831d942b10253bc70217a4f2e6a247 we
> > get the commit as the version string.
> >
> > Looking at the commits I'm guessing that the 076e825d commit interacts
> > with the af57d1bf commit 2 before it, and whether the guile is guile-3.0
> > or guile-final or guile-3.0-latest.
>
> Fun!  Turns out this was caused by cross-module inlining: the initial
> config.scm generated in ‘compiled-guix’ does (define %guix-version "0"),
> and that got inlined in (guix ui).
>
> Fixed in 54003af85cc5b689bd328b30617c93ed2f5fd647!
>
> Ludo’.
>
>
> --- End Message ---