Bug#296026: dpkg: State wrong when postrm fails on purge.

[Kurt Roeckx <kurt@roeckx.be>]

Package: dpkg
Version: 1.10.27
Severity: important

Hi,

It seems dpkg sets the state of a package wrong when the purge
failed and it was called with --purge.

Currently xfree86-common postrm fails to purge, but the removal
itself worked.

Starting with:
ii  xfree86-common 4.3.0.dfsg.1-1 X Window System (XFree86) infrastructure

dpkg --remove xfree86-common:
rc  xfree86-common 4.3.0.dfsg.1-1 X Window System (XFree86) infrastructure

dpkg --purge xfree86-common:
pc  xfree86-common 4.3.0.dfsg.1-1 X Window System (XFree86) infrastructure

This is the expected state.

Now, if I do start again from:
ii  xfree86-common 4.3.0.dfsg.1-1 X Window System (XFree86) infrastructure

And just do:
dpkg --purge xfree86-common
I get:
Removing xfree86-common ...
Purging configuration files for xfree86-common ...
 Removing any system startup links for /etc/init.d/xfree86-common
...
   /etc/rcS.d/S70xfree86-common
dpkg: error processing xfree86-common (--purge):
 subprocess post-removal script returned error exit status 20
Errors were encountered while processing:
 xfree86-common

And the state is:
pi  xfree86-common 4.3.0.dfsg.1-1 X Window System (XFree86) infrastructure

This is obviously wrong, since the postrm was succesful, it
should be in state c, as above.


Kurt