Hi Santiago, On 15-09-2022 09:26, Paul Gevers wrote:
I am trying to schedule autopkgtests in unstable on amd64 for all source packages that have one.
All results are now in. Only several test failed due this warning: the known dpkg and cjet and the newly found nagios-plugins-contrib, logcheck and xautolock (see links below).
Lucas, are you in the position to do an archive rebuild to check for the grep warnings (see full history at [1]). When you submit bugs, can you please file them as important, as apparently upstream wants to turn these warnings into failures in the future, but in Debian Santiago is going to silence the warning soon, so FTBFS due to this isn't an RC problem on the short term.Santiago, please keep the grep with warning in unstable until either all tests are finished or we abort this plan.
To be honest, without bug 1019326 in ucf and bug 1019725 in libtool fixed, I'm not sure how much value an archive rebuild would be at this stage.
So I think it would be good to silence the warning now in Debian. As discussed before, ideally with a way to turn it on (or make it error) such that we can do archive wide QA before the behavior is changed to error out upstream. I can understand it if you want to wait with deploying that optional behavior until upstream has implemented it.
Paul https://ci.debian.net/data/autopkgtest/unstable/amd64/n/nagios-plugins-contrib/26117196/log.gz /37.20211217/check_ssl_cert/check_ssl_cert_2.15.0/check_ssl_cert/ line 1125 https://ci.debian.net/data/autopkgtest/unstable/amd64/l/logcheck/26123766/log.gz https://ci.debian.net/data/autopkgtest/unstable/amd64/x/xautolock/26130620/log.gz--> https://sources.debian.org/src/xautolock/1%3A2.2-7/debian/tests/help/ line 5
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature