On Wed, Sep 12, 2007 at 08:59:37PM +0000, brian m. carlson wrote:
> package dpkg
> tags 432893 + patch
> kthxbye
>
> Attached is a patch that *should* fix this bug. It simply restores the
> previous state of a package when a removal fails, instead of simply
> setting it to installed. Preliminary testing seems to confirm that this
> works. A changelog entry is also included.
Policy says:
If this fails, the package is in a "Failed-Config" state, or else
it remains "Installed".
Is there a reason that prerm failure doesn't always set the
Failed-Config state? dpkg has no idea which part of the prerm was
succesful and which not, it might have undone some part of the postinst
and then failed, and I think the Failed-Config makes most sense.
But I guess it should only do that if the original state was either
Installed or Failed-Config, and else keep the original state.
But I have no idea if it calls the prerm in the other states. For
instance, what should it do if called from Unpacked state?
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
