Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] git tarball hashes [was: Report of Buildroot developer meeting FOSDEM 2019]
Date: Fri, 8 Feb 2019 18:04:36 +0100	[thread overview]
Message-ID: <20190208170436.GB3079@scaer> (raw)
In-Reply-To: <73a827af-2547-9b19-837a-c7eeadcd54cd@mind.be>

Arnout, All,

On 2019-02-08 10:16 +0100, Arnout Vandecappelle spake thusly:
> On 08/02/2019 08:54, Thomas Petazzoni wrote:
> > 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.
> 
>  Ah yes indeed, and someone (Yann?) observed that the output generated by gzip
> has been stable since the dawn of the universe.

Yeah, I tried versions back to 1.2.4, released in 1993, and the output
is strictly identical. To be sure, I just re-did the test right now, and
yeah, it works:

    $ /bin/gzip --version |head -1
    gzip 1.6
    $ /bin/gzip -n -c -9 - <gzip-1.2.4.tar |sha1sum
    889f641f3dd4333065ae94281b1420b965a7f32a  -

    $ ./gzip-1.2.4/gzip --version 2>&1 |head -1
    gzip 1.2.4 (18 Aug 93)
    $ ./gzip-1.2.4/gzip -n -c -9 - <gzip-1.2.4.tar |sha1sum
    889f641f3dd4333065ae94281b1420b965a7f32a  -

So, Woo! for reproducibility! :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2019-02-08 17:04 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
2019-02-08  9:16     ` Arnout Vandecappelle
2019-02-08 17:04       ` Yann E. MORIN [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=20190208170436.GB3079@scaer \
    --to=yann.morin.1998@free.fr \
    --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