Your message dated Mon, 6 Apr 2026 09:57:51 +0200
with message-id <[email protected]>
and subject line Re: Bug#1132621: unblock: rust-rand/0.10.0+dfsg-2 and friends
has caused the Debian Bug report #1132621,
regarding unblock: rust-rand/0.10.0+dfsg-2 and friends
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.)
--
1132621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1132621
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock
I would like to request an autopkgtest override for the following
packages.
rust-rand/0.10.0+dfsg-2
rust-ahash/0.8.12-4.1
rust-uuid/1.21.0-6
rust-rand-0.8/0.8.5+dfsg-3
For some reason, the part of britney that schedules autopkgtests
seems to think that the new version of rust-swc-core needs to be
included as part of this update, even though the part of britney
that actually schedules migrations does not, and I can't see any
good reason for it.
This causes two issues.
1. The new version of rust-swc-core has an autopkgtest failure on s390x
2. The new version of rust-swc-core breaks testings version of
rust-microformats, which leads to autopkgtest failures for
rust-indieweb.
--- End Message ---
--- Begin Message ---
Hi Peter,
On 4/4/26 01:12, Peter Green wrote:
I would like to request an autopkgtest override for the following
packages.
rust-rand/0.10.0+dfsg-2
rust-ahash/0.8.12-4.1
rust-uuid/1.21.0-6
rust-rand-0.8/0.8.5+dfsg-3
For some reason, the part of britney that schedules autopkgtests
seems to think that the new version of rust-swc-core needs to be
included as part of this update, even though the part of britney
that actually schedules migrations does not, and I can't see any
good reason for it.
For next time, can you maybe propose which sources should be combined,
such that I can trigger them manually? I prefer to have a passing test
instead of blindly migrating things.
This causes two issues.
1. The new version of rust-swc-core has an autopkgtest failure on s390x
2. The new version of rust-swc-core breaks testings version of
rust-microformats, which leads to autopkgtest failures for
rust-indieweb.
So, I went ahead and scheduled tests with one of the latest sets shown
for rust-indieweb but without src:rust-swc-core. They seem to have
passed, so that seems to have been a good call. I applied the same set
for the autopkgtest of rus-swc-core on s390x which also just passed. I
think things are no longer blocked on autopkgtest failures.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
