unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Diego Nicola Barbato <dnbarbato@posteo.de>
Cc: 33647@debbugs.gnu.org
Subject: bug#33647: First `guix pull' behaves unexpectedly
Date: Wed, 23 Jan 2019 10:51:01 +0100	[thread overview]
Message-ID: <87va2fhfcq.fsf@gnu.org> (raw)
In-Reply-To: <877eewxs6v.fsf@GlaDOS.home> (Diego Nicola Barbato's message of "Tue, 22 Jan 2019 23:07:04 +0100")

Hi Diego,

Diego Nicola Barbato <dnbarbato@posteo.de> skribis:

>> Thanks for the heads-up.  Commit
>> 3bbd6919bd84b76686d1aa626ba861faf3fc8ceb changes ‘guix pull’ to display
>> a hint in this case.
>>
>> Ludo’.
>
> I just tried to check if this worked.  I installed GuixSD in a VM (with
> the 0.16.0 installer), rebooted, and ran ‘guix pull’
> (commit d1dfcc7c1b38d816dddc2868917ba490db7e7c3b).  It did not print any
> hint (I have attached the bash session).
> Will this change only take effect once the installer is updated?

Yes, since the change is in ‘guix pull’ itself, the 0.16.0 ‘guix pull’
won’t display the message.  So you’d have to run the ‘guix pull’ you
just obtained from ‘guix pull’ (ah!) to see the message.

HTH,
Ludo’.

      reply	other threads:[~2019-01-23  9:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 14:56 bug#33647: First `guix pull' behaves unexpectedly Diego Nicola Barbato
2018-12-06 15:42 ` Ricardo Wurmus
2018-12-06 17:03   ` Diego Nicola Barbato
2018-12-06 23:06   ` Ludovic Courtès
2018-12-07  8:36     ` Diego Nicola Barbato
2018-12-07  9:41       ` Björn Höfling
2018-12-07 13:30       ` Ludovic Courtès
2018-12-19 12:49         ` Diego Nicola Barbato
2018-12-19 17:37           ` swedebugia
2018-12-19 19:27             ` Tobias Geerinckx-Rice
2018-12-20  5:24               ` swedebugia
2019-01-18 16:54           ` Ludovic Courtès
2019-01-22 22:07             ` Diego Nicola Barbato
2019-01-23  9:51               ` 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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87va2fhfcq.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=33647@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).