Dear ftp-master,

I am investigating if I can fix Debian bug #973493 [1] by removing
rust-log. Our (Release Team) tooling doesn't schedule autoremoval for
this package, but also the package isn't in the key packages list. This
is a clear hint to me that the package is kept because of
(Build-)Depends in key packages on binaries from rust-log via Provides.
However, $(dak rm) doesn't report any issues:

"""
elbrus@coccia:~$ dak rm --no-action -R --suite testing rust-log
Will remove the following packages from testing:

librust-log+serde-dev |    0.4.8-4 | amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x
librust-log-dev |    0.4.8-4 | amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x
  rust-log |    0.4.8-4 | source

Maintainer: Debian Rust Maintainers
<pkg-rust-maintainers@alioth-lists.debian.net>
------------------- Reason -------------------

----------------------------------------------

Checking reverse dependencies...
No dependency problem found.
"""

However, librust-log-dev Provides librust-log+default-dev (= 0.4.8-4)
and is the only package to do so. There's a whole bunch of package that
(build-) depend on librust-log+default-dev.

Can dak please be fixed to also check (unique) Provides?

Paul

[1] https://bugs.debian.org/973493 [src:rust-log: fails to migrate to
testing]