All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <unixmania@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 next] package/tar: bump target version to 1.32 (host is kept at 1.29)
Date: Sat, 18 Jan 2020 11:12:31 -0300	[thread overview]
Message-ID: <CAJ4jsae+9emfBSo1x9CHsNszj62fMx6Su-Jixp_OsbJbYL4ucw@mail.gmail.com> (raw)
In-Reply-To: <20200118123934.GV22540@scaer>

On Sat, Jan 18, 2020 at 9:39 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
>
> Luc, Carlos, All,
>
> On 2019-11-19 09:18 -0300, unixmania at gmail.com spake thusly:
> > From: Luc Creti <luc.creti@atos.net>
> >
> > 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 way
> > they generate the archives.
> >
> > So, all the archives that have been 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 host-tar must be kept at version 1.29.
> >
> > For the target variant, this is less important, so bump it to the latest
> > version.
> >
> > Fixes: https://bugs.busybox.net/show_bug.cgi?id=12256
> >
> > Signed-off-by: Luc Creti <luc.creti@atos.net>
> > Signed-off-by: Carlos Santos <unixmania@gmail.com>
>
> Thanks for the reiterated attempts at bumping tar. I've now applied this
> version of the patch, which has the great advantage of not patching tar.
>
> Applied to master, with all the host-related commentsd and variables
> moved down to gether. Thanks.

Can't we at least get rid of the cpio thing, as done in v5?

-- 
Carlos Santos <unixmania@gmail.com>

  reply	other threads:[~2020-01-18 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 12:18 [Buildroot] [PATCH v3 next] package/tar: bump target version to 1.32 (host is kept at 1.29) unixmania at gmail.com
2020-01-18 12:39 ` Yann E. MORIN
2020-01-18 14:12   ` Carlos Santos [this message]
2020-01-18 14:51     ` Yann E. MORIN
2020-01-18 20:22       ` Carlos Santos

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=CAJ4jsae+9emfBSo1x9CHsNszj62fMx6Su-Jixp_OsbJbYL4ucw@mail.gmail.com \
    --to=unixmania@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.