Frankly, I’m tempted to reassign this to dpkg; Policy §7.2 is very clear
on the relationship between prerm scripts and Depends.
It’s not the first time I’ve seen this, although it usually happens when
there is a dependency cycle: one of the dependencies of a package in the
Depends list can be in a broken state at the time of prerm running.
Dpkg needs to ensure that all dependencies *and their own dependencies*
are in a clean, installed state when running the prerm script. It
correctly does it for postinst already.
--
.'`.
: :' : We are debian.org. Lower your prices, surrender your code.
`. `' We will add your hardware and software distinctiveness to
`- our own. Resistance is futile.