unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Diego Nicola Barbato <dnbarbato@posteo.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 33647@debbugs.gnu.org
Subject: bug#33647: First `guix pull' behaves unexpectedly
Date: Thu, 06 Dec 2018 18:03:04 +0100	[thread overview]
Message-ID: <87woomsi47.fsf@GlaDOS.home> (raw)
In-Reply-To: <87k1km3bn0.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 06 Dec 2018 16:42:11 +0100")

Hello Ricardo,

Thank you for the prompt reply.

Ricardo Wurmus <rekado@elephly.net> writes:

> Hi Diego,
>
>> 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.
>
> “guix pull” should have reminded you to add ~/.config/guix/current/bin
> to the front of your PATH environment variable.

I just checked the output and there was nothing after
“1 package in profile”, which is where the
“The following environment variable definitions may be needed:” lines
are usually printed.  If ‘guix pull’ is indeed supposed to print a
reminder this is probably the bug.

Greetings

Diego

  reply	other threads:[~2018-12-06 17:04 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 [this message]
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

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=87woomsi47.fsf@GlaDOS.home \
    --to=dnbarbato@posteo.de \
    --cc=33647@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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).