Bug#1001765: [Pkg-rust-maintainers] Bug#1001765: src:rust-futures: fails to migrate to testing for too long: makes reverse dependencies uninstallable in testing

[peter green]

I know we 
expect this for some time in the rust ecosystem, but 60 days ought to be 
enough for that.


I appreciate your efforts to keep testing moving forwards.

All the crates that are used by applications in testing that had dependencies
on rust-futures have been dealt with (generally by disabling cargo features).

That leaves a bunch of crates from an old version of tokio which no longer
exist as separate crates in current tokio. The main tokio crate itself
(which has an updated version in unstable),and a couple of other miscellaneous
crates.

These will all be autoremoved in a few days time as a result of bugs
998570 and 998611

If you want to speed things up a bit and avoid rust-tokio cycling out
and back in to testing, then you could set removal hints on the following
packages.

rust-tokio-executor
rust-tokio-current-thread
rust-tokio-fs
rust-tokio-reactor
rust-tokio-tcp
rust-tokio-threadpool
rust-tokio-timer
rust-tokio-udp
rust-tokio-uds
rust-tokio-io
rust-bufstream
rust-lewton
rust-ogg
rust-tokio-async-await
rust-tokio-codec

Bug#1001765: src:rust-futures: fails to migrate to testing for too long: makes reverse dependencies uninstallable in testing

[Paul Gevers]

Source: rust-futures
Version: 0.1.29-3
Severity: serious
Control: close -1 0.3.17-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:rust-futures has been trying to migrate 
for 61 days [2]. Hence, I am filing this bug.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner. I know we 
expect this for some time in the rust ecosystem, but 60 days ought to be 
enough for that.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=rust-futures



OpenPGP_signature
Description: OpenPGP digital signature