Bug#1094083: fixed in bzrtp 5.3.104-1

[Emilio Pozuelo Monfort]

On Fri, 07 Feb 2025 11:20:41 +0000 Debian FTP Masters 
<ftpmaster at ftp-master.debian.org> wrote:
> Source: bzrtp
> Source-Version: 5.3.104-1
> Done: Victor Seva <vseva at debian.org>
> 
> We believe that the bug you reported is fixed in the latest version of
> bzrtp, which is due to be installed in the Debian FTP archive.
> 
> A summary of the changes between this version and the previous one is
> attached.
> 
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 1094083 at bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Victor Seva <vseva at debian.org> (supplier of updated bzrtp package)
> 
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmaster at ftp-master.debian.org)
> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Format: 1.8
> Date: Fri, 07 Feb 2025 10:25:57 +0100
> Source: bzrtp
> Architecture: source
> Version: 5.3.104-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian VoIP Team <pkg-voip-maintainers at lists.alioth.debian.org>
> Changed-By: Victor Seva <vseva at debian.org>
> Closes: 1094083
> Changes:
>  bzrtp (5.3.104-1) unstable; urgency=medium
>  .
>    * add myself to Uploaders. wrap-and-sort -sat
>    * Set upstream metadata fields: Repository-Browse.
>    * New upstream version 5.3.104
>    * update stack dependencies (Closes: #1094083)
>    * debian/copyright: update
>    * remove empty patches/to_upstream
>    * refresh debian/patches
>    * update Breaks with versions in trixie and bookworm

The auto-removals is triggering removal of this package, which is preventing the 
fix from entering testing. As the rest of the stack seems to be ready and is 
blocked by this removal, let's ping the bug so the autoremoval is dropped, and 
the packages are tried for migration, which should hopefully fix this issue in 
testing.

Emilio