[Pkg-rust-maintainers] Bug#975191: rust-js-sys: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

[peter green]

 > This will impact quite some other modules.

I agree that the current autoremoval list looks pretty scary, so I decided to do some
dependency analysis. It seems there are 5 source packages with direct or indirect hard
dependencies on rust-js-sys.

rust-www-sys
rust-ring
rust-rustls
rust-sct
rust-webpki

There are also some feature packages which directly or indirectly depend on rust-js-sys.

librust-chrono+js-sys-dev (already dropped by the version of rust-chrono in unstable)
librust-chrono+wasmbind-dev (already dropped by the version of rust-chrono in unstable)
librust-cookie+ring-dev (not in testing)
librust-cookie+secure-dev (not in testing)
librust-trust-dns-proto+dnssec-ring-dev
librust-trust-dns-proto+ring-dev
librust-reqwest+rustls-dev
librust-reqwest+rustls-tls-dev
librust-reqwest+webpki-roots-dev


None of these feature packages seem to have any reverse dependencies. Furthermore None of the other
binaries built from rust-trust-dns-proto seem to have any reverse dependenices in unstable.
For rust-reqwest there seems to be one reverse dependency in unstable, but it is not
currently in testing for other reasons.

In summary once kpcyrd's upload of rust-chrono migrates to testing, the list of packages
to be autoremoved because of rust-js-sys should get a lot shorter.