From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: bug#18534: problems with "guix pull" Date: Sun, 09 Nov 2014 22:38:44 +0100 Message-ID: <87ppcwrr4r.fsf@gnu.org> References: <84k34v2tdb.fsf@carleos.epv.uniovi.es> <87d2ammymo.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]:44512) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XnaCD-0002xm-9j for guix-devel@gnu.org; Sun, 09 Nov 2014 16:38:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XnaC8-0001pa-RP for guix-devel@gnu.org; Sun, 09 Nov 2014 16:38:53 -0500 Received: from hera.aquilenet.fr ([2a01:474::1]:51336) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XnaC8-0001pL-Ks for guix-devel@gnu.org; Sun, 09 Nov 2014 16:38:48 -0500 In-Reply-To: <87d2ammymo.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 23 Sep 2014 12:15:11 +0200") 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: Carlos Carleos , Igor Gajsin Cc: guix-devel@gnu.org, 18534-done@debbugs.gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) skribis: > The old =E2=80=98guix pull=E2=80=99 didn=E2=80=99t now about the gnu.scm = file, hence the error > (this was fixed in June, in commit 9d0b8fbd.) > > That means you have to actually run =E2=80=98guix pull=E2=80=99 from 0.7,= or from a > recent checkout. > > The fact that =E2=80=98guix pull=E2=80=99 can potentially break for some = future version > is unfortunate. It would be ideal if instead of using its own build > recipe, it would use one from the tarball. [...] > Igor Gajsin skribis: >=20 > > This is a output of `guix pull --verbose` > > > > compiling > > /gnu/store/akma9bmmjnizkv9sj1669wa8x4abrzyp-guix-latest/guix/import/pyp= i.scm'... > > ERROR: no code for module (json) >=20 > For now, this problem can be worked around as described here: >=20 > http://lists.gnu.org/archive/html/guix-devel/2014-09/msg00488.html This bug should be fixed by f81ac34. The idea is that the build recipe that is executed is now taken from the newly-downloaded Guix. Before that, we would use the build recipe from whatever Guix version was running, hence this kind of problems. Comments and testing welcome! Thanks, Ludo=E2=80=99.