I’m on the stable branch of Manjaro with kernel v.6.1.55-1 and KDE v.5.27.8. Upon running: pacman-mirrors -f5 && sudo pacman -Syyu
I’m asked if I wish to replace kirigami-addons with extra/kirigami-addons5. Whether or not I accept this change, the upgrade is failing nonetheless with a kirigami-addons5 and kirigami-addons are in conflict error.
Is that the only error message that you are getting? It sounds related to the chain of dependencies around kpeoplevcard. From the stable update announcement:
I have the same issue and it does seem to relate to kpeoplevcard
sudo pacman -R kirigami-addons
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing kirigami-addons breaks dependency 'kirigami-addons' required by colord-kde
:: removing kirigami-addons breaks dependency 'kirigami-addons' required by kdeconnect
sudo pacman -Syu kpeoplevcard
:: Synchronising package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
warning: downgrading package kpeoplevcard (0.1+r38.32d50a9-1 => 0.1-2)
:: Starting full system upgrade...
:: Replace kirigami-addons with extra/kirigami-addons5? [Y/n] n
resolving dependencies...
looking for conflicting packages...
:: kirigami-addons5 and kirigami-addons are in conflict. Remove kirigami-addons? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: kirigami-addons5 and kirigami-addons are in conflict
sudo pacman -Syuu
:: Synchronising package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
:: Replace kirigami-addons with extra/kirigami-addons5? [Y/n] n
warning: kpeoplevcard: downgrading from version 0.1+r38.32d50a9-1 to version 0.1-2
resolving dependencies...
looking for conflicting packages...
:: kirigami-addons5 and kirigami-addons are in conflict. Remove kirigami-addons? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: kirigami-addons5 and kirigami-addons are in conflict
Typing “Y” makes no difference, kirigami-addons5 and kirigami-addons are in conflict.
Just for completeness, could you show us the output from sudo pacman -Syuu when you choose Y to the question of Replace kirigami-addons with extra/kirigami-addons5?
sudo pacman -Syuu
:: Synchronising package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
:: Replace kirigami-addons with extra/kirigami-addons5? [Y/n] y
warning: kpeoplevcard: downgrading from version 0.1+r38.32d50a9-1 to version 0.1-2
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing kio5 (5.111.0-1) breaks dependency 'kio' required by kipi-plugins
:: installing kwidgetsaddons5 (5.111.0-1) breaks dependency 'kwidgetsaddons' required by kpmcore3
:: installing kcoreaddons5 (5.111.0-1) breaks dependency 'kcoreaddons' required by kpmcore3
:: installing ki18n5 (5.111.0-1) breaks dependency 'ki18n' required by kpmcore3
:: installing kxmlgui5 (5.111.0-1) breaks dependency 'kxmlgui' required by libkipi
:: installing kservice5 (5.111.0-1) breaks dependency 'kservice' required by libkipi
These are not from current Manjaro repos, but kpmcore is. I don’t know if they are needed in your case, but before updating you must remove them. In similar cases it was recommeded here to remove them with ignoring dependencies, i.e. using “pacman -Rdd”. This is not the ideal approach, but as long as no-one has a better idea, this means to run:
kipi-plugins and libkipi are still in AUR, so if ultimatively needed they could be installed from AUR. You could check upfront what packages might require them:
pacman -Qi kipi-plugins
pacman -Qi libkipi
Comunity repo has been merged with extra already a while ago, a sign you have not taken care on pacnew files.
Thanks all for your help its all better now and I can update successfully. I’ve got a laptop with the same issues and I should be able to deal with that now.
" Comunity repo has been merged with extra already a while ago, a sign you have not taken care on pacnew files."
That was helpful. I’ve setup the packnew files as described. I agree I’ve been less than attentive and I wondered what else I should be doing that I’ve missed?
pacnew files are mentioned when they are created, during updates.
You can also print them with pacdiff -o
There are also hooks and things available in the AUR.
And manjaro-pacnew-checker in the repos if you want a GUI thing.