I did that and everything seems to be fine. But I still have a question about it: If this is the classic method to install a package from the AUR - does that mean that I have now installed yay from the AUR and no longer from the extra repos? How do I get back to the “normal version” again… someday… ?
Is this something that will resolve itself via pacman in a few days, or does it require manual intervention? I can wait if that’s the simplest and cleanest solution.
$ yay
yay: error while loading shared libraries: libalpm.so.14: cannot open shared object file: No such file or directory
If your ETA is still 2 days, I can wait. I would rather have Endeavour mend this than me doing a bunch of extra work which I am bound to screw up.
Please confirm. And thanks for posting this thread.
If there’s a new version in the repos, it should take over from the AUR version - I’ve had this when I set ChaoticAUR (3rd party repo) up and it had newer versions than my older AUR packages.
Output of yay -Ss yay confirms the system knows whats going on after the manual update:
endeavouros/yay 12.3.5-1 (2.9 MiB 8.5 MiB) (Installed: 12.3.5-2)
Yet another yogurt. Pacman wrapper and AUR helper written in go.
aur/yay 12.3.5-2 (+2225 29.28) (Installed)
Yet another yogurt. Pacman wrapper and AUR helper written in go.
I have used trizen for about 5 years and haven’t had one issue with it. It is very stable, coded in perl, and doesn’t get updated very often. It is small and lightweight, has few dependencies, and just works without any drama.