libgnome-bluetooth13,  libgnome-bluetooth-dev,  gnome-bluetooth-common
and src:gnome-bluetooth are superseded versions of essentially the same
codebase as src:gnome-bluetooth3 (libgnome-bluetooth-3.0-13 and associated
packages).

The only packages outside this source package that
still depend on libgnome-bluetooth13 are budgie-core and
budgie-control-center. If possible, those packages should migrate to using
libgnome-bluetooth-3.0-dev and/or libgnome-bluetooth-ui-3.0-dev (I'll
report bugs and make them block this one). Or, if budgie specifically
needs libgnome-bluetooth13 for some reason, then the Budgie maintainers
will need to take responsibility for libgnome-bluetooth13.

    smcv

gnome-bluetooth is a transitional package now and does not depend on the old package.

Control: reopen -1
Control: reassign -1 src:gnome-bluetooth 3.34.5-8

This does not contradict my bug report. The fact that gnome-bluetooth.deb
is a transitional package depending on gnome-bluetooth-sendto does not alter
the fact that the upstream code contained in src:gnome-bluetooth is an
unmaintained library that has been superseded by src:gnome-bluetooth3.

We should remove this unmaintained upstream code from Debian, but at the
moment we cannot, because budgie-control-center (#1059485) and budgie-core
in unstable (#1059486, fixed in experimental) still have dependencies on it.

    smcv

Control: severity -1 serious
The reverse deps are gone. Please keep this out of trixie and consider filing a RM bug.

Thanks, I'll wait for the budgie packages to reach testing and then
ask the ftp team to remove this.

    smcv

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

gnome-bluetooth |  3.34.5-13 | source
gnome-bluetooth | 42~3.34.5-13 | all
gnome-bluetooth-common |  3.34.5-13 | all
libgnome-bluetooth-dev | 3.34.5-13+b4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x
libgnome-bluetooth13t64 | 3.34.5-13+b4 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x

------------------- Reason -------------------
RoQA; successor available; leaf package
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1093420@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1093420

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Paul Tagliamonte (the ftpmaster behind the curtain)