cogset
February 14th, 2016, 07:10 PM
I shall apologize in advance for this well known question, however if I may ask: now that the time has come to move from 15.04 to 15.10 (BTW, that being the main reason why I've always used only LTS releases, i.e. I don't like frequent system upgrades... but the official Ubuntu-Mate release available was 15.04, so I went with it) how inappropriate would be to upgrade in the so called "debian way", in other words ensure that the system is currently up to date, edit the sources.list file to point to the 15.10 release, then go ahead with apt-get update followed by apt-get dist-upgrade?
You may ask why go the trouble, well I've been managing package(s) installing and upgrades from command line for a while now, so bringing up the update manager and let it do all the work looks like taking a step back to me.
I understand it does some behind-the scenes work to set things properly for a full system update, but I'd like to get more in control: of course I have a recent full-system backup already, and I have a standard installation as far as I can see, meaning no ppas have been added, no alternative kernels, no custom built packages and no packages from backports or proposed updates have been installed that I know of (at least, I've never purposely installed a package from backports with the -t vivid-backports option) .
I have however all old kernels still left behind, I should have cleaned them but I think I can still do that before the update and just leave the latest one.
If I go that route, I would of course first simulate the upgrade to check that nothing important gets removed or that some unmet dependencies get in the way - therefore, I could always put the original sources back in place and launch the update manager. Any thoughts? Any reason why that could fail and/or break the system?
You may ask why go the trouble, well I've been managing package(s) installing and upgrades from command line for a while now, so bringing up the update manager and let it do all the work looks like taking a step back to me.
I understand it does some behind-the scenes work to set things properly for a full system update, but I'd like to get more in control: of course I have a recent full-system backup already, and I have a standard installation as far as I can see, meaning no ppas have been added, no alternative kernels, no custom built packages and no packages from backports or proposed updates have been installed that I know of (at least, I've never purposely installed a package from backports with the -t vivid-backports option) .
I have however all old kernels still left behind, I should have cleaned them but I think I can still do that before the update and just leave the latest one.
If I go that route, I would of course first simulate the upgrade to check that nothing important gets removed or that some unmet dependencies get in the way - therefore, I could always put the original sources back in place and launch the update manager. Any thoughts? Any reason why that could fail and/or break the system?