[rb-general] reproducible anything

[Vagrant Cascadian]

On 2018-10-09, Holger Levsen <holger at layer-acht.org> wrote:
> On Mon, Oct 08, 2018 at 05:27:52PM +0200, Bernhard M. Wiedemann wrote:
>> How are 'all' arch packages built in Debian?
>
> I believe they are build on the first arch being build but i'm not
> entirely sure this is the case, or rather, how this is determined.
> or maybe the arch:all packages from other binary uploads are discarded.

I'm pretty sure the arch:all build machines in debian are running amd64,
and are only built if the uploader didn't include arch:all packages (I
wish source-only uploads were mandatory... but that's a bit off-topic).

Which is different from the builds on tests.reproducible-builds.org for
debian, which build both arch:any and arch:all packages on all of the
architectures tested by tests.reproducible-builds.org.


>> If you publish only results from one arch there, they are effectively
>> cross-built already.

Without any serious study, I did check several of my own arch:all
packages at one point and was happy to find matching checksums across
the packages produced by debian's official build, my local build, and
most of the builds done on tests.reproducible-builds.org (I think one
had a serious toolchain difference at the time).

This is one reason I wish we did arch:all builds as a separate thing on
tests.reproducible-builds.org, as right now the only way to compare the
arch:all components across architectures is manually (though some of it
could possibly be scripted with some work). Given resource-constraints,
I can see this not being a high priority.

It seems very plausible to me that packages might build arch:all
differently depending on if arch:any were built at the same time. Again,
it's a matter of resource constraints and priorities.


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://lists.reproducible-builds.org/pipermail/rb-general/attachments/20181009/69933974/attachment.sig>