all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 30562@debbugs.gnu.org
Subject: bug#30562: "guix import pypi" fails now with "guix pulled" guix.
Date: Mon, 26 Feb 2018 16:13:31 +0100	[thread overview]
Message-ID: <87bmgbwzqc.fsf@gnu.org> (raw)
In-Reply-To: <20180221002726.0e855d65@scratchpost.org> (Danny Milosavljevic's message of "Wed, 21 Feb 2018 00:27:26 +0100")

Hi Danny,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> In guix/build/download.scm:
>     406:4  4 (open-connection-for-uri _ #:timeout _ # _)
>    407:14  3 (thunk)
>    342:14  2 (open-socket-for-uri #<<uri> scheme: https userinfo: #…> …)
>     321:4  1 (ensure-uri #<<uri> scheme: https userinfo: #f host: "p…>)
> In unknown file:
>            0 (_ #<<uri> scheme: https userinfo: #f host: "pypi.pytho…>)
>
> ERROR: ERROR: Wrong type to apply: #<syntax-transformer uri?>

The problem here has to do with an ABI change between Guile 2.2.2 and
2.2.3: in one case ‘uri?’ is a syntax, whereas in the other case it’s a
macro.

Normally ‘guix pull’ arranges to compile with a matching Guile version
for that reason: see commit 66f217b43aca603326dab17d4dda1a398bf4fb8c and
<https://bugs.gnu.org/29570>.

I’m not sure why this fix doesn’t work for you.  Is your ‘guix’ command
using 2.2.2 or 2.2.3?  Could it be that you ran ‘guix pull’ with 2.2.3
and then ran subsequent commands with 2.2.2?

Thanks,
Ludo’.

  parent reply	other threads:[~2018-02-26 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 23:27 bug#30562: "guix import pypi" fails now with "guix pulled" guix Danny Milosavljevic
2018-02-21  1:19 ` Marius Bakke
2018-02-21 11:03   ` Danny Milosavljevic
2018-02-26 15:13 ` Ludovic Courtès [this message]
2018-03-09 10:38   ` 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

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

  git send-email \
    --in-reply-to=87bmgbwzqc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=30562@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.