I want to try the new Plasma 6 beta so I followed the instructions on the Arch wiki on how to enable the kde-unstable repo and tried to update the system, but when I try pacman says “plasma-activities and kactivities are in conflict”, both are required by some of the packages that it’s trying to update and there’s no way to ignore the conflict.
Does anyone know how to install it?
You can do
sudo pacman -Syudd
where thedd
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 todolphin-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
andextra-testing
repos in addition tokde-unstable
as per the wikiI 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 withyay plasma
and then choose the ones from kde-unstable (122-194 for me) but you will have to manually avoid the ones with conflicts likeplasma-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:
Your Update likely removed these from your system breaking plasma6
The following packages are likely to blame (this list is likely incomplete):
Edit: if you have terminal access you can try the following (no guarantee it’ll work, I think it should but no guarantees):
What I did (switch to plasma 5 versions):
What you could do (switch to 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
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)