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

Johannes Schauer josch at debian.org
Tue Dec 20 12:49:27 UTC 2016


Hi,

Quoting Johannes Schauer (2016-12-19 10:02:58)
> I also came up with another question:

and as I'm implementing this, here yet another:

Currently, a buildinfo file does not specify which artifacts were supposed to
be built (source,any,all). 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?

How should a rebuilder infer the value of the --build argument that it passes
to dpkg-buildpackage to reproduce the given buildinfo file?

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/20161220/fbd1486f/attachment.sig>


More information about the Buildd-tools-devel mailing list