From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Hinsen Subject: bug#32316: Build failure with installed guix that does not happen with pre-inst-env Date: Tue, 31 Jul 2018 11:42:14 +0200 Message-ID: References: <20180730214222.4c08be42@alma-ubu> 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]:49179) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fkRBL-0001Ml-D7 for bug-guix@gnu.org; Tue, 31 Jul 2018 05:43:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fkRBI-0002au-Am for bug-guix@gnu.org; Tue, 31 Jul 2018 05:43:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:58970) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fkRBI-0002aP-2p for bug-guix@gnu.org; Tue, 31 Jul 2018 05:43:04 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fkRBG-0004xt-5D for bug-guix@gnu.org; Tue, 31 Jul 2018 05:43:03 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20180730214222.4c08be42@alma-ubu> 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: =?UTF-8?Q?Bj=C3=B6rn_?= =?UTF-8?Q?H=C3=B6fling?= Cc: 32316@debbugs.gnu.org Hi Bj=C3=B6rn, > thanks for the precise error report. Thanks for your quick reply! > Could it be the case that in your `guix build ...` you are not using > the guix you pulled? > > What does `guix --version` say? > > Where does `which guix` point to? > > It should point to > > ~/.config/guix/current/bin/guix It points to $HOME/.guix-profile/bin/guix, and since I have the package "guix" installed in my profile, that looks OK to me. At the very least I am used to it: guix has always been in my profile, and has always worked well that way. But I do see how this could cause various failures after a guix pull, because the guix in my profile has to work with the updated stuff the pull has placed under ~/.config. So perhaps the real mystery is that I haven't had any trouble before. And I wonder what strategy to adopt to avoid it - remove guix from my profile? There was a good reason to install it last year, but I don't remember what it was. If installing guix into a profile is not a good idea, perhaps the guix package should disappear or be renamed to something that indicates its true purpose? BTW, since I updated my profile with the pre-inst-env guix, I now also have a new guix in my profile and the build failure has disappeared. Konrad.