From: Christopher Baines <mail@cbaines.net>
To: 46212@debbugs.gnu.org
Subject: bug#46212: ci.guix.gnu.org narinfos with excessive NarSize
Date: Mon, 01 Feb 2021 19:57:06 +0000 [thread overview]
Message-ID: <87r1lzftnx.fsf@cbaines.net> (raw)
In-Reply-To: <87zh0pf9ip.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
Christopher Baines <mail@cbaines.net> writes:
> I noticed through the Guix Data Service that some narinfo files from
> ci.guix.gnu.org have an excessive NarSize.
>
> These are the three that I've found, but there could be more.
>
>
> /gnu/store/qln574djfgl8h9glij9id8jips7nnrlw-flightgear-2018.3.5
> NarSize: 18446744072099351584
>
> /gnu/store/qhix6afvy2a6n7hlx4qgdns461p8kdnv-repeat-masker-4.1.1
> NarSize: 18446744071612438544
>
> /gnu/store/wd9z64xpck56xzf52jwlpg8vb610b0ym-repeat-masker-4.1.1
> NarSize: 18446744071612438544
Guix gives the following error when it encounters one of these bad
narinfos:
error: integer expected from stream
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2021-02-01 19:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 14:47 bug#46212: ci.guix.gnu.org narinfos with excessive NarSize Christopher Baines
2021-01-31 15:20 ` Ludovic Courtès
2021-02-01 9:15 ` Ludovic Courtès
2021-02-19 15:11 ` Ludovic Courtès
2021-02-22 8:59 ` Mathieu Othacehe
2021-02-22 13:03 ` Ludovic Courtès
2021-02-24 10:26 ` Mathieu Othacehe
2021-02-01 19:57 ` Christopher Baines [this message]
2021-02-02 21:48 ` Ludovic Courtès
2021-03-21 14:38 ` Ludovic Courtès
2021-03-21 14:55 ` Ludovic Courtès
2021-03-21 14:55 ` Ludovic Courtès
2021-03-29 7:45 ` Mathieu Othacehe
2021-04-07 9:09 ` Brendan Tildesley via Bug reports for GNU Guix
2021-06-11 12:04 ` Christopher Baines
2021-06-18 9:48 ` Ludovic Courtès
2021-11-24 23:28 ` Ludovic Courtès
2021-11-25 8:42 ` Christopher Baines
2021-11-26 10:11 ` 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=87r1lzftnx.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=46212@debbugs.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.