On Wed, Sep 21, 2016 at 12:13:39PM +0100, Chris Lamb wrote: > > > > + * Continue to support --buildinfo-identifier as an override for > > > > + --buildinfo-id, as jenkins is using it atm. > > > > > > shall we switch and use --buildinfo-id on jenkins? > > I was wondering whether you had a brief moment to outline — for those naïve > in the ELF arts — what the buildinfo things are, how they affect us, and > what these recent patches to dpkg mean? I'm afraid I'm a bit lost and I'm > probably not the only one.
Umh, this has nothing to do with ELF.
It's only about the .buildinfo file.
The canonical filename of .buildinfo file is:
${pkg}_${ver}_${random-string}.buildinfo
the --buildinfo-id option of dpkg-buildpackage (and now also in
dpkg-genbuildinfo), formely known as --buildinfo-identifier is used to
use a static and defined string in that "random-string" part of the
filename.
The reason we like to have a static string in there (and in jenkins we
use the host architecture), is that otherwise diffoscope would be noisy
about the difference in the name if we compared the .changes files, or
(as we actually do right now) we wouldn't know what files to pass to
diffoscope.
> Oh, if the explanation gets "too long" for an email, perhaps even consider
> a blog post, either on your own blog or the Reproducible one... :)
it's not so long :)
also, I don't have a blog post, though probably it's a good paraph in
the next weekly report.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
_______________________________________________ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
