unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Michael Bowcutt <mwb71@case.edu>
Cc: 32929@debbugs.gnu.org
Subject: bug#32929: `guix pull` fail
Date: Wed, 10 Oct 2018 15:01:14 +0200	[thread overview]
Message-ID: <87va6a7y79.fsf@gnu.org> (raw)
In-Reply-To: <1bfe554e7bd3e7415d821b694106fb81948c0dd0.camel@case.edu> (Michael Bowcutt's message of "Mon, 08 Oct 2018 17:58:07 -0400")

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?

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.  :-)

Thanks,
Ludo’.

  reply	other threads:[~2018-10-10 13:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04  3:54 bug#32929: `guix pull` fail Michael Bowcutt
2018-10-08 20:47 ` Ludovic Courtès
2018-10-08 21:58   ` Michael Bowcutt
2018-10-10 13:01     ` Ludovic Courtès [this message]
2018-10-10 20:15       ` Michael Bowcutt
2018-10-10 20:47         ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87va6a7y79.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=32929@debbugs.gnu.org \
    --cc=mwb71@case.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).