Testing to Stable

[Don B. Cilly]

And the new code keeps protesting.
Neon Testing,
Needs a shove.

--- Wire States - Tunnel of Code

I'm running neon Testing, for which I really have no use any more.
I'd like to know, if I just change my repositories to the "stable" ones, would I effectively be on Stable from then on?

And which ones would they be?

[acheron]

'Testing' is effectively just the new name for what 'stable' was. IIRC the stable repo urls just redirect or symlink or something similar to the testing ones now.

[claydoh]

Do you mean going from Testing (formerly called Dev-stable) to User Edition?

technically, the switch involves editing /etc/apt/sources.list.d/neon.list to replace 'testing' with 'user', then update normally.

however, it is unknown what packaging conflicts (if any) might occur. At least, it is highly likely that you won't see any updates on your system until the packaging from User has a higher value than what you have now, so you may not see many updates up front.

I am updating a sacrificial machine in virt-manager to see what might go boom....

[Don B. Cilly]

Very good. Just, [from apt update, ignoring 3rd party ones] I have these repos enabled:

es.archive.ubuntu.com/ubuntu bionic InRelease
es.archive.ubuntu.com/ubuntu[/url] bionic-updates InRelease
es.archive.ubuntu.com/ubuntu[/url] bionic-backports InRelease
security.ubuntu.com/ubuntu[/url] bionic-security InRelease
archive.neon.kde.org/testing[/url] bionic InRelease

/etc/apt/sources.list.d/neon.list only has
archive.neon.kde.org/testing bionic main

So, change the "testing" one to "user"?
And remove the "backports" one?

I probably won't bother, just curious ;·)

[claydoh]

The backports won't affect neon packaging, so disabling that is up to you. probably a safe bet to do so for the time being, if you are going to go this route.

And, yes change 'testing' to 'user'

Okee dokeee the clipboard in my VM does not work, so here is a pic of the output till I get the text onto a flash drive, if I find one




nothing much going on here. nothing that breaks anything, for sure. But as I expected, it will stay at the current version until User gets a new version of Plasma, Applications, or Frameworks.
It seems neon uses the backports pocket, so it should not be an issue.

[claydoh]

neontesting@neontesting-Standard-PC:~$ sudo apt update       
[sudo] password for neontesting: 
Hit:1 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease          
Hit:3 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease    
Hit:4 http://security.ubuntu.com/ubuntu bionic-security InRelease                      
Get:5 http://archive.neon.kde.org/user bionic InRelease [131 kB]                       
Fetched 131 kB in 1s (120 kB/s)    
Reading package lists... Done
Building dependency tree       
Reading state information... Done
16 packages can be upgraded. Run 'apt list --upgradable' to see them.
neontesting@neontesting-Standard-PC:~$ sudo apt full-upgrade 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libkf5parts-plugins phonon4qt5
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
  base-files flatpak geoclue-2.0 libflatpak0 libkdsoap-common libkdsoap1 neon-adwaita
  neon-apport neon-hardware-integration neon-keyring neon-settings
  neon-ubuntu-advantage-tools phonon4qt5-backend-vlc python3-distupgrade
  ubuntu-release-upgrader-core ubuntu-release-upgrader-qt
16 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 2,189 kB of archives.
After this operation, 80.9 kB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
neontesting@neontesting-Standard-PC:~$

[Don B. Cilly]

Thank you

[Don B. Cilly]

OK. So, I backed up, then updated normally.
apt list --upgradable returned <empty>.

Then changed the repo to "user".
Did sudo apt update.
apt list --upgradable showed 16 packages.

Tried apt full-upgrade. (Hey, at least I can play with my little update script a bit :·)

The following packages will be upgraded:
base-files flatpak geoclue-2.0 libflatpak0 libkdsoap-common libkdsoap1 neon-adwaita neon-apport neon-hardware-integration
neon-keyring neon-settings neon-ubuntu-advantage-tools phonon4qt5-backend-vlc python3-distupgrade
ubuntu-release-upgrader-core ubuntu-release-upgrader-qt

Said: "not right now thanks".
Before I say "go ahead"... a few of those look vaguely... suspicious :·)
Details from apt list --upgradable :

base-files/bionic 10.1ubuntu2.8+p18.04+git20200414.1528 amd64 [upgradable from: 10.1ubuntu2.8+p18.04+git20200409.1229]
flatpak/bionic 1.6.2-1+18.04+bionic+build5 amd64 [upgradable from: 1.6.2-1+18.04+bionic+build4]
geoclue-2.0/bionic 2.5.5-1+18.04+bionic+build2 amd64 [upgradable from: 2.5.5-1+18.04+bionic+build1]
libflatpak0/bionic 1.6.2-1+18.04+bionic+build5 amd64 [upgradable from: 1.6.2-1+18.04+bionic+build4]
libkdsoap-common/bionic,bionic 1.9.0-0xneon+18.04+bionic+build15 all [upgradable from: 1.9.0-0xneon+18.04+bionic+build8]
libkdsoap1/bionic 1.9.0-0xneon+18.04+bionic+build15 amd64 [upgradable from: 1.9.0-0xneon+18.04+bionic+build8]
neon-adwaita/bionic,bionic 0.0+p18.04+git20180904.1047 all [upgradable from: 0.0+p18.04+git20180904.0651]
neon-apport/bionic,bionic 0.0+p18.04+git20180904.1047 all [upgradable from: 0.0+p18.04+git20180904.0651]
neon-hardware-integration/bionic,bionic 0+p18.04+git20180904.1047 all [upgradable from: 0+p18.04+git20180904.0651]
neon-keyring/bionic,bionic 2016.06.06+p18.04+git20180904.1047 all [upgradable from: 2016.06.06+p18.04+git20180904.0651]
neon-settings/bionic,bionic 0.0+p18.04+git20200211.1410 all [upgradable from: 0.0+p18.04+git20200211.1410]
neon-ubuntu-advantage-tools/bionic,bionic 0.0+p18.04+git20180904.1047 all [upgradable from: 0.0+p18.04+git20180904.0651]
phonon4qt5-backend-vlc/bionic 0.11.1-0xneon+18.04+bionic+build14 amd64 [upgradable from: 0.10.1+p18.04+git20180526.0111-0]
python3-distupgrade/bionic,bionic 1:18.04.37+p18.04+git20200414.1530 all [upgradable from: 1:18.04.37+p18.04+git20200410.0254]
ubuntu-release-upgrader-core/bionic,bionic 1:18.04.37+p18.04+git20200414.1530 all [upgradable from: 1:18.04.37+p18.04+git20200410.0254]
ubuntu-release-upgrader-qt/bionic,bionic 1:18.04.37+p18.04+git20200414.1530 all [upgradable from: 1:18.04.37+p18.04+git20200410.0254]

Well, not quite suspicious, but... ubuntu-release-upgrader-core, python3-distupgrade, neon-hardware-integration, and such, look... well, pretty major.
What do y'all think? As The Clash would say... "Should I stay or..."

[claydoh]

No these are not actually major. updates. I got most of the neon-specific ones a week ago.

The updater related packages are because they use Ubuntu's software, so whenever there is a change there, Neon's needs to be modified to match, partly to keep from getting upgrade notifications a bit too early

[Don B. Cilly]

OK, great. I'll go then. Probably tomorrow morning

[Don B. Cilly]

So I updated. Rebooted to see what would happen.
No BOOM (so far :·) but, automagically:

~$ lsb_release -d
Description: KDE neon User Edition 5.18

[Don B. Cilly]

... ...