GNU bug report logs -
#35601
First 'guix pull' does not display 'hash guix' hint
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 35601 in the body.
You can then email your comments to 35601 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#35601
; Package
guix
.
(Mon, 06 May 2019 13:05:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Diego Nicola Barbato <dnbarbato <at> posteo.de>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Mon, 06 May 2019 13:05:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi Guix,
Congratulations on 1.0.0!
I took the opportunity to revisit bug #33647 [0] and verify that commits
3bbd691 and d1d7283 have the desired effect. Unfortunately they do
not: The first time a user runs guix pull on a freshly installed Guix
System no hint about running 'hash guix' is displayed even though it is
precisely when the hint was supposed to be displayed.
To reproduce simply run (after installing Guix System using the 1.0.0
installer) 'guix --version', which will yield 'guix (GNU Guix) 1.0.0',
then 'guix pull', which will display no hint about running 'hash guix',
then 'guix --version' again, which will return 'guix (GNU Guix) 1.0.0'
again, and finally 'hash guix' followed by 'guix --version', which now
will yield 'guix (GNU Guix) 1234somecommithash123456789abcdefghijklm'.
Regardless of the hint I still believe it is unfortunate that running
'guix pull && guix system reconfigure /etc/config.scm' for the first
time will rather counterintuitively downgrade the system instead of
upgrading it.
Regards,
Diego
[0]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33647
Severity set to 'important' from 'normal'
Request was from
Ludovic Courtès <ludo <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Thu, 09 May 2019 10:16:02 GMT)
Full text and
rfc822 format available.
Reply sent
to
Ludovic Courtès <ludo <at> gnu.org>
:
You have taken responsibility.
(Thu, 09 May 2019 15:46:05 GMT)
Full text and
rfc822 format available.
Notification sent
to
Diego Nicola Barbato <dnbarbato <at> posteo.de>
:
bug acknowledged by developer.
(Thu, 09 May 2019 15:46:06 GMT)
Full text and
rfc822 format available.
Message #12 received at 35601-done <at> debbugs.gnu.org (full text, mbox):
Hi!
Diego Nicola Barbato <dnbarbato <at> posteo.de> skribis:
> To reproduce simply run (after installing Guix System using the 1.0.0
> installer) 'guix --version', which will yield 'guix (GNU Guix) 1.0.0',
> then 'guix pull', which will display no hint about running 'hash guix',
> then 'guix --version' again, which will return 'guix (GNU Guix) 1.0.0'
> again, and finally 'hash guix' followed by 'guix --version', which now
> will yield 'guix (GNU Guix) 1234somecommithash123456789abcdefghijklm'.
I *think* this is fixed for good by
a0dc97a517cbc4c82640e30cacb2a564d128bbe9.
> Regardless of the hint I still believe it is unfortunate that running
> 'guix pull && guix system reconfigure /etc/config.scm' for the first
> time will rather counterintuitively downgrade the system instead of
> upgrading it.
I agree. Perhaps an option would be to somehow pre-populate
~/.config/guix/current for all users on Guix System, but I’m not quite
sure how to do that intelligently.
Thoughts?
Thanks,
Ludo’.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 07 Jun 2019 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 297 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.