From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#25775: Attempts to fix bootstrap Guile bug Date: Tue, 21 Feb 2017 13:03:27 -0500 Message-ID: <20170221180327.GA6953@jasmine> References: <87ino4ylhi.fsf@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50860) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cgEnG-000764-04 for bug-guix@gnu.org; Tue, 21 Feb 2017 13:04:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cgEnC-0000Md-Ro for bug-guix@gnu.org; Tue, 21 Feb 2017 13:04:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:50982) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cgEnC-0000MQ-KS for bug-guix@gnu.org; Tue, 21 Feb 2017 13:04:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cgEnC-0007HT-Cu for bug-guix@gnu.org; Tue, 21 Feb 2017 13:04:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87ino4ylhi.fsf@pobox.com> 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: Andy Wingo Cc: 25775@debbugs.gnu.org On Tue, Feb 21, 2017 at 09:52:09AM +0100, Andy Wingo wrote: > I think in the meantime it would be acceptable to insert an > > (unless guile > (error "update your guix daemon from git and restart it (#25775)")) > > to url-fetch/reset-patch-level, or something like that. WDYT? I think it would be better if users didn't have to set up a Guix development environment to work around this bug. My hunch is that the people who never updated root's packages and thus experienced the bug are the people who are least comfortable with such a solution. What about Ricardo's "really gross fix"? [0] I don't understand it enough to know why it's gross. If it works and does not break other things, at least it could protect people who have not yet hit the bug, but will hit it the next time they run `guix pull`. [0] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25775#35