Just a friendly warning - with the new pacman comes a new version of libalpm.so, which breaks EOS’s version of yay.
So will this be an issue for EOS devs or yay devs to address?
Actually it’s yay itself (fixed my OP). I tried building yay from source and it ran into the same library version issue.
UPDATE: I’m an idiot. The script I was using was for yay-bin (pre-compiled), so naturally it failed. Using the source package works.
Thanks for the heads up.
Here is a partial list of “packages required by” for pacman from here
https://archlinux.org/packages/core-testing/x86_64/pacman/
- arch-audit (requires libalpm.so) (testing)
- arch-rebuild-order (requires libalpm.so) (testing)
- arch-repro-status (requires libalpm.so) (testing)
- paccat (requires libalpm.so) (testing)
- pacquery (requires libalpm.so) (testing)
So if you have the “testing” repos enabled and was able to successfully compile a working yay, this would be a good sign.
Pudge
Great to know, basically most if not all our AUR helpers will have to be recompiled once the new version of pacman hits the streets.