From: Jan Nieuwenhuizen <janneke@gnu.org>
To: ludo@gnu.org
Cc: 41457@debbugs.gnu.org
Subject: bug#41457: guix pull: channel d8feee9 - extraneous field initializers (sha256)
Date: Fri, 22 May 2020 20:49:18 +0200 [thread overview]
Message-ID: <87a71zx0sx.fsf@gnu.org> (raw)
In-Reply-To: <878shjalwr.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 22 May 2020 20:01:56 +0200")
Ludovic Courtès writes:
Hello,
> Good news, this is fixed by 50ea3135e0948a042cd3b899e970f6ade291a0c2!
>
> As noted in the commit log, this issue stemmed from a change in
> #:autoload semantics in Guile 3.0. In 3.0, the line:
>
> #:autoload (gcrypt hash) (port-sha256)
>
> means that only ‘port-sha256’ is imported. Conversely, in 2.2 (which is
> the Guile version used by the ‘compute-guix-derivation’ program above),
> that #:autoload line means that all the (gcrypt hash) bindings are
> imported. That includes the ‘sha256’ bindings, which would thus prevent
> matching the ‘sha256’ literal in the ‘origin-compatibility-helper’
> macro. Terrible!
Huh? I just used #:autoload for the first time (in the native
qemu-image patch thaw way may not be using after all ...) and so I just
read the documentation.
]I am pretty sure that t]The 3.0 documentation says that "when a module
is autoloaded, all symbols become available"?
http://git.savannah.gnu.org/cgit/guile.git/tree/doc/ref/api-modules.texi#n298
So...what's going on here?
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2020-05-22 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 10:14 bug#41457: guix pull: channel d8feee9 - extraneous field initializers (sha256) Matias Jose Seco Baccanelli
2020-05-22 14:49 ` Ricardo Wurmus
2020-05-22 15:12 ` Ludovic Courtès
2020-05-22 18:01 ` Ludovic Courtès
2020-05-22 18:49 ` Jan Nieuwenhuizen [this message]
2020-05-22 20:13 ` 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=87a71zx0sx.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=41457@debbugs.gnu.org \
--cc=ludo@gnu.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.