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

[Niko Tyni]

On Thu, Dec 15, 2016 at 02:21:49PM +0100, Johannes Schauer wrote:
> Quoting Niko Tyni (2016-12-15 14:04:19)

> > In general, I like the concept of sbuild/pbuilder accepting .buildinfo files
> > as input. This makes the user interface simple. My expectation for this mode
> > of operation would be for the builder to recreate the old build as closely as
> > possible.
> 
> I agree but would add that they should also have the ability to tell the user
> if the checksums of the re-compiled packages do or do not match the information
> in the supplied .buildinfo file.

I suppose; please just make sure such a failure is easily distinguishable
from a failing build.

> > The other somewhat generic thing that the current script does / could
> > do is mangling the package build dependencies to correspond to the
> > exact versions in the .buildinfo file. This is a much easier and quite
> > mechanical task, but it might still be worth to make it into a filter
> > that takes one .dsc and outputs a modified one with strictly versioned
> > build dependencies?

> Doing the latter is extremely trivial:

Right, I see.

> I don't care whether we have debrebuild as a wrapper to sbuild/pbuilder or
> sbuild/pbuilder use a common tool to figure out the right lines for the
> sources.list inside the chroot. I just want to have .buildinfo support for
> sbuild in Stretch and if either solution is not in unstable soon, then my plan
> is to just add .buildinfo support to sbuild myself so that it's still included
> in the next Debian stable release.

Having this just inside sbuild for stretch and refactoring it out later
if necessary works for me, but I'm not sure if HW42 and/or Mattia have
thoughts about the pbuilder side?

I note that we're only getting started on working with .buildinfo
files. It seems possible that we encounter enough common tasks that
something like a 'buildinfo-utils' package will be warranted, in which
case a 'buildinfo find-debs' command would fit in there.

(Another task for buildinfo-utils I can think of is diffing/intersecting
build environment information in two .buildinfo files to determine
different/common things about two builds, but this is getting off-topic
for this bug...)
-- 
Niko Tyni   ntyni at debian.org