From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Subject: bug#33647: First `guix pull' behaves unexpectedly
Date: Fri, 07 Dec 2018 14:30:09 +0100
Message-ID: <87r2eth3by.fsf@gnu.org>
References: <874lbqu2j3.fsf@GlaDOS.home> <87k1km3bn0.fsf@elephly.net>
	<871s6ugsrq.fsf@gnu.org> <87sgz9spgw.fsf@GlaDOS.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53713)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gVGDx-0007zt-7p
	for bug-guix@gnu.org; Fri, 07 Dec 2018 08:31:26 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gVGDk-0001da-En
	for bug-guix@gnu.org; Fri, 07 Dec 2018 08:31:18 -0500
Received: from debbugs.gnu.org ([208.118.235.43]:60353)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1gVGDg-0001SD-2f
	for bug-guix@gnu.org; Fri, 07 Dec 2018 08:31:06 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gVGDe-0002lo-Fh
	for bug-guix@gnu.org; Fri, 07 Dec 2018 08:31:03 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.33647.B33647.154418942510588@debbugs.gnu.org>
In-Reply-To: <87sgz9spgw.fsf@GlaDOS.home> (Diego Nicola Barbato's message of
	"Fri, 07 Dec 2018 09:36:31 +0100")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Diego Nicola Barbato <dnbarbato@posteo.de>
Cc: 33647@debbugs.gnu.org

Hi,

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

> Ludovic Court=C3=A8s <ludo@gnu.org> writes:

[...]

>> In addition, be aware that Bash maintains a cache of commands it looked
>> up in $PATH.  Thus it may be that, say, it had cached that =E2=80=98guix=
=E2=80=99 is
>> really /run/current-system/profile/bin/guix.  When you pulled, it didn=
=E2=80=99t
>> invalidate its cache thus you kept using that old version.
>>
>> The solution is to run =E2=80=9Chash guix=E2=80=9D at the Bash prompt to=
 force cache
>> invalidation (info "(bash) Bourne Shell Builtins").
>
> I believe this is it.  This also explains why =E2=80=98which guix=E2=80=
=99 returned the
> updated guix while =E2=80=98guix --version=E2=80=99 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.

Yeah.  This is not strictly speaking a Guix bug, but clearly it=E2=80=99s a
common pitfall.  Perhaps we should print a hint upon completion?

Ludo=E2=80=99.