Your message dated Sat, 30 Aug 2025 08:30:47 +0200 with message-id <f94bdd97-b44c-48a0-a20c-5d786fb36e0a@debian.org> and subject line Re: Bug#1112482: unblock: rust-tempfile/3.21.0 has caused the Debian Bug report #1112482, regarding unblock: rust-tempfile/3.21.0 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 owner@bugs.debian.org immediately.) -- 1112482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112482 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: rust-tempfile/3.21.0
- From: Peter Green <plugwash@debian.org>
- Date: Sat, 30 Aug 2025 00:24:48 +0100
- Message-id: <[🔎] ba6d8fd6-777b-460d-b225-d6fb407efa71@debian.org>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock rust-tempfile is blocked from migrating to testing by an autopkgtest "regression" in rust-debian-analyzer on s390x. The root cause of this "regression" is that apt currently fails to install some rust packages in testing even though they are technically installable due to the fact that rust-hashbrown-0.14 has migrated but rust-hashbrown has not. This leads to autopkgtest going to the fallback dependency solver, which leads to trying to run the tests from the old rust-debian-analyzer, against the packages from the new rust-debian-analyzer which leads to a "crate directory not found error". To fix the root cause we have to get the new version of rust-hashbrown into testing, to do that we need to get the new versions of rust-pyo3 and friends into testing and to do that we need to get the new version of rust-tempfile into testing. To workaround this issue, I bumped the dependency of rust-debian-analyzer on rust-tempfile, expecting that would cause britney to schedule tests with the new rust-debian-analyzer and it worked on most architectures, but for reasons I cannot fathom when britney scheduled the test on s390x it did not include rust-tempfile in the list of triggers or pinned packages. Please schedule a test on s390x for the new version of rust-debian-analyzer with the new version of rust-tempfile.
--- End Message ---
--- Begin Message ---
- To: 1112482-done@bugs.debian.org
- Subject: Re: Bug#1112482: unblock: rust-tempfile/3.21.0
- From: Paul Gevers <elbrus@debian.org>
- Date: Sat, 30 Aug 2025 08:30:47 +0200
- Message-id: <f94bdd97-b44c-48a0-a20c-5d786fb36e0a@debian.org>
- In-reply-to: <[🔎] d68c28fd-4ef2-4852-9b2d-0fe6c3e96149@debian.org>
- References: <[🔎] ba6d8fd6-777b-460d-b225-d6fb407efa71@debian.org> <[🔎] ba6d8fd6-777b-460d-b225-d6fb407efa71@debian.org> <[🔎] d68c28fd-4ef2-4852-9b2d-0fe6c3e96149@debian.org>
Forgot to close. On 30-08-2025 08:26, Paul Gevers wrote:Done.Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---