From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Bowcutt <mwb71@case.edu>
Subject: bug#32929: `guix pull` fail
Date: Wed, 10 Oct 2018 16:15:57 -0400
Message-ID: <2ed3e2703403ff085a3d3fa6a4e173439269bbb8.camel@case.edu>
References: <8366805ea63466ea6bbdcf42ea89cbb1cac75231.camel@case.edu>
	<87y3b8upwu.fsf@gnu.org>
	<1bfe554e7bd3e7415d821b694106fb81948c0dd0.camel@case.edu>
	<87va6a7y79.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42168)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gALOs-00020a-Lc
	for bug-guix@gnu.org; Wed, 10 Oct 2018 16:48:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gALOn-0001pI-Jb
	for bug-guix@gnu.org; Wed, 10 Oct 2018 16:48:09 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:39649)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1gALOj-0001fU-R1
	for bug-guix@gnu.org; Wed, 10 Oct 2018 16:48:03 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gALOj-0003Ay-KO
	for bug-guix@gnu.org; Wed, 10 Oct 2018 16:48:01 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.32929.B32929.153920443212134@debbugs.gnu.org>
Resent-To: 32929@debbugs.gnu.org
Resent-Message-ID: <87o9c18r7j.fsf@gnu.org>
In-Reply-To: <87va6a7y79.fsf@gnu.org>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>

Thanks, Ludo

On Wed, 2018-10-10 at 15:01 +0200, Ludovic Courtès wrote:
> Hi Michael,
> 
> Michael Bowcutt <mwb71@case.edu> skribis:
> 
> > On Mon, 2018-10-08 at 22:47 +0200, Ludovic Courtès wrote:
> > > Thanks for your report.  I pulled v0.15.0 and from there tried to
> > > pull
> > > the above commit, but I couldn’t reproduce the bug above.
> > > 
> > > Does it still occur for you?
> > 
> > Yes, I'm still getting this error, although with different program
> > and
> > guix version hashes which frequently change.
> > 
> > > How did you install Guix?  It seems to be running on Guile 2.0
> > > (not
> > > 2.2), can you confirm?
> > 
> > I installed via the Fedora 28 COPR at 
> > https://copr.fedorainfracloud.org/coprs/lantw44/guix/. I'm 90% sure
> > I'm
> > running Guile 2.0, even though I have both 2.0 and 2.2 installed
> > via
> > dnf.
> 
> I see.  I believe commit 099bb0175f681e5f68dafb8ad973866f31fe515c
> fixes
> the problem.  With this commit, running ‘guix pull’ will always give
> you, under ~/.config/guix/current, a new Guix running on Guile 2.2.
> 
> Could you try running ‘guix pull’ and see if it works now?

I can confirm that I'm no longer running into this issue, `guix pull`
finished successfully!

> Besides, I’d like to drop Guile 2.0 support soon, so if you could
> tell
> the COPR packagers to switch to Guile 2.2, that’d be great.  :-)

I'll report that upstream. Thanks!

-Michael