I guess I could uninstall NextCloud to see if this resolves the issues, but why does one dependency or update issue result in a total inability to update at all? Either with Shelly or CachyOS-Update. Details below.
This borders on a DoS issue and break the ability to update at all!
There is a Shelly update in the queue which won’t now install until this is resolved. I am on Kernal 7.1 and KDE Plasma 6.7, if that might be part of this issue.
Kind Regards
Simon Zerafa
Errors messages from CachyOS-Update.
warning:valkey: local (9.1.0-1.1) is newer than cachyos-znver4 (9.1.0-1) resolving dependencies... looking for conflicting packages... error:failed to prepare transaction (could not satisfy dependencies) :: installing nextcloud (34.0.0-1) breaks dependency 'nextcloud<34' required by nextcloud-app-tasks
I managed to do CLI updates of everything that was outstanding as of this morning, using pacman.
However, the Nextcloud apps and modules refuse to update due to dependency issues.
Not sure which other packages were causing issues from Shelly or CachyOS-Update, but something is the queue was buggering up the installation process for everything else.
Kind Regards
Simon Zerafa
Additional: After some more poking about I did the following:
As you can see in your output in the first post, nextcloud is being attempted to update to 34.0.0-1, which as you can see is a brand new version number, and nextcloud-app-tasks is hard requiring “nextcloud<34” or less than version 34.
The most likely culprit here is that the package maintainer needs to rebuild the package so that it’s properly inline with the rest of the Nextcloud suite in being allowed to requirenextcloud version 34.
And when we look at the Arch Linux code page for the package:
We can see that is indeed the case:
Basically, the package needs to be rebuilt and uploaded to Arch’s extra repo. This is something that you can either go through the steps to point this out to them manually(open an issue on the Arch GitLab for the package) or you can just wait for them to figure it out in a few hours or days.
The update process doesn’t allow partial upgrades to protect your system from unnecessary breakage. The native repositories are generally quick or instantaneous to sync package requirements up with each other but the occasional desync isn’t unheard of.
As with many update issues, “wait and update again a little later” is usually the right play.