Package: dpkg
Version: 1.15.8.10
Severity: wishlist
As it was discovered in some places (#558151), some system modifications
cannot be sanely made without specifying --auto-deconfigure to dpkg.
Please provide a --deconfigure command, so dpkg front-ends can plan and
request deconfigurations
Hi Eugene,
Eugene V. Lyubimkin wrote:
As it was discovered in some places (#558151), some system modifications
cannot be sanely made without specifying --auto-deconfigure to dpkg.
Please provide a --deconfigure command, so dpkg front-ends can plan and
request deconfigurations themselves.
I
Hi Jonathan,
Thanks for adding more examples to the list, but
On 2011-05-20 13:16, Jonathan Nieder wrote:
But the motivational example
libc6 Depends: libc-bin (= ${binary:Version})
libc-binBreaks: libc6 ( 2.10)
does not seem like a great example for this. libc6
Eugene V. Lyubimkin wrote:
On 2011-05-20 13:16, Jonathan Nieder wrote:
unpack libc6
unpack libc-bin
configure libc-bin
configure libc6
Emm, the whole #558151 was about the order above does not work unless
you specify --force-bad-path which Guillem was much against.
Hi again,
A quick note to finish the tangent.
Jonathan Nieder wrote:
In an ideal world, the upgrade path
would be
unpack libc-bin
unpack libc6
configure libc-bin
configure libc6
with no deconfigure step (essential packages are not supposed to ever
need to be
5 matches
Mail list logo
