To fix or not to fix in lenny?

[Frank Küster <frank@debian.org>]

Dear release team,

a FTBFS problem on a buildd has revealed a bug in tex-common's
maintainer script boilerplates which are used to create the postrm
scripts for texlive-$allofthem and some other packages.

In the corner case that the package - which has the problematic postrm -
is unpacked, but not its dependency tex-common, the postrm will fail
when the unpacked is trying to be removed.  This is not a RC bug by the
wording, since we just assumed that what policy says is implemented. But
of course it is a serious bug in reality.

We'll fix that in unstable, but should we also fix it for a stable point
release? It would mean rebuilding 5 texlive source packages and a couple
of others against a new tex-common. And only for a corner case, which is
likely to happen only when some other problem breaks a dpkg run, and
*not* upon upgrade from lenny to squeeze. (Because either tex-common is
already installed before the upgrade, or the new, not-buggy package
would be unpacked without tex-common present.)

Regards, Frank
-- 
Dr. Frank Küster
Debian Developer (TeXLive)
VCD Aschaffenburg-Miltenberg, ADFC Miltenberg
B90/Grüne KV Miltenberg