sudo apt-get update && \ sudo apt-get install apt dpkg locales && \ sudo apt-get --purge dist-upgrade && \ sudo apt-get --fix-policy install && \ sudo apt-get --purge autoremove $(deborphan --guess-all)
I guess I'll be busy filing bug reports for the next few hours. Wish me (and each faulty package's maintainer) luck!
PS: Apparently, so many aspects of Debian have become dependent upon GPG features that merely upgrading APT, DPKG and libc6+locales is no longer enough. One must also upgrade gnupg and gnupg2. Thus, the second element of the above recipe has become:
sudo apt-get install apt dpkg gnupg gnupg2 locales && \
Hopefully, APT's dist-upgrade command already knows that these must be upgraded first...
PPS: Hosts running Network-Manager cannot be upgraded remotely, because Network-Manager insists upon killing the network connection and the SSH daemon with it, when its turn comes to get upgraded.
4 comments:
I don't understand your remark about gnupg/gnupg2. I'm not aware of any signigicant change in GnuPG 1.4 between wheezy and jessie that relates to APT. Can you clarify what problem you're talking about exactly?
I wasn't talking about APT internals.
Some packages completely failed to upgrade until gnupg or gnupg2 (depending on which package we're talking about) had been upgraded. I had to manually do 'sudo dpkg -i /var/cache/apt/archives/*gnupg*' before I could execute 'sudo dpkg -a --configure' and then again 'sudo apt-get dist-upgrade' to continue the upgrade.
Basically, due to so many packages not being able to configure until gnupg/gnupg2 have been configured, I would hope that APT would unpack and configure gnupg/gnupg2 as early as possible upon a dist-upgrade.
So what is it exactly that fails in these packages?
Post a Comment