Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/tar: bump version to 1.30
Date: Tue, 17 Jul 2018 23:34:13 +0200	[thread overview]
Message-ID: <871sc1k0mi.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180715154847.GD2516@scaer> (Yann E. MORIN's message of "Sun, 15 Jul 2018 17:48:47 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > Arnout, All,
 > On 2018-07-10 10:00 +0200, Arnout Vandecappelle spake thusly:
 >> Have you seen b8fa273d500b4?
 >> 
 >> check-host-tar.sh: blacklist tar 1.30+
 >> 
 >> 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.
 >> 
 >> For more details, see:
 >> http://lists.busybox.net/pipermail/buildroot/2018-January/211222.html
 >> 
 >> 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.
 >> 
 >> 
 >> Marked as Rejected...

 > Yet at some point, we will want to bump tar to a newer version.

 > What I would suggest is that we pin the host version to 1.29, and still
 > allow bumping the target version, so maybe something like:

 >     TAR_VERSION = 1.30
 >     HOST_TAR_VERSION = 1.29

Yes, that is possible. It does add a bit of extra complexity (subdirs
for patches, 2 versions in tar.hash, ..), but we already have that for
packages where we have a version selection.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2018-07-17 21:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-09 22:42 [Buildroot] [PATCH 1/1] package/tar: bump version to 1.30 Bernd Kuhls
2018-07-09 22:58 ` Bernd Kuhls
2018-07-10  8:02   ` Arnout Vandecappelle
2018-07-10  8:00 ` Arnout Vandecappelle
2018-07-15 15:48   ` Yann E. MORIN
2018-07-17 21:34     ` Peter Korsgaard [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871sc1k0mi.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