On 03/09/2018 03:01 PM, Dennis Gilmore wrote:
El vie, 09-03-2018 a las 14:55 +0100, Florian Weimer escribió:
On 03/09/2018 02:52 PM, Josh Boyer wrote:
Stepping back a bit, I'm curious why glibc32 would land in the
composes. It shouldn't... it should only be tagged in the fNN-
build
tags, which the composes should not pull from. Where do we have
recent issues of it getting pulled into a compose?
It happens after every single mass rebuild. The package is rebuilt
and
tagged, and then *boom*.
Thanks,
Florian
I think we can resolve this by adding glibc32 to the mass rebuild
blacklist. then it will not be rebuilt. the sources for it is
precompiled binaries so rebuilding does nothing
Looks that this would be a small but helpful step forward.
What would we have to do, as package maintainers, in order to avoid the
same issue when rebuilding the package manually? I would like to put a
bit fat warning into the glibc32.spec file.
Thanks,
Florian
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
