From mboxrd@z Thu Jan 1 00:00:00 1970 From: taylanbayirli@gmail.com (Taylan Ulrich =?utf-8?Q?Bay=C4=B1rl=C4=B1?= =?utf-8?Q?=2FKammer?=) Subject: Outdated config.scm in development repo Date: Tue, 13 Oct 2015 20:08:39 +0200 Message-ID: <871tcy63q0.fsf@T420.taylan> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48394) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zm40E-0006k9-2G for guix-devel@gnu.org; Tue, 13 Oct 2015 14:08:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zm40A-000401-17 for guix-devel@gnu.org; Tue, 13 Oct 2015 14:08:46 -0400 Received: from mail-wi0-x22f.google.com ([2a00:1450:400c:c05::22f]:37861) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zm409-0003zT-R4 for guix-devel@gnu.org; Tue, 13 Oct 2015 14:08:41 -0400 Received: by wijq8 with SMTP id q8so44082738wij.0 for ; Tue, 13 Oct 2015 11:08:41 -0700 (PDT) Received: from T420.taylan ([2a02:908:c32:4740:221:ccff:fe66:68f0]) by smtp.gmail.com with ESMTPSA id h7sm5090706wjz.7.2015.10.13.11.08.39 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Oct 2015 11:08:40 -0700 (PDT) List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: guix-devel@gnu.org >From what I can tell this situation I landed in doesn't involve any bugs and won't happen to a normal user, but for the sake of documenting it for developers, here goes: I have $XDG_CONFIG_HOME/guix/latest point to a git repository so I can update it swiftly. In the repo, a ./guix/config.scm is generated from ./guix/config.scm.in sometimes, I guess on ./configure; I haven't tried to figure out exactly when but certainly not every time I run 'make'. That config.scm will contain absolute paths to gzip, bzip2, and some other things. If you used a Guix environment to build, those will be /gnu/store/... paths. When you update things and garbage-collect, those store items might get removed, since $XDG_CONFIG_HOME/guix/latest/guix/config.scm is not a GC root (rightly so, as far as I understand). And thus, guix commands will start failing, saying they can't find /gnu/store/.../bin/bzip2 or whatever. That sums up the problem description. Fixing it might be tricky if you need to use 'guix environment' to run ./configure or whatever to fix the config.scm, since you possibly first need to fix the issue to be able to use 'guix environment' (it will work only if no calls are made to the missing /gnu/store/... executables). Manually fixing the config.scm is easy, fortunately. Just change the absolute /gnu/store/... paths which point at non-existing store items to point to existing store items. Taylan