From: Maxime Devos <maximedevos@telenet.be>
To: 53496@debbugs.gnu.org
Cc: Peter Kois <kangus@gmail.com>
Subject: bug#53496: guix pull from 1.1.0 --> 29091731a0c6cb649cdfd72297575fe2bb2a9591 fails
Date: Sat, 19 Mar 2022 23:33:30 +0100 [thread overview]
Message-ID: <63a594ce58660df56b8a9437f4be00e438ceb295.camel@telenet.be> (raw)
In-Reply-To: <0d089b384be80e404ade7f9cf1647432aa1877f1.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 759 bytes --]
Maxime Devos schreef op za 19-03-2022 om 23:28 [+0100]:
> The only use of 'module-re-export!' in current Guix is
>
> (module-re-export! (current-module) '(delete) #:replace? #t)
>
> from (guix packages).
>
> Probably the issue is that 'module-re-export!' did not always support
> #:replace?, and that 1.1.0 uses an old version of Guile with the old
> calling convention when computing the derivation ... (I don't know
> if these details are actually true, it's a bit of a guess.)
The extra argument of module-re-export! was introduced with commit
cf08dbdc189f0005cab6f2ec7b23ed9d150ec43d in Guile. It seems like the
first Guile version after this commit is v2.2.7. Let's try
making the '#:replace? ...' conditional upon Guile>2.2 ...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-03-19 23:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 6:24 bug#53496: guix pull: error: build of `/gnu/store/njrsv4nw8v750zn6ajdcn8495592q6jb-compute-guix-derivation.drv' failed Peter Kois
2022-03-19 22:20 ` bug#53496: guix pull from 1.1.0 --> 29091731a0c6cb649cdfd72297575fe2bb2a9591 fails Maxime Devos
2022-03-19 22:28 ` Maxime Devos
2022-03-19 22:33 ` Maxime Devos [this message]
2022-03-19 22:58 ` Maxime Devos
2022-03-20 9:03 ` Maxime Devos
2022-03-21 15:19 ` Ludovic Courtès
2022-03-21 18:33 ` Maxime Devos
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=63a594ce58660df56b8a9437f4be00e438ceb295.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53496@debbugs.gnu.org \
--cc=kangus@gmail.com \
/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).