Package: python-apt Every few weeks I wonder why I don't get those cheery apt-listchanges messages any more.
It turns out every few weeks I must have hit RET when all along buried within the question I was being asked was, e.g., The following packages will be REMOVED: apt-file apt-listchanges libapt-pkg-perl python-apt The following packages will be upgraded: apt apt-utils Yes, I know the correct procedure when greeted with such a message is to just wait a couple of days before hitting RET. But now I am starting to wonder, why do packages other than apt-listchanges seem not so easy to get deleted so often? Could it be the order in which the dependencies are sent to the mirrors? Or something about the dependencies themselves. -o Debug::PkgProblemResolver=True shows Investigating python-apt Package python-apt has broken dep on libapt-inst-libc6.6-6-1.1 Considering apt-utils 4 as a solution to python-apt 1 Removing python-apt rather than change libapt-inst-libc6.6-6-1.1 Investigating libapt-pkg-perl Package libapt-pkg-perl has broken dep on libapt-pkg-libc6.6-6-4.6 Considering apt 10 as a solution to libapt-pkg-perl 1 Removing libapt-pkg-perl rather than change libapt-pkg-libc6.6-6-4.6 Investigating apt-file Package apt-file has broken dep on libapt-pkg-perl Considering libapt-pkg-perl 1 as a solution to apt-file 0 Removing apt-file rather than change libapt-pkg-perl Investigating apt-listchanges Package apt-listchanges has broken dep on python-apt Considering python-apt 1 as a solution to apt-listchanges 0 Removing apt-listchanges rather than change python-apt Anyways, all I know is the order in which you upstream guys push out your new packages creates a window of a day or two where users are faced with the above painful decisions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
