notfound 974916 3.8.1-1 close 974916 notfound 974917 3.8.1-1 close 974917 notfound 974919 0.7.19-2 close 974919 notfound 974920 0.7.19-2 close 974920 thanks
Hi Ralf, these issues are a normal way on how Rust packaging works, due to the fact that the Rust package manager does not pay any special attention to the concept of "source package" and only cares about "binary package". This means that a typical Rust Debian source package is in general expected to build binary packages that depend on other Rust Debian binary packages that may be uninstallable. This situation as you rightly pointed out is RC for Debian Stable. However, the Debian Testing migration script britney already prevents these packages from migrating to Debian Testing. And the Debian Rust team have scripts that monitor the reports output by britney. Therefore these extra bug reports are not helpful, since their usual purpose of blocking Testing migration is already performed automatically and in a fully-general way by britney. Therefore these RC bugs you filed serve no purpose but actually slow down our Rust packaging process, because the next maintainer who fixes the issue will have to hunt down the bug report number in order to close it, in order to unblock Testing migration. If you did not file this bug report, then this step would be unnecessary - britney would unblock as soon as the fix has been uploaded. Therefore, to save everyone's time, please do not file these types of bug reports for Rust packages in the future. I am closing these bug reports now because I noticed them, to save time for maintainers who have to dig them back up in the future. In fact there are very likely many more other Rust packages suffering from the same issue, and perpetually there will always be some in Debian Unstable, as explained above. Again, filing these bug reports provide no benefit, except add to the amount of work that Rust Debian packagers have to do to actually complete the Debian Testing migration process. See https://github.com/kpcyrd/cargo-debstatus/issues/2 for details. In summary, it is because the Rust dependency system encodes complex dependency relationships in a more efficient way than the Debian dependency system, meaning the typical Rust package expresses more complex dependencies than most other Debian packages. (But you can get this type of situation with other languages too, especially those with bootstrap loops. The only difference is in Rust it's much more common.) Best, Ximin
