From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#17150: Stale bootstrap/*/guile-2.0.9.tar.xz files are not detected Date: Mon, 31 Mar 2014 18:51:22 -0400 Message-ID: <87lhvqm179.fsf@yeeloong.lan> References: <8761munpip.fsf@yeeloong.lan> <8761mu57ui.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]:43145) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WUl4m-0005YK-4Y for bug-guix@gnu.org; Mon, 31 Mar 2014 18:53:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WUl4g-0003Wv-QM for bug-guix@gnu.org; Mon, 31 Mar 2014 18:53:08 -0400 Received: from debbugs.gnu.org ([140.186.70.43]:57259) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WUl4g-0003Wp-Ml for bug-guix@gnu.org; Mon, 31 Mar 2014 18:53:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1WUl4g-0002t9-3e for bug-guix@gnu.org; Mon, 31 Mar 2014 18:53:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <8761mu57ui.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 01 Apr 2014 00:19:49 +0200") 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-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 17150@debbugs.gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Mark H Weaver skribis: > >> I just realized that my x86_64 and Loongson 3A systems have spent an >> enormous amount of time building the new guix master branch based on >> outdated bootstrap/*/guile-2.0.9.tar.xz. >> >> The issue is that if you simply "git pull" from a build directory with >> older versions of bootstrap/*/guile-2.0.9.tar.xz, although the various >> places where the hashes are stored are updated, those new hashes are >> never checked against the existing files. Therefore, you can proceed to >> build an entire system based on an outdated bootstrap guile, and with >> hashes that don't match what's on hydra and what other people are >> building. > > Right, =E2=80=98guix pull=E2=80=99 doesn=E2=80=99t survive updates of the= bootstrap Guile > tarballs, because it doesn=E2=80=99t try to download it (see =E2=80=98bui= ld-guix=E2=80=99 in > guix/build/pull.scm.) That=E2=80=99s rare in practice, but still a serio= us > limitation as you note. :-/ Hmm, yes, I suppose that "guix pull" is more relevant for typical users, but actually that's not what I was talking about above. I was talking about "git pull" followed by "make". > There are other things to do in =E2=80=98guix pull=E2=80=99, such as auth= entication, and > improved bandwidth usage. For the latter an option would be to resort > to git, and perhaps for the former too. Yes, it seems to me that git is a good tool for this job. Mark