:: Searching Arch & EndeavourOS for updates…
apache 2.4.47-1 → 2.4.48-1
appstream-glib 0.7.18-1 → 0.7.18-2
pacman 5.2.2-4 → 6.0.0-2
pacman-contrib 1.4.0-1 → 1.4.0-2
Password:
:: Synchronizing package databases…
core is up to date
extra is up to date
community is up to date
multilib is up to date
endeavouros is up to date
:: Starting full system upgrade…
resolving dependencies…
looking for conflicting packages…
:: pacman and yay are in conflict (libalpm.so). Remove yay? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: pacman and yay are in conflict (libalpm.so>12-64)
I’m going wait a few days to update more than likely. This should be sorted out rather quickly by the Arch team. I just saw this when I went to update and cancelled.
It was in testing earlier today. We all knew this was coming and I’m sure it’s being worked on already. I’ve gone well over a month without updating with zero ill effects to my system. I’ll just wait it out.
I’m running Gnome & there is an extension that checks for updates–if you are on other DE’s there is a command to just see the upgrades–I don’t remember what it is though…
That’s not really how that works. That is how you can install something without upgrading other things. You DON’T want to do partial updates, because that could render your system even worse than not having yay.
I normally use paru as my AUR helper (which is more or less a drop-in replacement for yay), and it seems that paru is broken as well. However, the paru-git package is working. I’m not sure if it’s advisable to use a -git package just because the normal and -bin packages don’t work, but it’s working so here we are. I’ll switch back to the regular paru package once the issue is fixed over there as well. I imagine that this is the same issue in yay and paru since paru is essentially just a rewrite of yay which is being developed more actively, so it’s at least somewhat relevant in this thread.
ETA: according to this thread, just installing yay from the AUR is enough to (somewhat) fix the problem. I haven’t tried that, though.
Patience is your main friend in this case! I know we are spoiled rotten by Arch’s timely updates, but we can’t expect everyone to automagically ‘know’ that the change has been pushed out to mirrors already!
Yasy, paru, probably aura as well - need to be rebuilt against the new libraries (and may have been in -git versions) - so I doubt it’ll take more than a day or so. It’s not even a weekend - and your system won’t be hurt by postponing updates for a bit!
In the meantime - if your AUR packages need updating - you can use yay -Sua, which will update ONLY AUR packages, and leave the main updates for a day or so…