Page 1 of 1

FYI: "disabled on upgrade to trusty"

Posted: November 17th, 2014, 6:55 am
by sander
A a FYI:

I discovered SABnzbd on my Ubuntu VPS was still on 0.7.18. I then found the reason:

Code: Select all

$ grep -ir jcfp /etc/apt/*
/etc/apt/sources.list:# deb http://ppa.launchpad.net/jcfp/ppa/ubuntu trusty main # disabled on upgrade to trusty
/etc/apt/sources.list.d/jcfp-ppa-precise.list:# deb-src http://ppa.launchpad.net/jcfp/ppa/ubuntu trusty main # disabled on upgrade to trusty
/etc/apt/sources.list.d/jcfp-ppa-precise.list.save:# deb-src http://ppa.launchpad.net/jcfp/ppa/ubuntu trusty main # disabled on upgrade to trusty
/etc/apt/sources.list.d/jcfp-ppa-precise.list.distUpgrade:deb-src http://ppa.launchpad.net/jcfp/ppa/ubuntu precise main
/etc/apt/sources.list.distUpgrade:deb http://ppa.launchpad.net/jcfp/ppa/ubuntu precise main
/etc/apt/sources.list.save:# deb http://ppa.launchpad.net/jcfp/ppa/ubuntu trusty main # disabled on upgrade to trusty
"disabled on upgrade to trusty"? Ah, great. >:(
I removed the comment-hash from /etc/apt/sources.list, and ran update/upgrade:

Code: Select all

The following packages have been kept back:
  sabnzbdplus sabnzbdplus-theme-classic sabnzbdplus-theme-plush
  sabnzbdplus-theme-smpl
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
A dist-upgrade solved that: sabnzbdplus-0.7.20RC2

Re: FYI: "disabled on upgrade to trusty"

Posted: November 17th, 2014, 8:56 am
by jcfp
sander wrote:"disabled on upgrade to trusty"? Ah, great. >:(
It's update-manager doing that, probably trying to lower the risk of repos other than the official ones interfering with os upgrades. Unfortunately, there's no reminder to re-enable after completing the upgrade... :-\
sander wrote:The following packages have been kept back:
Welcome to 'apt-get upgrade' being (overly) cautious. Or as its manpage puts it: under no circumstances are currently installed packages removed, or packages not already installed retrieved and installed - which can be triggered by something as simple and harmless as adding or promoting a dependency. No such restrictions with dist-upgrade.

Re: FYI: "disabled on upgrade to trusty"

Posted: November 17th, 2014, 9:38 am
by sander
Thank you for your explanation. We're in sync.