From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/dvb-apps: add hash file
Date: Tue, 7 Jul 2020 12:21:25 +0200 [thread overview]
Message-ID: <20200707122125.102c9bea@windsurf> (raw)
In-Reply-To: <20200705173702.GI2273@scaer>
Hello,
On Sun, 5 Jul 2020 19:37:02 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> I too got that 926208 sha256 here, with two different hg versions: 3.7.3
> and 4.8.2.
>
> > --2020-07-05 14:51:38-- http://sources.buildroot.net/dvb-apps/dvb-apps-3d43b280298c39a67d1d889e01e173f52c12da35.tar.gz
>
> dvb-apps-3d43b280298c39a67d1d889e01e173f52c12da35.tar.gz 2014-Sep-01 16:03:23 442.7K application/x-gtar-compressed
>
> So, this file was created before the commit that made the archives
> reproducible. So, no surprise that the sha256 does not match the
> locally-created archive but that from s.b.o.
Here, since there is no hash file for dvb-apps in Buildroot in any
Buildroot version, we could change the tarball on sources.b.o.
It would of course be nicer if we could bump the version of dvb-apps,
so that we can keep this older tarball unchanged. But that's not
strictly required as we have never had any hash file for this package.
> The python-pygame archive was however created after commit 76b51f90c0e...
>
> > requesting all changes
> > adding changesets
> > adding manifests
> > adding file changes
> > added 3652 changesets with 15404 changes to 1890 files (+17 heads)
> > new changesets 4609a0076cda:48e19c7b9ee9
> > ERROR: pygame-d61ea8eabd56.tar.gz has wrong sha256 hash:
> > ERROR: expected: f95a7dd68ea294d415e36e068d2f533c5a01c67773452d14a535c5c7455681fe
> > ERROR: got : d5e0a43a4e338de4cb282af0ddd6e671055d6b9290030c27cfac41b1f7801232
>
> I too git d5e0a43a4e33.
>
> What machine is pushing the archives to s.b.o. ?
I've added Peter in Cc, as he is taking care of the sources.b.o
maintenance. I think it is done on the OSUOSL machine, because Peter
has a script update-br-mirror.sh on this machine.
This machine has:
$ hg --version
Mercurial Distributed SCM (version 2.6.2)
So it is even older than the 3.x and 4.x Mercurial versions you have
tested.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-07-07 10:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 1:05 [Buildroot] [PATCH] package/dvb-apps: add hash file Sergio Prado
2020-07-05 12:54 ` Thomas Petazzoni
2020-07-05 17:37 ` Yann E. MORIN
2020-07-07 10:21 ` Thomas Petazzoni [this message]
2020-07-07 13:12 ` Peter Korsgaard
2020-07-07 19:55 ` Sergio Prado
2020-07-08 16:35 ` Yann E. MORIN
2020-07-08 16:51 ` Thomas Petazzoni
2020-07-08 17:03 ` Peter Korsgaard
2020-07-08 16:59 ` Peter Korsgaard
2020-07-05 17:40 ` Sergio Prado
2020-07-06 17:21 ` Yann E. MORIN
2020-07-06 20:14 ` Sergio Prado
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=20200707122125.102c9bea@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.