[Debian-med-packaging] Bug#760790: Why does libtecla not propagate to testing (Was: libtecla is marked for autoremoval from testing)

[Adam D. Barratt]

On Sun, 2014-10-05 at 22:12 +0200, Andreas Tille wrote:
> the bug mentioned below was fixed on
> 
>    Mon, 08 Sep 2014 09:18:09 +0200
> 
> but the package did not migrated to testing.  In fact other
> architectures do not seem to build the package since the testing
> migration page
> 
>    https://qa.debian.org/excuses.php?package=libtecla
> 
> shows a lot of missings.

No, it built everywhere. What that page is showing you is that you
stopped building libtecla1-dev, having renamed it to libtecla-dev.

> I suspect that there was some manual hold or
> something like this on the package doe to the nature of bug #760790.

There was not.

If you stop building a package, it will not automatically disappear from
unstable. Assuming the package is dropped on all architectures then it
will appear on ftp-master's "cruft report" output
(https://ftp-master.debian.org/cruft-report-daily.txt) along with an
indication of which packages would be broken if it were removed from the
archive. Once that number is zero, it will be removed by a member of the
FTP team.

In the case of libtecla1-dev, because it Provides: libtecla-dev and
several packages build-depend on that, dak believed that removing the
package would break those other packages. After the confusion was
explained on IRC (not by me) the FTP team have now removed the old
package.

As a consequence, assuming there are no other issues, libtecla should
migrate in the next britney run.

Regards,

Adam