Skip to main content ↑ ↓
Topic: thrown off by *pacman -Su* behavior (Read 549 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

thrown off by *pacman -Su* behavior

I had what I thought was a nicely running Artix installation that I boot once a week. Don't know when I signed up but I've been doing it since about that time while also doingan update on almost every occasion. But a few weeks ago my update attempt started reeling in promts like these, quite a few in fact

Code: [Select]
:: Starting full system upgrade...
:: Replace attica with world/attica5? [Y/n] 
:: Replace baloo with world/baloo5? [Y/n] 
:: Replace bluez-qt with world/bluez-qt5? [Y/n]

If I just hit RET for the default YES each time it ends with

Code: [Select]
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing kxmlgui breaks dependency 'kxmlgui' required by libkipi
:: removing kservice breaks dependency 'kservice' required by libkipi
:: installing libpamac (11.6.2-1.1) breaks dependency 'libpamac<11.5' required by pamac-cli
:: installing libpamac (11.6.2-1.1) breaks dependency 'libpamac<11.5' required by pamac-gtk

OK, not the end of the world if it's just 2 unresolvables, I can wait for the next update. If on the other hand I answer with "n" each time then I end up with

Code: [Select]
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: kitemmodels5 and kitemmodels are in conflict (kitemmodels<5.111)


So now I'm starting to worry, should I?  What to do (as a regular beginner)?  I could just re-install with a new KDE image but I'm not really looking forward to that on account that it takes a day to repeat the setup necessary after an install. I do have a backup image made about 2 weeks ago but it could be that that one already had this problem.

TIA

Who, has loved us more?

Re: thrown off by *pacman -Su* behavior

Reply #1 –
Code: [Select]
pacman -Su
should probably be replaced with
Code: [Select]
pacman -Syu
The first is not updating the pacman database.

Looking at your output what I would suggest as the safest solution is removing pamac-cli & pamac-gtk
Code: [Select]
pacman -R pamac-cli pamac-gtk
updating and then installing them again if required.

What there's a good chance I would actually do is add the option to the pacman command to ignore dependencies and see what happens. But I'd do that safe in the knowledge that if things go tits up I take daily incremental backups of my root partition and can easily revert to yesterdays if need be. If it seemed fine I'd then update  pamac-cli pamac-gtk if, as I suspect, they are AUR packages.

Edit:
Your second approach of answering 'n' is almost never going to be a good, or workable, idea. If the packages have new names you have to accept that or basically never update your system again.

Re: thrown off by *pacman -Su* behavior

Reply #2 –
Quote from: gripped – on
Code: [Select]
pacman -Su
should probably be replaced with
Code: [Select]
pacman -Syu
The first is not updating the pacman database.

Looking at your output what I would suggest as the safest solution is removing pamac-cli & pamac-gtk
Code: [Select]
pacman -R pamac-cli pamac-gtk
updating and then installing them again if required.

What there's a good chance I would actually do is add the option to the pacman command to ignore dependencies and see what happens. But I'd do that safe in the knowledge that if things go tits up I take daily incremental backups of my root partition and can easily revert to yesterdays if need be. If it seemed fine I'd then update  pamac-cli pamac-gtk if, as I suspect, they are AUR packages.

Edit:
Your second approach of answering 'n' is almost never going to be a good, or workable, idea. If the packages have new names you have to accept that or basically never update your system again.


Those 2 removes weren't enough so after the whole attempt I ended up having to recover from the 2-week old backup because several apps just refused to launch. So the second time I ventured into unknown territory and started removals and ended up with more than 2. Once done the upgrade went ahead as it should, I'm writing this from the system already backed up again.

THANK YOU.


Here's the run with many snips:

Code: [Select]
error: failed to prepare transaction (could not satisfy dependencies)
:: removing kxmlgui breaks dependency 'kxmlgui' required by libkipi
:: removing kservice breaks dependency 'kservice' required by libkipi
:: installing libpamac (11.6.2-1.1) breaks dependency 'libpamac<11.5' required by pamac-cli
:: installing libpamac (11.6.2-1.1) breaks dependency 'libpamac<11.5' required by pamac-gtk
...
artixlinux:[root]:/# pacman -d -d -R libpamac
...
artixlinux:[root]:/# pacman -d -d -R pamac-cli
...
artixlinux:[root]:/# pacman -d -d -R pamac-gtk
...
: Starting full system upgrade...
:: Replace attica with world/attica5? [Y/n] 
....
:: removing kxmlgui breaks dependency 'kxmlgui' required by libkipi
:: removing kservice breaks dependency 'kservice' required by libkipi
artixlinux:[root]:/# pacman -d -d -R libkipi
....
looking for conflicting packages...
warning: dependency cycle detected:
warning: harfbuzz will be installed before its freetype2 dependency
warning: dependency cycle detected:
warning: mesa will be installed before its libglvnd dependency
warning: dependency cycle detected:
warning: libcamera-ipa will be installed before its libcamera dependency
...
(508/508) checking keys in keyring                                   [######################################] 100%
downloading required keys...
:: Import PGP key 9B7A287D9A2EC608, "David Runge <[email protected]>"? [Y/n]

Artix Linux , Kernel=6.5.7-artix1-1 on x86_64,
DM=Unknown, DE=KDE, ST=x11,grub2, GPT, BIOS-boot
Who, has loved us more?

Re: thrown off by *pacman -Su* behavior

Reply #3 –
I had the same problem with pamac I solved it by removing these two packages and reinstalling pamac which is in galaxy now.
Code: [Select]
sudo pacman -Sy pamac
 

Re: thrown off by *pacman -Su* behavior

Reply #4 –
Quote from: tintin – on
I had the same problem with pamac I solved it by removing these two packages and reinstalling pamac which is in galaxy now.
Code: [Select]
sudo pacman -Sy pamac

I'm not even what you could call a 'knowledgable user', show me a keyboard and I run!  But I've had unequivocally faultless results with the simple pacman command for something like two years now ever since I installed the KDE-based iso.

Code: [Select]
pacman -Syu

I ususally split thje above into two separate operations.

The only time tried pamac it bombed, as long as the repos remain impeccable with the required order and discipline reigning over them I have no need for pamac :-)

Who, has loved us more?