On Tue, 23 Dec 2008, Thomas Viehmann wrote:
Niko Tyni wrote:On Tue, Dec 23, 2008 at 02:15:22PM +0100, Thomas Viehmann wrote:immediately after I sent the last mail, Sune Vuorela pointed me to apache2's fix for #390823: They simply remove the problematic maintainer script. The question then is where to do this in so it is reliably done before stuff happens. In one of the perl packages (because the upgrade of perl triggers this) is probably too ugly, maybe the configure script of ghostscript?I think it's too late to do it inside ghostscript, it would have to go in perl-modules.
Maybe "configure script" is badly worded: It's most blatant abuse, but I'd just stick it into a /var/lib/dpkg/info/ghostscript.config unless there are apt-get-lookalikes that don't call that at the beginning of an upgrade. If the user produces the bad situation with dpkg by himself, well, who cares.
I think this is the best strategy. Better to hack related packages.An alternative is to to add gs-common being added to apt's 01autoremove, but I think that the /var/lib/dpkg/info/ghostscript.config change is a better choice; it limits the number of source packages affected.
I left some more notes on the bug, but this is the crux of it. -- Asheesh. -- You never know how many friends you have until you rent a house on the beach.