Package Details: yay-bin 12.3.5-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: 275
Popularity: 8.18
First Submitted: 2016-12-03 15:06 (UTC)
Last Updated: 2024-03-23 22:58 (UTC)

Dependencies (4)

Required by (36)

Sources (3)

Pinned Comments

jguer commented on 2021-05-20 11:48 (UTC) (edited on 2021-06-04 16:36 (UTC) by jguer)

With pacman 6 arriving a rebuild of yay will be necessary, if you upgrade pacman without upgrading yay at the same time, yay will not run after.

It will take a bit to release the yay-bin binaries compiled with pacman 6 support

Once they're released (and if you installed pacman 6 before)

# pacman -S --needed git base-devel
$ git clone https://aur.archlinux.org/yay-bin.git
# pacman -R yay-bin
$ cd yay-bin
$ makepkg -si

Latest Comments

1 2 3 4 Next › Last »

tech commented on 2024-05-05 18:10 (UTC)

@Gotit It sounds like you have an older version of yay installed. yay and yay-bin are two different packages. yay is a package built and installed by your system, while yay-bin is the binary version of yay that's already been compiled and is merely downloaded and installed on your system. You can remove yay and install yay-bin to resolve this conflict if you want to use yay-bin over yay.

Gotit commented on 2024-05-05 18:04 (UTC) (edited on 2024-05-05 18:17 (UTC) by Gotit)

I'm getting a conflict when installing yay-bin:

==> Finished making: yay-bin 12.3.5-1 (Sun 05 May 2024 01:36:50 PM EDT)
==> Installing package yay-bin with pacman -U...
loading packages...
resolving dependencies...
looking for conflicting packages...
:: yay-bin-12.3.5-1 and yay-12.3.4-1 are in conflict. Remove yay? [y/N]

any thoughts on how can I resolve this?

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