Control: reassign -1 apt Hi!
On Sat, 2025-01-04 at 13:49:17 +0100, Niels Thykier wrote: > Niels Thykier: > > Package: dpkg,apt > > Severity: serious > > X-Debbugs-Cc: ni...@thykier.net > > There are a couple of failures in the apt's autopkgetests log with > > dpkg/1.22.13 (last success was probably dpkg/1.22.11, so it might be > > dpkg/1.22.12 triggering the problem for all I know). Hopefully I quoted > > there relevant parts. Thanks for keeping an eye on the autopkgtests! > > > 413s Test for failure in execution of grep Section rootdir/tmp/ > > > testsuccess.output … #### Complete file: rootdir/tmp/ > > > testsuccess.output #### > > > 413s 413s Package: nosection > > > 413s Architecture: amd64 > > > 413s Version: 1 > > > 413s Priority: optional > > > 413s Section: unknown > > > 413s Maintainer: Joe Sixpack <j...@example.org> > > > 413s Installed-Size: 11 > > > 413s Filename: pool/nosection_1_amd64.deb > > > 413s Size: 1220 > > > 413s SHA256: > > > 25a7930cc053e6ae84f4969f700f81f3c0c7d57c39f77c538dd2774e82d1f78f > > > 413s Description-en: an autogenerated dummy nosection=1/stable > > > 413s If you find such a package installed on your system, > > > 413s something went horribly wrong! They are autogenerated > > > 413s and used only by testcases and serve no other purpose?? > > > 413s Description-md5: c382d18d4d70f19b3be6b8f42648cb21 > > > 413s 413s #### grep output #### > > > 413s Section: unknown > > > 413s FAIL: exitcode 0 > > > 415s P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P > > > 415s Running test-apt-never-markauto-sections -> FAILED > Further thinking makes me think this is related to > https://lists.debian.org/debian-dpkg/2024/12/msg00010.html, which `dpkg` > also changed recently. Yes, this looks like a problem with an assumption that the Section is going to be missing instead of "unknown" now. > > > 430s Ensure correct error message file-conflict … #### Complete > > > file: apt-progress.log #### > > > 430s 430s dlstatus:1:0.0000:Retrieving file 1 of 2 > > > 430s dlstatus:2:50.0348:Retrieving file 2 of 2 > > > 430s dlstatus:2:100.0000:Retrieving file 2 of 2 > > > 430s pmstatus:dpkg-exec:0.0000:Running dpkg > > > 430s pmstatus:foo1:0.0000:Preparing foo1 (arm64) > > > 430s pmstatus:foo1:11.1111:Unpacking foo1 (arm64) > > > 430s pmstatus:foo1:22.2222:Installing foo1 (arm64) > > > 430s pmstatus:foo2:22.2222:Preparing foo2 (arm64) > > > 430s pmstatus:foo2:33.3333:Unpacking foo2 (arm64) > > > 430s pmerror:/tmp/tmp.hfgiCUnMQo/aptarchive/pool/ > > > foo2_0.8.15_arm64.deb:33.3333:trying to overwrite '/usr/bin/file- > > > conflict', which is also in package foo1 (0.8.15) > > > 430s #### grep output #### > > > 430s FAIL: exitcode 1 > > > 430s P P > > > 430s Running test-apt-progress-fd-error -> FAILED > > Still no clue on this one. This seems to be due to some error message unification from the dpkg side, specifically surrounding the package version within parenthesis, the subject for the commit introducing it was: dpkg: Unify package and version printing format to «package (version)» Thanks, Guillem
