From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] git tarball hashes [was: Report of Buildroot developer meeting FOSDEM 2019]
Date: Fri, 8 Feb 2019 08:54:50 +0100 [thread overview]
Message-ID: <20190208085450.6306509e@windsurf> (raw)
In-Reply-To: <78472b2d-4adc-b110-273e-ddce78316dc2@mind.be>
On Thu, 7 Feb 2019 23:55:24 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:
> On 07/02/2019 23:51, Arnout Vandecappelle wrote:
> > making sure the git backend
> > produces reproducible tarballs by using the pax archive format (Yann started
> > working on an implementation for that)
>
> ?I realized while writing this: how does this approach fix the instability of
> gzip? Or do we assume that that was a one-off?
Which gzip issue are you talking about ? I think we never had a
*version* issue with gzip, only with installations where gzip is a
symlink to pigz.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-08 7:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 22:51 [Buildroot] Report of Buildroot developer meeting FOSDEM 2019 Arnout Vandecappelle
2019-02-07 22:55 ` [Buildroot] git tarball hashes [was: Report of Buildroot developer meeting FOSDEM 2019] Arnout Vandecappelle
2019-02-08 7:54 ` Thomas Petazzoni [this message]
2019-02-08 9:16 ` Arnout Vandecappelle
2019-02-08 17:04 ` 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=20190208085450.6306509e@windsurf \
--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 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.