[Resolved] Conflicting apt sources in Neon

I’ve been having a nightmare with dependencies since the Plasma 6 update. I’ve realized part of it is due to having both Ubuntu and Neon repositories enabled. My system was initially a Kubuntu installation, which I converted to Neon.

Here is my sources for pkcon refresh. What should be there and what should I remove to have a stable Neon system?

 Enabled                              http://us.archive.ubuntu.com/ubuntu jammy InRelease
 Enabled                              http://security.ubuntu.com/ubuntu jammy-security InRelease
 Enabled                              http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
 Enabled                              https://download.docker.com/linux/ubuntu jammy InRelease
 Enabled                              https://brave-browser-apt-release.s3.brave.com stable InRelease
 Enabled                              http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
 Enabled                              http://us.archive.ubuntu.com/ubuntu jammy InRelease
 Enabled                              https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease
 Enabled                              http://archive.neon.kde.org/user jammy InRelease
 Enabled                              http://security.ubuntu.com/ubuntu jammy-security InRelease
 Enabled                              http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
 Enabled                              https://download.docker.com/linux/ubuntu jammy InRelease
 Enabled                              https://brave-browser-apt-release.s3.brave.com stable InRelease
 Enabled                              http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
 Enabled                              https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease
 Enabled                              http://archive.neon.kde.org/user jammy InRelease

I also run a system that was Kubuntu upgraded to Neon, and it works well for me.

The first thing to note is that the base system must be jammy - which seems to be the case with your setup.

I then added a file /etc/apt/sources.list.d/neon.list with this content:

deb http://archive.neon.kde.org/release jammy main
deb-src http://archive.neon.kde.org/release jammy main

and that should be it.

I don’t use Ubuntus/Debians as main to know much, but I think having jammy-backports there doesn’t sound like a good idea. Maybe OP has to revert all versions to jammy first before using the Neon repositories. Probably using some more advanced apt syntax giving higher priorities or something. To me this looks rather messy.

By default jammy-backports has a lower priority in (K)ubuntu than the rest (100 instead of 500) and therefore nothing will be installed from there and it should not interfere with neon.
Unless one explicitly installs packages like LibreOffice from there with apt install <package_name> -t jammy-backports (to get a more recent LO version - 7.6.5 instead of 7.3.7 - like people can do in (K)ubuntu 22.04 LTS), it should do no harm.

That said I suggest the OP removes it as it is not one of the repositories that KDE neon uses by default but a remaining one from Kubuntu - or at least check the priorities with apt policy

By the way: from the KDE neon FAQ - Can I turn Kubuntu into KDE neon with a PPA?

We recommend that you install a fresh KDE neon from the provided ISO images. But you can indeed add an APT repository to switch from Kubuntu to KDE neon. This is absolutely not tested or supported. If things take a turn for the worse you are expected to be knowledgable enough to repair your system on your own. A web search should quickly give you relevant information on how to do this.

Thanks all for the responses. I managed to get it fixed a couple of hours ago.

First thing I did was manually install the unmet dependencies. I did this by using pkcon install package --allow-reinstall. This told me that there were different versions of the packages available and allowed me to pick the correct one. After that I did an apt update, pkcon refresh and pkcon update and all packages installed except libkcolorpicker0. That issue is being tracked as KDE Bug 484940 and I managed to resolve it with dpkg --remove --force-remove-reinstreq libkcolorpicker0 and then re-running pkcon update.

I definitely think the unmet dependencies issue I was seeing has something to do with source priority, because when I used the allow-reinstall option I could pick the version I wanted. So it seems all versions were available, but the defaults were just wrong.

@schwarzerkater as for updating from Kubuntu. I had my current installation of Kubuntu for about 5 years before updating to KDE Neon a couple of years ago and didn’t want to do a reinstall at that time since my system has been configured perfectly for my needs over many years :smiley:

1 Like