Greetings.

If the reproducible builds autobuilders continue to build with
(the equivalent of) "dpkg-buildpackage", the following FTBFS will be
missed:

Packages which FTBFS in every autobuilder, including "Arch: all" if it
were uploaded in source-only form, like this one:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835224
https://buildd.debian.org/status/package.php?p=pymol

or the funny list of "Arch: all" packages having their binary-arch and
binary-indep targets swapped:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=sanv...@debian.org;tag=arch-all-swapped-binary-targets

none of which FTBFS in tests.reproducible-builds.org (or at least not
for that reason), but would FTBFS if they were uploaded in source-only
form.


Some time ago I proposed Holger to setup a queue for "dpkg-buildpackage -A".

But that's probably not good enough.

The ideal thing would be to have separate queues for "dpkg-buildpackage -A"
and "dpkg-buildpackage -B" and just forget about "dpkg-buildpackage".

This is really the "standard", what the official autobuilders do,
and what they will probably continue to do when everybody makes
source-only uploads, or maybe when the ftp-master queue start
ignoring the .debs and just pass the source to all the autobuilders.


It could be argued that "We are mainly interested in the
reproducibility issue, the FTBFS bugs are just a side effect".

And to that I would say "Fine, but what's the point in making a
package reproducible when it does not even build from source to begin
with?"


Thanks.

_______________________________________________
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Reply via email to