Hi, Quoting Chris Hofstaedtler (2024-04-28 18:30:56) > the autopkgtests for mmdebstrap as part of migration tests for testing/amd64 > fail with apt reporting 'Not found' errors. > > As an example, for this scenario: > mmdebstrap 1.4.3-6 > util-linux/2.40-8 gdm3/46.0-2 sssd/2.... > src:util-linux from unstable > src:gdm3 from unstable > src:sssd from unstable > https://ci.debian.net/packages/m/mmdebstrap/testing/amd64/46033215/ > > 1085s Err:22 http://127.0.0.1/debian unstable/main amd64 libssl3 amd64 3.1.5-1 > 1085s 404 File not found [IP: 127.0.0.1 80] > ... > 1085s Err:41 http://127.0.0.1/debian unstable/main amd64 libdb5.3 amd64 > 5.3.28+dfsg2-4+b1 > 1085s 404 File not found [IP: 127.0.0.1 80] > ... > 1085s Err:73 http://127.0.0.1/debian unstable/main amd64 libgdbm6 amd64 > 1.23-5+b1 > 1085s 404 File not found [IP: 127.0.0.1 80] > 1085s Err:74 http://127.0.0.1/debian unstable/main amd64 libgdbm-compat4 > amd64 1.23-5+b1 > 1085s 404 File not found [IP: 127.0.0.1 80] > > This looks like a pinning problem or some other issue. Given libssl3 is > a problem here, which is NOT a package considered for migration in this > test, I don't see how the test failure is actually related to the > involved packages. > If this is a transient situation, please detect it and exit with status 77.
unfortunately, this problem is not transient but reproducible. The problem is, that the involved libraries which are 404 have alternative 64bit time_t versions in unstable: libssl3 -> libssl3t64 libdb5.3 -> libdb5.3t64 libgdbm6 -> libgdbm6t64 libgdbm-compat4 -> libgdbm-compat4t64 And apt chooses to satisfy the (virtual) dependencies on those differently, depending on the surrounding dependency satisfaction problem. Related, debootstrap is also broken by the virtual providers of libssl3: #1069787 Feel free to tell the release team to ignore these failures if necessary. They will go away once the 64bit time_t transition is finished. Thanks! cheers, josch
signature.asc
Description: signature
