From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/download/svn: generate reproducible svn archives
Date: Sun, 22 Dec 2019 22:57:27 +0100 [thread overview]
Message-ID: <20191222225727.7e8f88d4@windsurf> (raw)
In-Reply-To: <CAEyMn7aZgVT2hmb8O4duNFeD4_x2_jkChOj9Cv3MAtVXZhQNLQ@mail.gmail.com>
On Sun, 22 Dec 2019 22:40:43 +0100
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> > Thanks. Could you check whether the tarballs that are now produced by
> > this are identical to the tarballs we already have on
> > sources.buildroot.org ?
>
> I checked this for the fis package and unfortunately this is not the
> case. Do you expect to have the same hashes?
Probably not, because with your change we now generate the tarballs
differently.
Normally, it is annoying because it means the hash has changed,
breaking the build for older Buildroot users, if we update the tarballs
on sources.buildroot.org.
However, in this case, current Buildroot does not have any hash (as far
as I can see) for Subversion-fetched packages. So we could introduce
your change and update the tarballs on sources.buildroot.org at the
same time, and then introduce hashes in those packages.
Peter, Yann, what do you think ?
We have only very few Subversion-fetched packages, I think we should
keep it simple.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-22 21:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-22 21:31 [Buildroot] [PATCH] support/download/svn: generate reproducible svn archives Heiko Thiery
2019-12-22 21:36 ` Thomas Petazzoni
2019-12-22 21:40 ` Heiko Thiery
2019-12-22 21:54 ` Heiko Thiery
2019-12-22 21:57 ` Thomas Petazzoni [this message]
2019-12-23 17:16 ` Yann E. MORIN
2019-12-23 22:05 ` Peter Korsgaard
2019-12-23 22:19 ` Thomas Petazzoni
2019-12-23 22:36 ` Peter Korsgaard
2020-01-06 9:31 ` Alexandre Belloni
2019-12-30 9:58 ` Yann E. MORIN
2020-05-22 14:09 ` 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=20191222225727.7e8f88d4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox