Hi,
Am 15.09.22 um 15:50 schrieb Paul Gevers:
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.
And the first results are coming in. I'm not sure how to proceed
though, see 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.
I wonder if this is going to be useful. The first couple of hits I
inspected, the warning didn't occur in the autopkgtest itself, but
during installation of required packages.
Packages using ucf, yes.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019326
E.g.
https://ci.debian.net/data/autopkgtest/unstable/amd64/l/lintian-brush/26114550/log.gz
shows the warning while running update-perl-sax-parsers during
installation libxml-sax-perl
and
https://ci.debian.net/data/autopkgtest/unstable/amd64/g/golang-github-lib-pq/26114898/log.gz
shows the warning while installing postgresql-common
A lot of tests use postgresql, so weeding that out isn't going to be
trivial.
Any ideas? (I'll of course file bugs against postqresql-common and
whatever contains update-perl-sax-parsers, but I'll need more
automation for the rest)
Doesn't make sense imho, as neither has a bug and it's actually ucf in
many cases doing the grep in question.
Regards,
Rene
