Page 1 of 1
Upgrade of Ubuntu wants to remove sabnzb
Posted: June 17th, 2017, 3:13 pm
by knelmes
Hi
I have sabnzb installed on Ubuntu server 16.10 via the jcfp ppa from the nobeatas channel (currently 2.1.0 [443efb5]). I'm trying to upgrade to Ubuntu 17.04 but when I try (via do-release-upgrade) it says it's going to uninstall sabnzbdplus.
First of all it says "1 package is going to be removed"
When I press 'd' for details it tells me that package is sabnzbdplus
I have screenshots but I'm not allowed to post links.
It doesn't seem to give any reasons why it wants to remove it. Anyone know what's going on?
Re: Upgrade of Ubuntu wants to remove sabnzb
Posted: June 17th, 2017, 4:24 pm
by knelmes
Hmm, I think the same thing happened to spanky85 in thread 22699 but he didn't notice the message, it was just uninstalled after the upgrade. He managed to just reinstall it afterwards. If no one has any ideas I might just try that.
Re: Upgrade of Ubuntu wants to remove sabnzb
Posted: June 17th, 2017, 5:00 pm
by safihre
From what I understand (not the expert): external PPA's get removed on such a major upgrade. You'll have to readd after it's upgraded.
I think this is a safeguard of the system since they can't verify external packages if they are suited for the new OS release.
Re: Upgrade of Ubuntu wants to remove sabnzb
Posted: June 17th, 2017, 5:20 pm
by knelmes
I have other external PPAs and it wants to disable them but it only want to uninstall sabnzb, not the other programs installed from external ppas.
Re: Upgrade of Ubuntu wants to remove sabnzb
Posted: June 18th, 2017, 7:23 am
by knelmes
Figured I'd give it a try (with a checkpoint in place in case it all went wrong) and it's fine.
After upgrade, re-add sab PPA (and the addons PPA if previously added) and install sabnzbdplus as normal. All fine and dandy.
Like I said, I've got another PPA (deluge) that got disabled but it didn't remove deluge itself. Shrug
Re: Upgrade of Ubuntu wants to remove sabnzb
Posted: June 18th, 2017, 11:29 pm
by jcfp
No need to worry. As safihre correctly mentioned ppas get removed by the upgrade handler; but not the package(s) installed from there. That leaves a package tailored to your old ubuntu release still installed when the upgrade starts, while there may not be version as new available from the official repositories. Most times you wouldn't even notice but in case the dependencies of that package cannot be met on the new ubuntu release, that temporarily forces its removal until you re-add the ppa afterwards - this time targeting the freshly upgraded ubuntu release so it magically installs just fine again.