[buildd-tools-devel] Bug#774415: From srebuild sbuild-wrapper to debrebuild

[Johannes Schauer]

Hi,

Quoting Johannes Schauer (2016-12-20 13:49:27)
> Currently, a buildinfo file does not specify which artifacts were supposed to
> be built (source,any,all).

as guillem points out to me on #debian-dpkg, the Architecture field lists
exactly that. It will contain "source" if the source package was built, "all"
for arch:all packages and a Debian architecture for arch:any builds.

> What should happen if the buildinfo file was for an Arch:any build but when
> rebuilding the source package, also arch:all packages show up? What should
> happen if the original build was including the source package but now it does
> not?
> 
> Should the verification fail if the build produces artifacts that are not
> listed in the buildinfo?
> 
> Should the verification fail if the build produces does not produce artifacts
> that are listed in the buildinfo?

I thus propose that a builder should use the Architecture field to figure out
what to build and fail if the produced artifacts are any different from the
ones in the buildinfo (being as strict about it as possible).

I implemented parsing of the Architecture field in the debrebuild.pl script and
let it pass the --build, --host, --arch-all, --arch-any and --source options to
sbuild.

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20161221/d963d6e9/attachment.sig>