Hello,
On 24.12.2012 17:50, Adam D. Barratt wrote:
On 09.10.2012 08:10, Helmut Grohne wrote:
On Tue, Oct 09, 2012 at 09:15:32AM +0200, Raphael Hertzog wrote:
On Mon, 08 Oct 2012, Helmut Grohne wrote:
> 1) Add a pre-dependency on dpkg such that dpkg is already upgraded
> before deconfiguring sgml-base. This does not guarantee to solve the
> issue, because the old dpkg may still be running, but it makes it
> highly unlikely.
IIRC when apt upgrades dpkg, it configures it immediately so that any
package processed after dpkg is guaranteed to be processed by the
upgraded
dpkg.
Thanks for the explanation. Do you also know whether aptitude and cupt
show the same behaviour?
CCing the relevant maintainers.
Thanks for caring.
As for (lib)cupt, newest/latest dpkg is invoked for every new action
group. Dpkg is essential, therefore it cannot have circular
dependencies, therefore it's guaranteed to be the only package in the
action group.
In other words, I believe "any package processed after dpkg is
guaranteed to be processed by the upgraded dpkg" is true.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
