Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12256] package tar is outdated (1.29 is 3 years old)
Date: Mon, 07 Oct 2019 16:38:49 +0000	[thread overview]
Message-ID: <bug-12256-163-jHSj0oz3Ks@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12256-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=12256

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yann.morin.1998 at free.fr

--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
We can't upgrade the version of tar without being cautious.

The host tar is used to create the archives in the VCS download backends
(git, cvs, svn, hg...) and tar 1.30 and forward have changed the wau they
generate the archives.

So, all the archives we had generated before 1.30 was released are not
bit-for-bit reproducible (even though the extracted content would be),
so the hashes we have for those archives would not match.

Hence we need to keep host-tar to 1.29.

For the target variant, this is less important of course, but so far
no one submitted a patch. It's also that we do not have many packages
for which the host and target versions are different.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2019-10-07 16:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07  9:40 [Buildroot] [Bug 12256] New: package tar is outdated (1.29 is 3 years old) bugzilla at busybox.net
2019-10-07 16:38 ` bugzilla at busybox.net [this message]
2019-10-08 11:36 ` [Buildroot] [Bug 12256] " bugzilla at busybox.net
2019-11-17 13:06 ` bugzilla at busybox.net
2019-11-18 13:21 ` bugzilla at busybox.net
2019-11-19  1:17 ` bugzilla at busybox.net
2019-11-19  8:15 ` bugzilla at busybox.net
2020-05-19 21:45 ` bugzilla at busybox.net

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=bug-12256-163-jHSj0oz3Ks@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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