Hi Jochen, El 14/09/22 a las 15:16, Jochen Sprickerhof escribió: > Hi Santiago, > > * Santiago Ruano Rincón <santiag...@riseup.net> [2022-09-14 10:36]: > > > this causes build failures: > > > > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/libtool.html > > > > > > and also autopkgtest failures: > > > > > > https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dpkg/26032114/log.gz > > > https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cjet/26041201/log.gz > > > > > > The first autopkgtest failure is in libtool which is vendored by a lot > > > of packages so will probably take a long time to fix. > > > > > > > Fixing this would require fixing libtool only, isn't that right? > > I don't think so, as it is in a lot of packages: > > https://codesearch.debian.net/search?q=Configured+with%3A%22+%7C+%24GREP+%22+%5C-L > > (Note that the buggy libtool.m4 is included into configure.)
Yeah, sorry. I lately realised not all the packages would autoreconf during building time. So silencing these warnings would make sense. > > > > P.S.: I will send a bug with a patch to the libtool maintainer. > > > > Please do. > > Done as #1019725. > > > P.S. I am letting Severity: serious for now to prevent migration to > > testing. But *I* am considering this rather Severity: important, at > > most. > > Note that the release team issued a block for now: > > https://release.debian.org/britney/hints/jcristau > > and proposed to test with a archive rebuild before introducing it again. ACK. Dear Release Team, just to be sure of being on the same page: if you are proposing to rebuild the whole archive, should I wait before silencing the warnings, for being able to (mass-)bug filing? Thanks, -- Santiago
signature.asc
Description: PGP signature
