[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#503712: the gs-common problem

On Tue, Dec 23, 2008 at 09:39:20PM +0100, 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.
> > 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 see. It's blatant abuse indeed, but it might work.

The preconfiguration only happens if debconf and apt-utils are installed
(see /etc/apt/apt.conf.d/70debconf and /usr/sbin/dpkg-preconfigure), but
according to popcon more than 99.8% of all installations have them. 

If this is the chosen approach, the script could as well fix the etch
gs-common.prerm script instead of removing it; I think something like

if md5sum --status --check <<EOF
1959479be1e513d94a22f6fad8227fa3  /var/lib/dpkg/info/gs-common.prerm
    sed -i 's/defoma-app -t \(purge\|clean\) gs$/& || true/' \
        /var/lib/dpkg/info/gs-common.prerm || true

should do.
Niko Tyni   ntyni@debian.org

Reply to: