On Sun, Jun 04, 2017 at 12:15:56AM +0200, Andreas Beckmann wrote:
>...
> dpkg spews a lot of warnings about dependency problems, so it's not
> dblatex's fault if its postrm failed due to dependency violations.
> More likely apt (from jessie) is at fault here for choosing a broken
> upgrade path.
>...
> I don't see a point of updating dblatex in jessie to make its postrm
> handle "invalid states", at least not until the underlying cause has
> been identified.
Policy version 3.9.8.0 says in section 6.5:
<postrm> `remove'
<postrm> `purge'
<old-postrm> `upgrade' <new-version>
<disappearer's-postrm> `disappear' <overwriter> <overwriter-version>
The `postrm' script is called after the package's files have been
removed or replaced. The package whose `postrm' is being called
may have previously been deconfigured and only be "Unpacked", at
which point subsequent package changes do not consider its
dependencies. Therefore, all `postrm' actions may only rely on
essential packages and must gracefully skip any actions that
require the package's dependencies if those dependencies are
unavailable.
> Andreas
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
