From: Maxime Devos <maximedevos@telenet.be>
To: "Toorn, H.W.P. van den (Henk)" <H.W.P.vandenToorn@uu.nl>,
57527@debbugs.gnu.org
Subject: bug#57527: compute-guix-derivation has an error
Date: Thu, 1 Sep 2022 18:39:20 +0200 [thread overview]
Message-ID: <c31526e0-eec1-2a76-409e-a22e5b3438a5@telenet.be> (raw)
In-Reply-To: <4a7379ce-40b6-0a56-648c-8160cd1cf1b6@uu.nl>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 1540 bytes --]
severity 57527 important
merge 47764 57527
thanks
For now, you can try working-around by retrying "guix pull".
On 01-09-2022 17:00, Toorn, H.W.P. van den (Henk) via Bug reports for
GNU Guix wrote:
> 1417:15 4 (_ #<store-connection 256.99 7f46930e6e60>
> ("/gnu/store/4khcb3b0iqfimjgg6yqnlpf9pkim7s4v-curl-7.84.?" ?) ?)
> 1417:15 3 (loop #f)
> 711:11 2 (process-stderr #<store-connection 256.99 7f46930e6e60> _)
> In ./guix/serialization.scm:
> 102:11 1 (read-int #<input-output: file 10>)
> 80:6 0 (get-bytevector-n* #<input-output: file 10> 8)
Procedure at 80:6:
> (define (get-bytevector-n* port count)
> (let ((bv (get-bytevector-n port count)))
> (when (or (eof-object? bv)
> (< (bytevector-length bv) count))
> (raise (condition (&nar-error
> (file (currently-restored-file))
> (port port)))))
> bv))
An alternative hypotheses:
* build-aux/build-self.scm lets the port be a duplicate of standard
input. But maybe some other code for whatever reason accidentally
reads from there as well? Or: maybe the script is started without
stdout, so when it is duplicated, it becomes stdout, and future code
writes to stdout (i.e., the store port), causing interference?
Potential solution: Open /dev/null on top of stdin, check that the
store port is >2.
Greetings,
Maxime.
[-- Attachment #1.1.1.2: Type: text/html, Size: 2176 bytes --]
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-09-01 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 15:00 bug#57527: compute-guix-derivation has an error Toorn, H.W.P. van den (Henk) via Bug reports for GNU Guix
2022-09-01 16:39 ` Maxime Devos [this message]
2022-09-01 17:38 ` zimoun
2022-09-01 17:07 ` 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=c31526e0-eec1-2a76-409e-a22e5b3438a5@telenet.be \
--to=maximedevos@telenet.be \
--cc=57527@debbugs.gnu.org \
--cc=H.W.P.vandenToorn@uu.nl \
/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).