Package Details: yay-bin 12.5.7-1

Git Clone URL: https://aur.archlinux.org/yay-bin.git (read-only, click to copy)
Package Base: yay-bin
Description: Yet another yogurt. Pacman wrapper and AUR helper written in go. Pre-compiled.
Upstream URL: https://github.com/Jguer/yay
Keywords: AUR go helper pacman wrapper
Licenses: GPL-3.0-or-later
Conflicts: yay
Provides: yay
Submitter: jguer
Maintainer: jguer
Last Packager: jguer
Votes: 364
Popularity: 9.96
First Submitted: 2016-12-03 15:06 (UTC)
Last Updated: 2025-12-14 20:01 (UTC)

Dependencies (4)

Required by (121)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

m040601 commented on 2024-03-24 03:52 (UTC)

@jguer:

Thank you for keeping up and regularly providiing and maintaining this yay-bin.

  • yay_12.3.5_armv7h.tar.gz
  • yay_12.3.5_aarch64.tar.gz

I want to let you know that it is still very needed and appreciated that you build and release those two also.

m040601 commented on 2024-03-20 12:12 (UTC) 

The armv7h bin package seems to have been incorrectly built against the old libalpm. Pacman on my ARM Pi2 has
updated to 6.1.0-3 but after building and installing this latest 12.3.4-1 package manually I still get:....

Yeap. Can confirm. I get exactly the same problem also on Pi2.

bulletmark commented on 2024-03-18 06:24 (UTC) (edited on 2024-03-18 06:37 (UTC) by bulletmark)

The armv7h bin package seems to have been incorrectly built against the old libalpm. Pacman on my ARM Pi2 has updated to 6.1.0-3 but after building and installing this latest 12.3.4-1 package manually I still get:

$ yay
yay: error while loading shared libraries: libalpm.so.13: cannot open shared object

PS edit: It has occurred to me what the problem is. Pacman 6.1 took 2 extra days before it was released on Arch ARM and I am guessing jguer built the ARM v7 binary in that 2 day window on his ARM v7 box assuming it had updated to pacman 6.1 but it had not.

rabin commented on 2024-03-17 15:32 (UTC)

Can we update the dependency to libalpm.so=14 instead of directly on pacman>5?

tech commented on 2024-03-17 01:49 (UTC)

I had no problems upgrading yay-bin and pacman, I upgraded at the same time through yay itself, after not upgrading my system for a while. I then checked version output.

$ pacman --version .--. Pacman v6.1.0 - libalpm v14.0.0 $ yay --version yay v12.3.3 - libalpm v14.0.0

Dounial commented on 2023-10-25 06:47 (UTC)

If someone is trying to install this via Fedora (or really any other unlisted distro), I have one simple tip which helped me install it properly: In the PKGBUILD-file simply delete the two needed dependencies (pacman & go) because you might fail trying to install it via the PKGBUILD so I recommend installing it via dnf as that's the only way [it seems to me] to get this working on Fedora.

bbaster commented on 2022-06-20 16:24 (UTC)

Anyone else getting this error while trying to upgrade this package?

-> error fetching yay-bin: fatal: not a git repository (or any of the parent directories): .git 
         context: exit status 128

tech commented on 2021-12-06 21:54 (UTC)

It seems redundent to strip a binary that is already stripped in upstream. Unless this goes against the AUR submition guidelines for binary packages, why not remove this from the build? This patch works for me.

diff --git a/PKGBUILD b/PKGBUILD
index 06df7aa..7281848 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -14,6 +14,7 @@ optdepends=(
 )
 provides=('yay')
 conflicts=('yay' 'libalpm.so<13')
+options=('!strip')

 source_x86_64=("https://github.com/Jguer/yay/releases/download/v${pkgver}/${pkgname/-bin/}_${pkgver}_x86_64.tar.gz")
 source_aarch64=("https://github.com/Jguer/yay/releases/download/v${pkgver}/${pkgname/-bin/}_${pkgver}_aarch64.tar.gz")

Alterego commented on 2021-06-04 12:22 (UTC)

Oh yes i forgot to do that, thanks

« First ‹ Previous 1 2 3 4 5 6 Next › Last »