Your message dated Tue, 1 Nov 2022 13:40:54 +0000
with message-id <c9408bf8-33db-0f25-03b5-3f94a591b...@debian.org>
and subject line Re: Bug#1023265: Test failures blocking migration of rust-libc
and several deps to testing
has caused the Debian Bug report #1023265,
regarding Test failures blocking migration of rust-libc and several deps to
testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1023265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rust-libc
Version: 0.2.137-1
Severity: serious
X-Debbugs-CC: plugw...@debian.org, wolfg...@silbermayr.at, infini...@debian.org
Migration of several other packages is blocked due to the issues listed
over at:
https://tracker.debian.org/pkg/rust-libc
In particular, it has caused failures in rust-capston on s390x and
rust-netlink-sys in multiple platforms.
Thanks,
John
--- End Message ---
--- Begin Message ---
On 01/11/2022 12:11, John Goerzen wrote:
Package: rust-libc
Version: 0.2.137-1
Severity: serious
X-Debbugs-CC: plugw...@debian.org, wolfg...@silbermayr.at, infini...@debian.org
Migration of several other packages is blocked due to the issues listed
over at:
https://tracker.debian.org/pkg/rust-libc
In particular, it has caused failures in rust-capston on s390x and
rust-netlink-sys in multiple platforms.
These failures are not caused by the new version of rust-libc, but are
artifiacts of the way Debian's CI infrastructure satisfies dependencies
for autopktests.
Specifically, when performing unstable->testing migration tests, but not
when performing plain testing tests, Debians autopkgtest infrastructure
uses a fallback dependency solver. This means if the test dependencies
can't be satisfied using the generated pins, it will instead try using
packages only for unstable.
The result of this is that the tests in question are skipped in plain
testing tests, but run in unstable->testing migration tests. This leads
to psudedo-regressions.
I have made uploads for netlink-sys and capstone which make the
autopkgtests pass, where I have felt reasonablly able to I have fixed
the underlying issues, but in some cases I have reported the issues
upstream and skipped the tests (since they do not represent real
regressions compared to the current state in testing.
Once the netlink-sys and capstone uploads reach testing and the migration
tests are re-run then libc should migrate to testing.
--- End Message ---
