Bug#284969: debian-policy: [PROPOSED] stop letting font packages that move stuff around screw people over

[Santiago Vila <sanvila@unex.es>]

On Wed, 15 Dec 2004, Branden Robinson wrote:

> On Thu, Dec 09, 2004 at 02:13:23PM -0800, Chris Waters wrote:
> > I would change that last "if" to "even if".  With or without that
> > change, though, I second the proposal.
> 
> So amended.

Branden, it will *not* work, because you can't change a postrm retroactively.
Please, read my previous message in this thread, specially the paragraph
starting with "IMHO".

Or else, think of it again: If a package move fonts from woody to sarge and
we make policy that the postrm of the sarge package runs update-fonts-dir
in the old location, it will not be until you upgrade from sarge to etch
that the new postrm will actually work and create the right fonts dir
in the directory where the fonts are not anymore.

In fact, I formally object to this proposal.

Now back to the problem, to solve it you can:

a) Require that postrm always run update-fonts-dir in the directory
where it ships the fonts, even on upgrades. This would solve the
problem from now on, but not for upgrades from packages which still do
not follow the new policy.

b) Require that postinst run update-fonts-dir in the directories where
previous releases of the same package located the fonts, if they are
different from the current location.

I would gladly second any of the solutions that work, but not the
proposed one.