Bug#443334: marked as done (policy: postinst abort-remove state.)

[owner@bugs.debian.org (Debian Bug Tracking System)]

Your message dated Tue, 22 Jan 2008 13:07:18 -0800
with message-id <87bq7dtvqx.fsf@windlord.stanford.edu>
and subject line Bug#443334: policy: postinst abort-remove state.
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---

• To: submit@bugs.debian.org
• Subject: policy: postinst abort-remove state.
• From: Kurt Roeckx <kurt@roeckx.be>
• Date: Thu, 20 Sep 2007 18:56:09 +0200
• Message-id: <20070920165609.GA30871@roeckx.be>

Package: policy

Hi,

In section 6.8 it says:
     1.   <prerm> remove

          If prerm fails during replacement due to conflict

               <conflictor's-postinst> abort-remove \
                 in-favour <package> <new-version>

          Or else we call:

               <postinst> abort-remove

          If this fails, the package is in a "Failed-Config" state, or else
          it remains "Installed".


This remains "Installed" is wrong.  It should remain in the state it
was before the prerm remove was called.   The abort-remove should undo
what the prerm remove did, and prerm remove can be called from other
states than installed.

Please see bug #432893.


Kurt

--- End Message ---

--- Begin Message ---

• To: Ian Jackson <ian@davenant.greenend.org.uk>
• Cc: 443334-done@bugs.debian.org
• Subject: Re: Bug#443334: policy: postinst abort-remove state.
• From: Russ Allbery <rra@debian.org>
• Date: Tue, 22 Jan 2008 13:07:18 -0800
• Message-id: <87bq7dtvqx.fsf@windlord.stanford.edu>
• In-reply-to: <[🔎] 18326.20084.20656.754488@davenant.relativity.greenend.org.uk> (Ian Jackson's message of "Tue\, 22 Jan 2008 20\:13\:40 +0000")
• References: <18187.50915.735839.745678@davenant.relativity.greenend.org.uk> <18215.31418.402716.678362@davenant.relativity.greenend.org.uk> <20071031080953.GA26192@ouaza.com> <18216.30277.910641.310378@davenant.relativity.greenend.org.uk> <87myrrcua9.fsf@windlord.stanford.edu> <[🔎] 18326.20084.20656.754488@davenant.relativity.greenend.org.uk>

Ian Jackson <ian@davenant.greenend.org.uk> writes:

> Russ Allbery writes ("Re: Bug#443334: policy: postinst abort-remove state."):
>> I have lost track of the status of this and I don't know if a Policy
>> change is still needed here.  Has this change been made in dpkg?  Is there
>> something that should be changed in the Policy wording at this point?
>
> The change to dpkg seems to be blocked since October.  See #432893.
>
> The policy should remain unchanged.  The correct phrasing is indeed
> to say that the package `remains installed'.  If the package wasn't
> sufficiently close to installed to start with then the postinst won't
> be called.

Okay, thanks.  Closing this bug accordingly.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

--- End Message ---