From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] check-host-tar.sh: blacklist tar 1.30+
Date: Tue, 27 Feb 2018 17:03:35 +0100 [thread overview]
Message-ID: <87606ipgh4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180227085541.11318-2-peter@korsgaard.com> (Peter Korsgaard's message of "Tue, 27 Feb 2018 09:55:41 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Tar 1.30 changed the --numeric-owner output for filenames > 100 characters,
> leading to hash mismatches for the tar archives we create ourselves from
> git. This is really a fix for a bug in earlier tar versions regarding
> deterministic output, so it is unlikely to be reverted in later versions.
> To work around this issue, blacklist tar 1.30+ similar to how we do it for
> pre-1.17 versions so Buildroot falls back to building host-tar.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> Changes since v1:
> - None
Committed after adding a link to
http://lists.busybox.net/pipermail/buildroot/2018-January/211222.html
which explains the issue in more details, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-02-27 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 8:55 [Buildroot] [PATCH v2 1/2] dependencies.mk: check for valid host-tar before other host dependencies Peter Korsgaard
2018-02-27 8:55 ` [Buildroot] [PATCH v2 2/2] check-host-tar.sh: blacklist tar 1.30+ Peter Korsgaard
2018-02-27 16:03 ` Peter Korsgaard [this message]
2018-04-10 20:50 ` Peter Korsgaard
2018-02-27 14:36 ` [Buildroot] [PATCH v2 1/2] dependencies.mk: check for valid host-tar before other host dependencies Matthew Weber
2018-02-27 16:03 ` Peter Korsgaard
2018-04-10 20:49 ` Peter Korsgaard
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=87606ipgh4.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox