On Mon, 2020-06-01 at 20:53 +0200, Mattia Rizzolo wrote: > But so, do you think the first step lies in pbuilder/sbuild to decide an > interface for the package maintainers to use, or for the buildd managers > (wanna-build/buildd and launchpad) to decide on an interface that > sbuild needs to provide (and I would guess pbuilder will try to copy it > for consistency).
My initial thought was that none of the existing codebases should be doing this. Instead dsa-puppet should get sbuild post-build hooks that tar up a configurable set of build artefacts and transfer those to buildd.d.o to be displayed alongside build logs. The list of build artefact path patterns would be maintained in wanna-build/launchpad, transferred to each buildd before each build, matched after each build, the matches passed to tar and the tarball uploaded alongside the log. Since then I talked about this with aurel32/jcristau on #debian-buildd and they reached the conclusion that this should be a per-package thing left up to maintainers of packages rather than a global thing done by buildd management systems like wanna-build/launchpad. They thought the audience for this was mainly individual package maintainers rather than the porters, maintainers, RC bug fixers, NMUers and everyone else. All that said, I am not really one of the stakeholders in this discussion so I'll just follow along as a lurker from now on. -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Reproducible-builds mailing list Reproducible-builds@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds
