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 deconfigured). Of course, libc6 is not essential, and deconfiguring a package does not cause its dependencies to be deconfigured (should it?) so its being pseudo-essential is not too relevant here. So I guess this also illustrates another side to the problem --- deconfiguring a package is a weird thing to do, which puts a package in a state where it is used to satisfy existing dependencies but its own dependencies might not be satisfied. Of course, that's the whole point. :) Just something worth remembering when documenting the new --deconfigure option. Sorry for the noise. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
