You are not logged in.
Hi!
What are "inner" conflicts and how can I resolve them? Admittedly this is on a system that hasn't been updated in a long time.
Is it possible to force the updates, break parts of the system and then fix dependencies in a 2nd step?
Prior to Plasma 6 the preceding, ordinary conflict checking already failed.
# yay -Syuw --noconfirm
...
:: Checking for conflicts...
:: Checking for inner conflicts...
-> Inner conflicts found:
-> sdl12-compat: sdl
-> Package conflicts found:
-> Installing at-spi2-core will remove: at-spi2-atk (at-spi2-atk<=2.38.0-2), atk (atk<=2.38.0-2)
-> Installing libplasma will remove: plasma-framework
-> Installing kate will remove: kwrite
-> Installing plasma-activities will remove: kactivities
-> package conflicts can not be resolved with noconfirm, aborting
# yay -Qi plasma-framework kactivities at-spi2-atk atk | egrep '^(Name|Version)'
Name : plasma-framework
Version : 5.91.0-1
Name : kactivities
Version : 5.91.0-1
Name : at-spi2-atk
Version : 2.38.0-1
Name : atk
Version : 2.36.0-1
thx
tcn
Offline
Use pacman for system updates.
Offline
https://github.com/Jguer/yay/issues/673
> package conflicts can not be resolved with noconfirm, aborting
Cause is gonna be the kde6 shift, but that's irrelevant.
Last edited by seth (2024-03-18 08:12:59)
Offline
Mod note: moving to AUR Issues
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Get rid of yay. Really. Not only is that most of the problem here - it has also prevented you from understanding the most basic functions of your package manager. There is no reason to pipe -Qi output through grep to get the name and version, just use -Q properly in the first place: it shows just the package name and version!
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline