If you followed the wiki, I'd just try again tomorrow and hope the maintainers have resolved the conflict by then. These are the issues you run into with unstable repos.
this post was submitted on 30 Nov 2023
13 points (93.3% liked)
Linux
48214 readers
711 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
You can do sudo pacman -Syudd where the dd is for ignoring dependencies to force it through. But be aware this is basically asking for things to break. Some packages haven't been updated to the latest versions yet. For example dolphin wouldn't launch so I had to switch to dolphin-git from the AUR.
I'm very happy to inform you that I broke my system
As long as you still have access to the cli it should be fixable. If you want to still try to get to plasma 6 make sure you also enabled the core-testing and extra-testing repos in addition to kde-unstable as per the wiki
If you enable any other testing repository listed in the following subsections, you must also enable both core-testing and extra-testing
I missed that little snippet when I first swapped over.
If you do yay kf6 you can install all of the framework-related packages which might also help fill out some missing dependencies. For me it's 1-71. You can do the same with yay plasma and then choose the ones from kde-unstable (122-194 for me) but you will have to manually avoid the ones with conflicts like plasma-framework.
But if you want to try and revert theoretically simply removing the testing and unstable repos and doing another sudo pacman -Syu should get you back onto the older versions.
It's ok, I did a backup with clonezilla before trying it of course :) But thanks for the help
Hopefully helpful:
you need the following packages for kde-unstable:
- plasma-activities
- plasma-activities-stats
- libplasma
Your Update likely removed these from your system breaking plasma6
The following packages are likely to blame (this list is likely incomplete):
- kweather (I removed it since I don't use it)
- dolphin (as suggested above switching to dolphin-git should help, alternatively installing extra/dolphin will install the plasma 5 version bypassing the dependency problems)
- kio-extras (same fix as for dolphin)
- sweeper (see above)
Edit: if you have terminal access you can try the following (no guarantee it'll work, I think it should but no guarantees):
- pacman -Rdd kactivites kactivites-stats plasma-framework
- pacman -Syudd libplasma plasma-activities plasma-activities-stats
What I did (switch to plasma 5 versions):
- pacman -Syudd extra/dolphin extra/sweeper extra/kio-extras extra/kweather
What you could do (switch to git):
- $AUR_HELPER -Syu dolphin-git sweeper-git kio-extras-git kweather-git
Update: the bad packages got updated, you should be fine just installing them from kde-unstable again
Wow, that is incredibly unfortunate timing.
cosmically unfortunate timing, package maintainer probably just took a nap between updating most packages and fixing the leftovers and the resulting gap caused this mayhem
It's called kde-unstable for a reason! ;) Packaging issues are expected to happen as it's where the maintainer irons out the issues.
I would definitely recommend against -Syudd with kde-unstable, the packages can change drastically (as was the case here) breaking the entire system if dependencies are ignored (as happened here)