From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Lepiller Subject: bug#32316: Build failure with installed guix that does not happen with pre-inst-env Date: Tue, 31 Jul 2018 12:04:13 +0200 Message-ID: <20180731120413.35f65561@lepiller.eu> 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]:52816) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fkRWd-000147-Sy for bug-guix@gnu.org; Tue, 31 Jul 2018 06:05:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fkRWY-0003n5-V0 for bug-guix@gnu.org; Tue, 31 Jul 2018 06:05:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:58986) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fkRWY-0003n1-QP for bug-guix@gnu.org; Tue, 31 Jul 2018 06:05:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fkRWY-0005YG-C2 for bug-guix@gnu.org; Tue, 31 Jul 2018 06:05:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: 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: 32316@debbugs.gnu.org Le Tue, 31 Jul 2018 11:42:14 +0200, Konrad Hinsen a =C3=A9crit : > Hi Bj=C3=B6rn, >=20 > > thanks for the precise error report. =20 >=20 > Thanks for your quick reply! >=20 > > 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 =20 >=20 > 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. >=20 > 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? >=20 > 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. >=20 > Konrad. You're experiencing the change to the (not so) new guix pull. Now a complete guix is installed in ~/.config/guix/current. The guix installed in your profile doesn't look for packages in that directory, but uses its own definitions. This has a side-effect: whenever you try to update your profile, not only does your guix not use the newer guix, but the only guix package it knows of is a least 1 commit *before* your current guix, hence downgrading guix (and package definitions) at every update. Make sure you uninstall guix from your profile and add ~/.config/guix/current/bin to your PATH. Then you should be able to use the freshly pulled guix.