Hi Tomas, Great you like it! Many people are busy working on smoothing the edges uncovered by all the inflowing bugreports, so the occasional "thanks!" is a nice boost to troop morale. :)
On Thu, Nov 27, 2014 at 02:22:14PM +0100, Tomas Pospisek wrote: > Allthough apt-get dist-upgrade broke half way through due to > unresolvable package dependencies, I was able to finish the upgrade via > aptitude's ncurses interface. Please lookup /var/log/apt/term.log and report a bug about the specific failure you see in there. I presume some maintainerscript is failing, preventing configuration of something which ultimately lets dpkg fail with an unresolved dependency error as the package is arguable not correctly installed… Your system state before the upgrade might be of interest to: You can find a backup of it in /var/backups. One of the files names "dpkg.status" with an 'old-enough' date will be it. Note that if apt-get failed "half way through" in the upgrade, aptitude more than likely would have failed just as well as the code running the installation process is shared. The difference between the two is "just" UI and dependency resolution before you press 'y'. Everything after that like the download, consistency check or the installation is the same… It's also not the worst idea to remove stuff from third party repositories before upgrading and only install them again after the upgrade. This way you can sure that they aren't interfering (something which can't be prevented and just works most of the time because you are lucky) and you can recheck that the 3rd party repository is still maintained/supported or if this or a comparable package appeared in Debian. If not, you should think about getting it into Debian… btw: apt-get is actually recommend for dist-upgrade as it is requiring less knowledge than the operation of aptitude. The later can also be a bit unpredictable in its resolution process, which has its advantages in day to day usage maybe with small solutions, but most people don't second-guess solutions involving >=2000 packages and just press 'y'… Point being: If apt-get doesn't work we ought to know so that can be solved one way or the other, but flipping package manager is unlikely to be the way at this stage. [Disclaimer: I (hopefully) don't say that only because I work on apt] Best regards David Kalnischkies P.S.: Despite many people believing it: -f isn't short for --force, but for --fix-broken. It can work on dist-upgrade, but it is probably better you just run "apt-get install -f" instead as adding new problems on top of the existing ones is usually not a good way forward…
signature.asc
Description: Digital signature
