Package Details: yay 12.4.2-1

Git Clone URL: https://aur.archlinux.org/yay.git (read-only, click to copy)
Package Base: yay
Description: Yet another yogurt. Pacman wrapper and AUR helper written in go.
Upstream URL: https://github.com/Jguer/yay
Keywords: arm AUR go helper pacman wrapper x86
Licenses: GPL-3.0-or-later
Submitter: jguer
Maintainer: jguer
Last Packager: jguer
Votes: 2254
Popularity: 25.31
First Submitted: 2016-10-05 17:20 (UTC)
Last Updated: 2024-09-19 14:27 (UTC)

Pinned Comments

jguer commented on 2024-03-16 08:06 (UTC)

yay: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory

This will happen if you upgrade pacman and yay separately If you have this error you need to manually recompile yay

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

jguer commented on 2019-04-16 14:08 (UTC)

I cannot delete the spam comments appearing regularly in this page, which has also led me to disable notifications from here. I remind that the best way to receive support or report a problem is through the Upstream URL.

Latest Comments

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 35 Next › Last »

Jake commented on 2019-10-23 19:17 (UTC) (edited on 2019-10-23 19:19 (UTC) by Jake)

Is it really necessary to put the specific pacman version in the dependency list? It might be not totally clean, but can't you just expect that it is built with the current versions from the official repo? Then yay would as usual upgrade from the offical repos first, build the AUR stuff afterwards and everything would be fine.

Also if we are really strict, if yay-bin is compiled against v5.2 (libalpm.so.12) it will also not run with 5.1.x. So it should also depend on pacman>=5.2, or not? If you fix this that workaround would also not work.

wooptoo commented on 2019-10-23 17:16 (UTC)

@jguer Another method is to fetch the latest yay PKGBUILD yay -G yay, update pacman, then build the new yay with makepkg.

AlexWayfer commented on 2019-10-23 12:41 (UTC)

@jguer, thank you, sorry.

jguer commented on 2019-10-23 12:12 (UTC) (edited on 2019-10-23 12:12 (UTC) by jguer)

WARNING: PACKAGER should have the format 'Example Name <email@address.invalid>'

https://github.com/Jguer/yay/issues/1085

AlexWayfer commented on 2019-10-23 12:09 (UTC)

WARNING: PACKAGER should have the format 'Example Name <email@address.invalid>'

flower commented on 2019-10-23 10:36 (UTC) (edited on 2019-10-23 10:39 (UTC) by flower)

sudo pacman -R yay

sudo pacman -Syu

cd yay # your old yay dir... otherwise follow new install

git pull

makepkg -si

cd ..

yay -Syu

worked for me :)

jguer commented on 2019-10-23 08:36 (UTC) (edited on 2019-10-23 08:45 (UTC) by jguer)

Having issues upgrading yay and pacman at the same time? Here is the proposed workaround for now.

yay -S yay-bin
sudo pacman -Syu
yay -S yay

yay-bin is a binary ready package with yay already compiled against v5.2, it does not require go to build. https://github.com/Jguer/yay/issues/1084

WSDMatty commented on 2019-10-22 14:42 (UTC) (edited on 2019-10-22 14:47 (UTC) by WSDMatty)

For those on the testing branch needing to manually update yay for the newest pacman. Here's a PKGBUILD.

# Maintainer: Jguer <joaogg3@gmail.com>
pkgname=yay
pkgver=9.4.0
pkgrel=1
pkgdesc="Yet another yogurt. Pacman wrapper and AUR helper written in go."
arch=('i686' 'x86_64' 'armv7h' 'armv6h' 'aarch64')
url="https://github.com/Jguer/yay"
license=('GPL')
depends=(
  'pacman>=5.2.0'
  'sudo'
  'git'
)
makedepends=(
  'go'
)
source=("${pkgname}-${pkgver}.tar.gz::https://github.com/Jguer/yay/archive/v${pkgver}.tar.gz")
sha1sums=('9e62c6e3d0bae7b6687717b07e3455ac9aa451cd')

build() {
  cd "$srcdir/$pkgname-$pkgver"
  EXTRA_GOFLAGS="-gcflags all=-trimpath=${PWD} -asmflags all=-trimpath=${PWD}" \
    LDFLAGS="-linkmode external -extldflags \"${LDFLAGS}\"" \
    make VERSION=$pkgver DESTDIR="$pkgdir" build
}

package() {
  cd "$srcdir/$pkgname-$pkgver"
  make VERSION=$pkgver DESTDIR="$pkgdir" PREFIX=/usr install
}