Package Details: yay-bin 10.3.1-2

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: GPL3
Conflicts: libalpm.so<13, yay
Provides: yay
Submitter: jguer
Maintainer: jguer
Last Packager: jguer
Votes: 186
Popularity: 9.86
First Submitted: 2016-12-03 15:06
Last Updated: 2021-07-29 20:25

Required by (16)

Sources (4)

Pinned Comments

jguer commented on 2021-05-20 11:48

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 Next › Last »

Alterego commented on 2021-06-04 12:22

Oh yes i forgot to do that, thanks

kuluse commented on 2021-06-04 07:55

Alterego, I just reinstalled yay-bin following the pinned comment and there is no conflict anymore. Maybe you have another error

bulletmark commented on 2021-06-03 23:36

I've been using yay-bin on my Arch and Arch ARM boxes for ages. All of these have updated to pacman 6 and I have updated yay-bin to work on the Arch boxes but it fails to install on my Arch ARM boxes because of error yay-bin and pacman are in conflict (libalpm.so<13-64). On my Arch boxes, pacman 6 provides libalpm.so=13-64 but on Arch ARM pacman 6 provides libalpm.so=13-32. Changing the PKGBUILD to conflicts=('yay' 'libalpm.so<13') fixes this.

Alterego commented on 2021-06-03 23:29

Still conflicting after latest release

hexhu commented on 2021-06-01 03:15

pacman 6.0.0-2 conflicts with yay-bin

==> Installing package yay-bin with pacman -U...
loading packages...
resolving dependencies...
looking for conflicting packages...
:: yay-bin and pacman are in conflict (libalpm.so). Remove pacman? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: yay-bin and pacman are in conflict (libalpm.so>12-64)
==> WARNING: Failed to install built package(s).

jguer commented on 2021-05-20 11:48

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

jpegxguy commented on 2021-01-11 21:36

If v10.1.2 supports pacman > 6, why the < 6 check in the depends array?

jguer commented on 2020-12-15 08:41

@maverick1 yay is built with versioned bindings meaning it requires a recompile when libalpm is updated. Right now building yay with -tags six will use the pacman6 bindings. This yay-bin was compiled without -tags six so will only be compatible with pacman5, once pacman6 is released I'll update yay-bin to build using -tags six by default

maverick1 commented on 2020-12-15 05:35

I am wondering why pacman<6 is being added now. It should have been added for previous builds but not this one according to the changelog.

SleeplessSloth commented on 2020-12-14 23:59

Why does v10.1.2 require pacman<6 when in the changelog it clearly says support for >6 was added instead? Shouldn't it be just depends=('pacman'...)?