From mboxrd@z Thu Jan 1 00:00:00 1970 From: Diego Nicola Barbato Subject: bug#33647: First `guix pull' behaves unexpectedly Date: Wed, 19 Dec 2018 13:49:17 +0100 Message-ID: <87y38lu1f6.fsf@GlaDOS.home> References: <874lbqu2j3.fsf@GlaDOS.home> <87k1km3bn0.fsf@elephly.net> <871s6ugsrq.fsf@gnu.org> <87sgz9spgw.fsf@GlaDOS.home> <87r2eth3by.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60903) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gZbIf-0004ku-0b for bug-guix@gnu.org; Wed, 19 Dec 2018 07:50:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gZbIY-0002ZN-Ow for bug-guix@gnu.org; Wed, 19 Dec 2018 07:50:08 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:49781) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gZbIY-0002Z3-K8 for bug-guix@gnu.org; Wed, 19 Dec 2018 07:50:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gZbIY-0001mW-Ca for bug-guix@gnu.org; Wed, 19 Dec 2018 07:50:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87r2eth3by.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 07 Dec 2018 14:30:09 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 33647@debbugs.gnu.org Hello, Ludovic Court=C3=A8s writes: > Diego Nicola Barbato skribis: > >> Ludovic Court=C3=A8s 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=98gui= x=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 t= o 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? While I think it would be nice for Guix (or strictly speaking Bash) to just do what a noob like me would expect it to do in this situation, a hint would have certainly saved me some trouble. If it is unreasonably cumbersome to make Guix tell Bash to invalidate its cache upon completion of =E2=80=98guix pull=E2=80=99, I believe a hint would be good e= nough. Greetings, Diego