Hi,
Plasma 5.8.9 packages for xenial are available in backports-landing. I tested dist-upgrades and everything seems ok, so it would be nice to move this packages to the regular backports PPA soon.
Cheers.
Hi,
Plasma 5.8.9 packages for xenial are available in backports-landing. I tested dist-upgrades and everything seems ok, so it would be nice to move this packages to the regular backports PPA soon.
Cheers.
full-upgrade -y gave me 84 packages to update after the final XX release candidate. Looked clean in konsole. After a re-booting my VM,
Big Bright Blue SDDM screen.
But, I seemed to have lost the default wall paper, and the panel tray seemed pushed to the left instead of its usual position on the right.
In the panel tray, it said I had updates, but clicking on the shield I got:
Error loading QML File: file (long path here) org.kde.discovernotfier is not installed.
Alt F1 gives me a similar message:
Error loading QML File: file (long path here) org.kde.private.kicker is not installed.
But Alt F2 gives me krunner. And it launches konsole just fine. And I find some packages are held back.
$ sudo apt update && sudo apt full-upgrade -y [sudo] password for mparillo: Hit:1 http://security.ubuntu.com/ubuntu xenial-security InRelease Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease Hit:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease Hit:5 http://ppa.launchpad.net/kubuntu-ppa/backports-landing/ubuntu xenial InRelease Reading package lists... Done Building dependency tree Reading state information... Done 52 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: muon-notifier muon-updater ubuntu-release-upgrader-qt Use 'sudo apt autoremove' to remove them. The following packages have been kept back: kde-cli-tools-data kwin-data libkf5sysguard-data muon-notifier muon-updater plasma-desktop-data plasma-discover-common 0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Is it possible I need to install backports first, and only then install backports-landing?
Tested upgrade from stock 16.04.4 in a VM to backports, then bp-landing. Plus the same but in one go.
No obvious issues. Could not replicate mparillo's problems.
Hi Marco,
I couldn't reproduce the possible issues you have described. However, a test like yours, just adding backports-landing could be flawed (see below).
Is it possible I need to install backports first, and only then install backports-landing?
They are 2 possible upgrade paths:
a) upgrading from a 'plain' xenial installation, i.e. without backports
b) upgrading from a xenial installation where you already have backports, i.e. plasma 5.8.8 among other things
If you are testing the upgrade path a), and it seems to me that's what you are doing, the correct way to proceed is:
The reason to do this is that backports might have packages that backports-landing isn't providing, and that could explain that packages being held back.
Regards.
I confirmed that adding backports, update, full-upgrade, makes backports-landing work, even if backports are added after backports-landing.