KDE Framework update 5.111 fails

Desktop Environments Plasma
1

As with today’s “yay” KDE framework got an update to 5.111. In preparation to plasma6 some packages seem to have a “5” appendix like kcrash5 instead of kcrash, etc. Now wothh this update I got some errors and update failed:

Fehler: Vorgang konnte nicht vorbereitet werden (Kann Abhängigkeiten nicht erfüllen)
:: Installation von kiconthemes5 (5.111.0-1) verletzt Abhängigkeit »kiconthemes«, benötigt von isoimagewriter
:: Installation von kcrash5 (5.111.0-1) verletzt Abhängigkeit »kcrash«, benötigt von isoimagewriter
:: Installation von solid5 (5.111.0-1) verletzt Abhängigkeit »solid«, benötigt von isoimagewriter
:: Installation von plasma-framework5 (5.111.0-1) verletzt Abhängigkeit »plasma-framework«, benötigt von plasma5-wallpapers-xml
:: Installation von knewstuff5 (5.111.0-1) verletzt Abhängigkeit »knewstuff«, benötigt von plasma5-wallpapers-xml
:: Installation von plasma-framework5 (5.111.0-1) verletzt Abhängigkeit »plasma-framework«, benötigt von plasmoidviewer-debug
 -> error installing repo packages

Any suggestions / anyone else? Wait one or two days? I haven’t seen a bugreport yet. I guess it needs to be created @kde project, not here?

2

Those packages for which the dependency will be broken by the update seem to come from AUR.

They need to be rebuild to match the new dependencies.

I think you might need to remove them first update your system and hopefully they will build against the new packages again.

For what is worth, prefixing the command with LANG=C will output the text in English.

3

LANG=C prefix hint is very helpful. Thanks!
I’ll remove the mentioned packages first…

4

Tip: if AUR packages cause issues like this, one can update all non-AUR packages first (so that system packages get updated):

sudo pacman -Syu && yay
5

I have to remove lightly-git and klassy-window-decorations . After that the update is going well.

Hopefully they rebuild to match the dependencies. Just lightly is a very nice addition for Breeze. I could do without klassy

6

See if editing the PKGBUILD at

depends=

and changing the name of the relevant dependencies to the new ones will get it to build.

7

thank you very much, i will have a look at it again and again. As soon as it has been changed i can do an installation again

8

For me, the list of packages that break the update is much longer and apparently includes non-AUR packages as well. In such cases, I think it is best to wait, because I think it is not advisable to remove so many packages from the system in order to avoid breaking the dependency.

resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing kiconthemes5 (5.111.0-1) breaks dependency 'kiconthemes' required by isoimagewriter
:: installing kcrash5 (5.111.0-1) breaks dependency 'kcrash' required by isoimagewriter
:: installing solid5 (5.111.0-1) breaks dependency 'solid' required by isoimagewriter
:: installing kholidays5 (1:5.111.0-1) breaks dependency 'kholidays' required by kalarmcal
:: installing kxmlgui5 (5.111.0-1) breaks dependency 'kxmlgui' required by kfloppy
:: installing kcompletion5 (5.111.0-1) breaks dependency 'kcompletion' required by kfloppy
:: installing kcoreaddons5 (5.111.0-1) breaks dependency 'kcoreaddons' required by libmediawiki-git
:: installing knotifications5 (5.111.0-1) breaks dependency 'knotifications' required by telepathy-kde-approver
:: installing kservice5 (5.111.0-1) breaks dependency 'kservice' required by telepathy-kde-approver
:: installing knotifyconfig5 (5.111.0-1) breaks dependency 'knotifyconfig' required by telepathy-kde-common-internals
:: installing ktexteditor5 (5.111.0-1) breaks dependency 'ktexteditor' required by telepathy-kde-common-internals
:: installing kpeople5 (5.111.0-1) breaks dependency 'kpeople' required by telepathy-kde-common-internals
:: installing krunner5 (5.111.0-1) breaks dependency 'krunner' required by telepathy-kde-contact-runner
:: installing kidletime5 (5.111.0-1) breaks dependency 'kidletime' required by telepathy-kde-integration-module
:: installing kactivities5 (5.111.0-1) breaks dependency 'kactivities' required by telepathy-kde-integration-module
9

If they are from AUR, they are build against the now obsolete version of their dependencies which need to be updated.

Not removing them won’t resolve this issue. You need to remove them, update the system and rebuild them again against the updated version of their dependencies. Otherwise they will hold up updating your system for as long as you keep them.

If they are installed from a third party repo, the maintainer of the repo will have to address the issue.

10

Same problem here.
They are official packages from Arch (KDE stuff), not AUR.

11

Please start a new thread and post the full output of sudo pacman -Syu.

12

In the meantime, I found something else that might be useful. It’s interesting that it didn’t happen on all my installed EOS.

https://bbs.archlinux.org/viewtopic.php?id=289694

P.S. One last question. Won’t these telepathy packages, which are no longer maintained and are now removed from the system, still be missing later for some purpose? I reinstalled the isomimagewriter package because its last update date was the day before yesterday. I also checked the other removed packages one by one. Among those in the AUR, there were some whose last update was three years ago, i.e. they are orphaned.

13

Being from AUR, they are certainly not “system critical” packages.

You should know yourself for what purpose you have installed them at the first place.

14

Obviously, among these there were those that were installed as part of a package group or as a dependency of another package, not specifically manually.

15

Could be.

However none of the packages or package groups from repos have dependencies on AUR packages.

So you must have installed something from AUR, manually, which, obviously, was dependendent on something else from AUR.

16

I don’t really use AUR. In four years, I installed maybe three applications from here. Rather, it may be that there are packages that have been removed from the official repositories and moved to the AUR. We have already seen an example of this.