From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/open2300: add hash file
Date: Sun, 22 Dec 2019 12:05:34 +0100 [thread overview]
Message-ID: <20191222110534.GA26395@scaer> (raw)
In-Reply-To: <CAEyMn7aQSNzWDyPLi_g3mn+9Ze5ZxDYJ+mWp4m4TTMHUY6jrxg@mail.gmail.com>
Heiko, All,
On 2019-12-22 11:56 +0100, Heiko Thiery spake thusly:
> Am So., 22. Dez. 2019 um 11:08 Uhr schrieb Yann E. MORIN
> <yann.morin.1998@free.fr>:
> > On 2019-12-22 10:57 +0100, Thomas Petazzoni spake thusly:
> > > On Sun, 22 Dec 2019 09:37:08 +0100
> > > Heiko Thiery <heiko.thiery@gmail.com> wrote:
> > > > - add sha256 tarball hash
> > > > - add sha256 license hash
> > > The source code for this package is fetched from Subversion. Are the
> > > tarballs we create out of SVN repositories reproducible ? I guess so,
> > > but let's loop in Yann Morin for some additional feedback on this.
> > Seeing the dance we do in the git backend, and that we don't do it in
> > the svn backend, I doubt the svn backend is reproducible...
> >
> > Yet, I just checked, and I indeed get the same sha256 as Heiko provided
> > in this patch...
> >
> > Which prompted me in lookig at it. And we are not getting it from the
> > svn repository, for the good reason that the repository is dead and
> > off-line.
> >
> > Instead, we're getting in from s.b.o instead, and thus the reason why
> > the sha256 is reproducible...
> >
> > Dang... :-(
> >
> > So I suggest we do indeed add this hash, because in the end, that's
> > s.b.o providing it, so it is stable.
>
> Sorry, I didn't want to create this work ;-/ I just wanted to do some
> cleanup for the stats. So I picked a simple package to improve.
No problem. It was nice that you picked it up, because that made us
notice the problem! :-)
> I was not aware that special handling is needed for making builds
> reproducible at this point.
Yeah... Reproducibility is not a given. :-(
The subversion backend would need some love for that, so if you have a
bit of time on your hnads, that's be nice if you could tackle it (if
you're interested).
> By the way ... what does s.b.o mean?
Sources.Buildroot.Org, our fallback mirror:
http://sources.buildroot.org/
Regards,
Yann E. MORIN.
> > 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. |
> > '------------------------------^-------^------------------^--------------------'
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-12-22 11:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-22 8:37 [Buildroot] [PATCH] package/open2300: add hash file Heiko Thiery
2019-12-22 9:57 ` Thomas Petazzoni
2019-12-22 10:08 ` Yann E. MORIN
2019-12-22 10:56 ` Heiko Thiery
2019-12-22 11:05 ` Yann E. MORIN [this message]
2019-12-22 12:50 ` Heiko Thiery
2019-12-22 13:00 ` Yann E. MORIN
2019-12-22 11:00 ` Heiko Thiery
2019-12-22 11:07 ` Yann E. MORIN
2019-12-22 13:11 ` 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=20191222110534.GA26395@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 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.