[Top][All Lists]

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

[debbugs-tracker] bug#33647: closed (First `guix pull' behaves unexpecte

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#33647: closed (First `guix pull' behaves unexpectedly)
Date: Fri, 07 Dec 2018 09:42:01 +0000

Your message dated Fri, 7 Dec 2018 10:41:36 +0100
with message-id <address@hidden>
and subject line Re: bug#33647: First `guix pull' behaves unexpectedly
has caused the debbugs.gnu.org bug report #33647,
regarding First `guix pull' behaves unexpectedly
to be marked as done.

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

33647: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=33647
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: First `guix pull' behaves unexpectedly Date: Thu, 06 Dec 2018 15:56:48 +0100
Hello Guix,

The first time a user runs ‘guix pull’ after a fresh install it does not
seem to update guix.  ‘guix --version’ reports that guix is still
version 0.15.0 after running ‘guix pull’, instead of showing the hash of
the latest commit.
This can be mitigated by logging out and back in, after which
‘guix --version’ returns the expected version.



--- End Message ---
--- Begin Message --- Subject: Re: bug#33647: First `guix pull' behaves unexpectedly Date: Fri, 7 Dec 2018 10:41:36 +0100
On Fri, 07 Dec 2018 09:36:31 +0100
Diego Nicola Barbato <address@hidden> wrote:

> I believe this is it.  This also explains why ‘which guix’ returned
> the updated guix while ‘guix --version’ claimed it was still the older
> version, which I found rather confusing.
> I am afraid being unaware of this has led me to inadvertently
> downgrade GuixSD whenever I reconfigured for the first time after a
> fresh install.

OK, then I'm closing this issue.


Attachment: pgpjKqx5lQZJg.pgp
Description: OpenPGP digital signature

--- End Message ---

reply via email to

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