On Thu, Nov 08, 2018 at 05:53:59PM +0000, Simon McVittie wrote:
> On Thu, 08 Nov 2018 at 15:50:48 +0000, Holger Levsen wrote:
> > On Thu, Nov 08, 2018 at 04:31:32PM +0100, Michael Biebl wrote:
> > > Wasn't there the idea to utilise the reproducible-build effort to detect
> > > binaries that differ depending on whether they were built in merged-usr
> > > environment or not?
>
> <https://bugs.debian.org/901473>
>
> > however, I would prefer a way which would prevent such
> > buggy binary packages from entering the archive in the first place...
>
> Do you have a way in mind?
source only uploads, for one.
> Are you saying that buildds should stick to unmerged /usr until we are
> more confident that merged /usr buildds will not misbuild packages, as
> I suggested? Or something else?
that's probably something which would help a bit, yes. (but its of
course not enough.)
> For maintainer uploads, there's a lintian tag that would have caught
can we have autorejects based on that?
As said, I'll happily merge a fix for #901473, I just think it's
fundamentally wrong to use a CI system to detect bugs done by manual
mistakes if such mistakes can be systematically avoided. also these bugs
still need to be manually filed.
(and because jenkins.d.n had severe issues the last days which I only
managed to address today I'm a bit reluctant to merge that fix right now
or probably even tomorrow. give us two days of nicely working jenkins
again, first, please :)
--
cheers,
Holger
-------------------------------------------------------------------------------
holger@(debian|reproducible-builds|layer-acht).org
PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
Attachment:
signature.asc
Description: PGP signature