On Sat, Jan 30, 2021 at 09:13:42PM +0200, Niko Tyni wrote: > On Sat, Jan 30, 2021 at 07:35:04AM +0100, Paul Gevers wrote: > > > The pseudo excuses [1] report quite some autopkgtest regressions. Can > > you please check them, fix them if relevant or explain why they are not > > relevant for bullseye (e.g. unstable only)? > > > [1] https://release.debian.org/britney/pseudo-excuses-experimental.html#perl > > I spent most of today going through logs of the 300 or so packages showing > regressions. The gain was not worth the maintainer time IMHO. I'm not > looking forward to doing this again for the actual testing migration.
Thanks! > I found about 160 network/proxy failures on arm64 hosts with apt bailing > out, and about 120 installability failures relating to the four packages > that we already knew will need a rebuild. > > The remaining 19 failures are categorized below with comments. > > I'm away from my credentials for the self service, can schedule retries > probably tomorrow if necessary. Happy if somebody else beats me to it. I pressed retry a bunch of times. > Needs fixing for 5.32.1 > ----------------------- > > - libdevel-mat-dumper-perl > real issue; needs a strict dependency and a rebuild for 5.32.1 > also means this is a fifth package that needs a binnmu > filed #981408 > > - perl > filed as #981409 > minor issue, can be fixed when uploading to sid Fixed in git. > Retry suggested > --------------- > > bioperl # flaky; API rate limit exceeded, similar to testing/amd64/1.7.7-2 > 2020-12-02 04:21:20 UTC > backuppc # one-off? unlikely it's perl's fault > jellyfish # test suite timeout, not perl specific? > ikiwiki-hosting # not perl specific: apache2.service: Failed to set up mount > namespacing: Permission denied > libbio-db-ncbihelper-perl # network error? MSG: Can't query website: 500 > Status read failed: Connection reset by peer > trinityrnaseq # probably flaky? > libtest-valgrind-perl # no idea, worth a retry. Might be a valgrind issue on > ppc64el
