Hi, Niko Tyni wrote: >> 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 > EOF > then > sed -i 's/defoma-app -t \(purge\|clean\) gs$/& || true/' \ > /var/lib/dpkg/info/gs-common.prerm || true > fi > > should do.
Barring objections, I'll test things and NMU along the lines Niko indicated on Sunday. Thanks to everyone for weighing in on the bug report. Kind regards T. -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
