Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/7] support/download: reproducible archives whatever tar version (branch yem/dl-git-tar-pax)
Date: Thu, 19 Nov 2020 22:53:27 +0100	[thread overview]
Message-ID: <20201119225327.48a2a6d2@windsurf.home> (raw)
In-Reply-To: <cover.1605821010.git.yann.morin.1998@free.fr>

On Thu, 19 Nov 2020 22:23:47 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> Yann E. MORIN (7):
>       core/pkg-infra: prepare for alternate default source archives
>       WIP: support/download: change format of archives generated from git
>       WIP: boot+packages: update hash to new git-tarballs format
>       WIP: support/testing: update git-hash checks with new archive format
>       support/download: change format of archives generated from svn
>       support/dependencies: drop check for maximal tar version
>       package/tar: drop specific version for host variant

I reviewed the series, and overall it looks good to me. Of course, I
haven't actually tested/verified that the new magic set of tar options
makes things reproducible, but it seems like the amount of research on
this has been significant.

The only thing that bothers me a bit is that this series uses the
one-time bullet of switching from .tar.gz to .tar.xz, and I'm wondering
if we will not have other situations like this, and we won't have much
solution as we would already be using .tar.xz.

Just in my Go/Cargo vendoring, I'm encountering a similar problem: due
to the vendoring, the tarballs are changing and so are their hashes.
Since only two packages are impacted, I'm using the trick of bumping
them at the same time as I enable vendoring for them. But perhaps it
would be better to have a mechanism to support having different
tarballs for the same package ? I'm not sure how that would work
really, I don't have any clear idea.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2020-11-19 21:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 21:23 [Buildroot] [PATCH 0/7] support/download: reproducible archives whatever tar version (branch yem/dl-git-tar-pax) Yann E. MORIN
2020-11-19 21:23 ` [Buildroot] [PATCH 1/7] core/pkg-infra: prepare for alternate default source archives Yann E. MORIN
2020-11-19 21:23 ` [Buildroot] [PATCH 2/7] WIP: support/download: change format of archives generated from git Yann E. MORIN
2020-11-19 21:23 ` [Buildroot] [PATCH 3/7] WIP: boot+packages: update hash to new git-tarballs format Yann E. MORIN
2020-11-19 21:23 ` [Buildroot] [PATCH 4/7] WIP: support/testing: update git-hash checks with new archive format Yann E. MORIN
2020-11-19 21:23 ` [Buildroot] [PATCH 5/7] support/download: change format of archives generated from svn Yann E. MORIN
2020-11-19 21:23 ` [Buildroot] [PATCH 6/7] support/dependencies: drop check for maximal tar version Yann E. MORIN
2020-11-19 21:23 ` [Buildroot] [PATCH 7/7] package/tar: drop specific version for host variant Yann E. MORIN
2020-11-19 21:53 ` Thomas Petazzoni [this message]
2020-11-19 22:25   ` [Buildroot] [PATCH 0/7] support/download: reproducible archives whatever tar version (branch yem/dl-git-tar-pax) Yann E. MORIN

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=20201119225327.48a2a6d2@windsurf.home \
    --to=thomas.petazzoni@bootlin.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