all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Diego Nicola Barbato <dnbarbato@posteo.de>
Cc: 35601-done@debbugs.gnu.org
Subject: bug#35601: First 'guix pull' does not display 'hash guix' hint
Date: Thu, 09 May 2019 17:45:33 +0200	[thread overview]
Message-ID: <87ftpnd42q.fsf@gnu.org> (raw)
In-Reply-To: <87zhnzpwe0.fsf@GlaDOS.home> (Diego Nicola Barbato's message of "Mon, 06 May 2019 15:04:07 +0200")

Hi!

Diego Nicola Barbato <dnbarbato@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’.

      reply	other threads:[~2019-05-09 15:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06 13:04 bug#35601: First 'guix pull' does not display 'hash guix' hint Diego Nicola Barbato
2019-05-09 15:45 ` Ludovic Courtès [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ftpnd42q.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=35601-done@debbugs.gnu.org \
    --cc=dnbarbato@posteo.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.