Control: severity -1 normal Control: tags -1 - d-i Hi Richard,
On Mon, Sep 30, 2013 at 11:31 AM, richard <rich...@mail.sheugh.com> wrote: > Subject: apt: Apt fails in upgrade to jessie when setting up upower (0.9.21-3) > Package: apt > Version: 0.9.9.4 > Justification: Policy 2.5 Priorities required > Severity: serious > Tags: d-i huh? Have you copied this from somewhere? I at least don't see the seriousness and have absolutely no idea where would we violate §2.5 or effect d-i, hence downgrade to normal for now. > I was in the process of upgrading from “stable” to “testing” (jessie) and > apt-get dist upgrade informed me that the upgrade could not proceed because of > package conflicts. I then began, using dselect and apt-get, to upgrade > selected > packages, beginning with required. At some point in the process apt broke, > leaving the upgrade in a locked condition. If its the same I experienced yesterday the upower thingy froze and did nothing anymore. Interestingly, killing upower mad the upgrade proceed without any further complain. I was a bit surprised, but had to carry on, so did no further investigation on that front. > This appears to be related to bug #722612 but as apt said to report this bug > against apt, that is where it is filed. In a way. term.log looks like you managed to interrupt the upgrade completely, so you have (potentially) a lot of half-configured packages on your system. APT isn't tested in those situations a lot as it depends on other packages being buggy enough to interrupt the upgrade (and autoremove isn't exactly the first step you should do to fix the situation). Would be nice if you could upload/attach/sent the following to files two the bugreport (or me only, they include information about what packages you have installed in which version on your system): /var/lib/apt/extended_states /var/lib/dpkg/status After you have saved the files, you should be able to fix your system with dpkg --configure --pending And after that repeating the APT command which failed for you, e.g. apt-get dist-upgrade to finish whatever is left to do to comply with the request. > # apt-get autoremove && apt-get clean && apt-get autoclean Pro-tip: There is no point in calling "clean" and "autoclean" together, as "clean" will delete every already downloaded *.deb file, while "autoclean" will only delete does which can't be downloaded anymore; so choose whatever you prefer instead of calling both needlessly. And frankly, "autoremove" is a command which requires the user to check if the packages considered for autoremove are really okay to be removed, as its a guess, no a definite knowledge. The stuff deleted by the clean commands on the other hand is really not needed anymore and/or is redownloaded by APT automatically if it needs it. So, I wouldn't run them together as they don't belong together. Best regards David Kalnischkies -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
