From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 45962@debbugs.gnu.org
Subject: bug#45962: ‘binutils-mesboot0’ includes non-zero timestamps in ar archives
Date: Thu, 04 Mar 2021 11:14:29 -0500 [thread overview]
Message-ID: <87k0qmq4ka.fsf@gmail.com> (raw)
In-Reply-To: <87lfb4s5z7.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 03 Mar 2021 14:48:44 +0100")
Hi,
Ludovic Courtès <ludo@gnu.org> writes:
[...]
> ERROR: In procedure scm-error:
> ERROR: decompressed-port failure (7)
> error: in phase 'unpack': uncaught exception:
> srfi-34 #<condition &invoke-error [program: "tar" arguments: ("xvf" "/gnu/store/ywf5j03423yiawix3z21xa14hyyvd83z-binutils-2.14.tar.xz") exit-status: 1 term-signal: #f stop-signal: #f] 1215400>
> phase `unpack' failed after 0.3 seconds
> command "tar" "xvf" "/gnu/store/ywf5j03423yiawix3z21xa14hyyvd83z-binutils-2.14.tar.xz" failed with status 1
> builder for `/gnu/store/fwz150xjaqbh8n02z6gsmpm9w8lxckak-binutils-mesboot0-2.14.drv' failed with exit code 1
>
> Maxime, does that ring a bell? Could it be that this bootstrap ‘xz’ is
> less capable, or could it be a Gash-Utils bug?
From my IRC logs:
2020-09-20 22:32:01 apteryx janneke: haha! the xz-bootstrap supports
--memlimit with % after all, my mistake was really silly... forgetting a
space between the args passed as XZ_DEFAULTS
I recall a similar error I had hit when working on adding multi-core
compression support to xz, but it ended up being just a mistake on my
part; the xz-bootstrap supported the required arguments just fine after
all.
HTH,
Maxim
prev parent reply other threads:[~2021-03-04 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 17:29 bug#45962: ‘binutils-mesboot0’ includes non-zero timestamps in ar archives Ludovic Courtès
2021-03-03 13:48 ` Ludovic Courtès
2021-03-03 17:54 ` Jan Nieuwenhuizen
2021-03-04 16:39 ` Maxim Cournoyer
2021-03-08 14:13 ` Ludovic Courtès
2021-03-10 5:52 ` Jan Nieuwenhuizen
2021-03-04 16:14 ` Maxim Cournoyer [this message]
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=87k0qmq4ka.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=45962@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 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).