Your message dated Tue, 9 Sep 2025 20:48:04 +0100
with message-id <[email protected]>
and subject line re: rust-x509-parser: fails its autopkgtests with badpkg
has caused the Debian Bug report #1114558,
regarding rust-x509-parser: fails its autopkgtests with badpkg
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 [email protected]
immediately.)
--
1114558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1114558
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rust-x509-parser
Version: 0.18.0-3
Severity: serious
Control: affects -1 src:pdns-recursor
Hi,
rust-x509-parser's autopkgtests currently fail to install the
necessary packages. Obviously this blocks testing migration.
autopktest log:
https://ci.debian.net/packages/r/rust-rustls/testing/amd64/64200177/
I can't quite figure out whats going on there, sorry.
Thanks,
Chris
--- End Message ---
--- Begin Message ---
rust-x509-parser's autopkgtests currently fail to install the
necessary packages. Obviously this blocks testing migration
rust-x509-parser's autopkgtests are passing just fine.
What was failing were rust-rustls's autopkgtests when triggered
by the new version of rust-x509-parser.
I can't quite figure out whats going on there, sorry.
Afaict the root of this issue is that test-dependencies are not
exported into any metadata files, so tools like britney cannot
use them in their dependency analysis.
rust-rustls 0.23.31+ds-4 has a test dependency on
librust-x509-parser-0.17+default-dev which is provided by
rust-x509-parser from testing, but not by rust-x509-parser
from unstable. So it is not possible to run the tests for
rust-rustls from testing with rust-tonic from unstable.
rust-rustls from unstable has test dependencies that are
satisfiable with the new rust-x509 parser, but britney has
no way of knowing that.
Sometimes this sort of issue can be worked around by
adjusting dependencies or breaks, in other cases it makes
more sense to ask the release team to manually schedule
more sensible tests, which is what I did in this case.
The release team has scheduled such tests and they have
passed on all relevant architectures.
--- End Message ---
