Re: Why? "Marked for autoremoval on 24 March due to xdelta3: #965883"
On Thu, 24 Feb 2022 at 14:48:42 +0100, Andreas Metzler wrote:
> Afaiui xdelta3 was (see below) rc-buggy, because it used dh 5 or 6 and
> was therefore marked for autoremoval. Afaik autoremovals are recursive,
> i.e. we do not make packages uninstallable by removing their
> dependencies but instead also remove these depending packages. I think
> this also extends to build-dependencies, we do not want unbuildable
> packages in testing so these would be removed, too.
Yes, all of that is correct.
If anyone has a better wording for the autoremoval message, that can
express this message as clearly and concisely as possible:
- the package you maintain does not have a RC bug itself
- but it (recursively) (build-)depends on xdelta3, which has RC bug #965883
- we cannot remove xdelta3 from testing without also removing the packages
that (build-)depend on xdelta3 from testing
- therefore the package you maintain is going to be autoremoved, unless
someone fixes #965883 in an xdelta3 upload sufficiently soon
then I'm sure the release team accept merge requests.
> This is probably very academic now since Andreas Tille has uploaded a fixed
> xdelta3 package today.
Hopefully yes!
smcv
Reply to: