From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia@riseup.net Subject: bug#31907: New users get wrong/old profile path to guix after reconfiguring Date: Tue, 26 Jun 2018 04:06:01 -0700 Message-ID: <68c050778b26c874e04e2b34703cc363@riseup.net> References: <022CFE10-F1D7-4C39-BBFE-473F82165F47@riseup.net> <87sh5hp2e0.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57785) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fXloS-0001dS-4i for bug-guix@gnu.org; Tue, 26 Jun 2018 07:07:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fXloN-0002Im-Hm for bug-guix@gnu.org; Tue, 26 Jun 2018 07:07:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:56011) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fXloN-0002IU-DU for bug-guix@gnu.org; Tue, 26 Jun 2018 07:07:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fXloL-0001fn-Mh for bug-guix@gnu.org; Tue, 26 Jun 2018 07:07:03 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87sh5hp2e0.fsf@gnu.org> 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: ludo@gnu.org Cc: 31907@debbugs.gnu.org On 2018-06-20 23:35, ludo@gnu.org wrote: > Hello swedebugia, ..snip > ~/.config/guix/current is created by the new ‘guix pull’. So when > coming from 0.14, you actually need to run it twice: the first run will > give you the new ‘guix pull’, and the second run will actually run the > new code and create ~/.config/guix/current. I understand. This is not the problem. I wrote yesterday on #guix: hi guix I wonder if any of "pull" or "system reconfigure" update the guix in the system profile? My system profile in sdb1@antelope ~$ ls -l /run/current-system/profile/bin/guix lrwxrwxrwx 2 root root 75 1 jan 1970 /run/current-system/profile/bin/guix -> /gnu/store/avg3vnk6p752z8iwld6yzv1wg7ki48vp-guix-0.14.0-13.7af5c2a/bin/guix even though I have pulled and reconfigured multiple times: as root root@antelope /home/sdb1# guix pull -l Generation 1 jun 18 2018 19:26:00 guix b4eae99 repository URL: https://git.savannah.gnu.org/git/guix.git commit: b4eae997fe5b928f179c34d281e9f2c3eccd3670 Generation 2 jun 22 2018 20:48:03 (current) guix 8edebd3 repository URL: https://git.savannah.gnu.org/git/guix.git commit: 8edebd3207335aff15081458e895104ac9f45d3d You could ask: why care about the guix version in the system profile at all? It is not used as soon as you run guix pull or populated the .config/guix some other way and adjusted the this to preceede in the PATH. I care because if I create a new user via config.scm they by default get access to an outdated guix when a newer is available. This is in my view a bug. Maybe its me who do not fully understand how system profiles is supposed to work. I tried looking into the source but it was not clear to me how it is supposed to work together. The manual does not mention when/how the system profile gets updated. I supposed it happens when a new profile derivation is built during reconfigure. Maybe this is not correct. Maybe guix is supposed to be in the system profile after all (I dont specify it in my config.scm ATM and none of the templates do either) Cheers sdb