From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Jan Nieuwenhuizen <janneke@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:39:04 -0500 [thread overview]
Message-ID: <87ft1aq3fb.fsf@gmail.com> (raw)
In-Reply-To: <8735xc86ne.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Wed, 03 Mar 2021 18:54:29 +0100")
Jan Nieuwenhuizen <janneke@gnu.org> writes:
> Ludovic Courtès writes:
>
> Hello!
>
>> Ludovic Courtès <ludo@gnu.org> skribis:
>>
>>> On #bootstrappable, mid-kid reported that ‘binutils-mesboot0’ in
>>> commencement.scm lacks ‘--enable-deterministic-archives’. So I checked
>>> if this had an effect by running:
>
>> [...]
>>
>>> Apparently Binutils 2.14 didn’t have ‘--enable-deterministic-archives’
>>> so we’ll have to patch it.
>>
>> Sikonas on #bootstrappable provided a patch for that (thanks!) so I went
>> ahead and gave it a try on ‘core-updates’ (Guix patch attached).
>
> Great!
>
>> The binutils source gets patched and repacked, but then decompressing it
>> fails:
>
> [..]
>
>> Maxime, does that ring a bell? Could it be that this bootstrap ‘xz’ is
>> less capable, or could it be a Gash-Utils bug?
>
> Currently, we avoid using non-bootstrapped binaries in the bootstrap,
> that includes 'xz'; earlier in the bootstrap that includes also 'patch'.
>
> See also gcc-core-mesboot0: it applies the patch in a manual phase. So
> I'm not sure if we want to start depending on 'xz' an this stage?
I see; so what Ludovic got surprised by is the fact that when adding
patches or a snippet to an origin it gets repacked as an xz tarball.
That's nothing new (it's how it is on the master branch too); but it can
indeed be surprising.
Maxim
next prev parent reply other threads:[~2021-03-04 16:42 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 [this message]
2021-03-08 14:13 ` Ludovic Courtès
2021-03-10 5:52 ` Jan Nieuwenhuizen
2021-03-04 16:14 ` Maxim Cournoyer
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=87ft1aq3fb.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=45962@debbugs.gnu.org \
--cc=janneke@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).