Update to pacman 7.0.0 and AUR Helpers
Hi all, today the update to pacman 7.0.0-r3 was installed on my machine through the core-testing repository. I am usually using the AUR helper yay for any kind of updates. After the update, yay didn't start anymore, as the library version of libalpm increased to 15 and yay was still looking for 14. A manual rebuild of yay easily fixed this. However, I am wondering if there is any way how to make such an update smoother, so that yay would be rebuilt in the same step after pacman was updated and avoid the necessity for a manual rebuild? Kind regards, Moabeat
On Tue, 2024-09-10 at 19:32 +0200, Moabeat wrote:
I am wondering if there is any way how to make such an update smoother, so that yay would be rebuilt in the same step after pacman was updated and avoid the necessity for a manual rebuild?
Hi, I do not use yay. However, yay is provided by chaotic-aur, https://wiki.archlinux.org/title/Unofficial_user_repositories#chaotic-aur . It's probably not up to date yet. However, you could add chaotic-aur and wait a bit to get the binary without building it manually with an AUR helper, or build it the official way, e.g. in a clean chroot, Regards, Ralf
On Tue, 2024-09-10 at 20:08 +0200, Ralf Mardorf wrote:
On Tue, 2024-09-10 at 19:32 +0200, Moabeat wrote:
I am wondering if there is any way how to make such an update smoother, so that yay would be rebuilt in the same step after pacman was updated and avoid the necessity for a manual rebuild?
I do not use yay. However, yay is provided by chaotic-aur, https://wiki.archlinux.org/title/Unofficial_user_repositories#chaotic-aur .
It's probably not up to date yet. However, you could add chaotic-aur and wait a bit to get the binary without building it manually with an AUR helper, or build it the official way, e.g. in a clean chroot
PS: Probably no other AUR helper can build it ;). However, you could either write a pacman warper script that automatically builds yay from AUR or just add the unofficial user repositories chaotic-aur and be patient.
My apologies for the PPPS. On Tue, 2024-09-10 at 20:16 +0200, Ralf Mardorf wrote:
write a pacman warper script
Even a wrapper scrip not necessarily does the job. In the worst case, the PKGBUILD or the yay source code requires editing. Just rebuilding yay might fail.
On Tue, 2024-09-10 at 19:32 +0200, Moabeat wrote:
core-testing
PPS: Huh?! If you rely on a testing repository and use an AUR helper, you shouldn't even just send a request ;).
On 10.09.24 20:27, Ralf Mardorf wrote:
On Tue, 2024-09-10 at 19:32 +0200, Moabeat wrote:
core-testing PPS: Huh?! If you rely on a testing repository and use an AUR helper, you shouldn't even just send a request ;).
Hi, I think there is nothing wrong using an AUR helper and, at the same time, contributing to Archlinux in testing packages from the testing repositories. Actually, I was under the impression I am sharing a result of my test in my initial mail, pointing out, that the update of pacman would break compatibility with an existing yay binary and, potentially, also with other AUR helpers. As already stated, I was able to get this fixed by myself in just rebuilding yay and now it works fine, linked against libalpm.so.15. Thank you for all your hints and insights, but the initial mail was merely intended as a heads-up that less experienced users could use some (if possible, easier) guidance how to overcome this issue when the pacman update hits the main repositories. Kind regards, Moabeat
On 9/10/24 7:32 PM, Moabeat wrote:
Hi all,
today the update to pacman 7.0.0-r3 was installed on my machine through the core-testing repository. I am usually using the AUR helper yay for any kind of updates. After the update, yay didn't start anymore, as the library version of libalpm increased to 15 and yay was still looking for 14. A manual rebuild of yay easily fixed this.
However, I am wondering if there is any way how to make such an update smoother, so that yay would be rebuilt in the same step after pacman was updated and avoid the necessity for a manual rebuild?
You need a custom post-transaction hook that will rebuild and install yay. After pacman may be too early. It is safer to do it after full OS upgrade. I am too lazy to automate it, I just usually do: cd ~/aur/yay git pull makepkg -si ... where ~/aur/yay is a git clone from AUR. Regards, Łukasz
today the update to pacman 7.0.0-r3 was installed on my machine through the core-testing repository. I am usually using the AUR helper yay for any kind of updates. After the update, yay didn't start anymore, as the library version of libalpm increased to 15 and yay was still looking for 14. A manual rebuild of yay easily fixed this.
that's a common and expected behaviour - packages like yay, installed locally from AUR (basically your own private binary repo) will never be in-sync with Arch package repositories.
However, I am wondering if there is any way how to make such an update smoother, so that yay would be rebuilt in the same step after pacman was updated and avoid the necessity for a manual rebuild?
as things stand now, not easily, perhaps you can edit your yay PKGBUILD to have a depends on "libalpm.so=14" so that pacman will warn you that updating the library will break the package. but then you'd still need to fix things manually. -- damjan
as the library version of libalpm increased to 15
Note that it is safer to rebuild binaries after a library they link against is upgraded. I personally rebuild all AUR packages after any system upgrade with `pacman -Qqm | yay -S -` no matter what.
participants (5)
-
Damjan Georgievski
-
Moabeat
-
Ralf Mardorf
-
Shawn Michaels
-
Łukasz Michalski