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: 2251
Popularity: 23.92
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 .. 28 29 30 31 32 33 34 35 Next › Last »

psi-jack commented on 2018-06-01 03:34 (UTC)

Yep, I was just reading about that in the issues, from discussions in the #archlinux-pacman channel (meant to be in #archlinux, but, oops)

And yep.. yay-git does resolve the problem. When will that be released to here?

Morganamilo commented on 2018-06-01 03:18 (UTC)

If you're using PKGDEST at all then Pacman 5.1 changed some stuff with that. Should be fixed in -git if you want to try that.

psi-jack commented on 2018-06-01 03:16 (UTC) (edited on 2018-06-01 03:16 (UTC) by psi-jack)

Recently I've been getting, since pacman 5.1.0 update, all AUR packages failing to install after being built:

==> Leaving fakeroot environment.
==> Signing package(s)...
  -> Created signature file google-chrome-67.0.3396.62-1-x86_64.pkg.tar.xz.sig.
==> Finished making: google-chrome 67.0.3396.62-1 (Thu 31 May 2018 11:04:43 PM EDT)
==> Cleaning up...
Could not find built package google-chrome-67.0.3396.62-1-x86_64.pkg

And yet, it's there in my specifically configured directory in makepkg.conf:

-rw-r--r-- 1 psi-jack users 53835768 May 31 23:04 google-chrome-67.0.3396.62-1-x86_64.pkg.tar.xz

jonathon commented on 2018-04-29 15:53 (UTC)

Sounds good. An AUR helper without git support isn't much of an AUR helper. ;)

jguer commented on 2018-04-29 11:17 (UTC)

Will do :)

Yay can still function, albeit limped, without git. We decided to change git to a hard dependency as unless you change the settings before first run to --nogitclone yay will crash and we've committed to making git a first class citizen.

I would only feel comfortable changing git to an optdepend if the source is changed to never crash in the absence of git (which is not that hard, just low priority right now).

jonathon commented on 2018-04-29 10:18 (UTC)

Please switch the source line to 

source=("${pkgname}-${pkgver}.tar.gz::https://github.com/Jguer/yay/archive/v${pkgver}.tar.gz")

to avoid potential $SRCDEST conflicts with other packages which have the same version.

Is git a hard dependency for yay operation? If not, it's an optdepend rather than a depend. Otherwise carry on. :)

jguer commented on 2018-04-26 21:25 (UTC)

True, I'll add it and increase the pkgrel

Morganamilo commented on 2018-04-26 20:24 (UTC)

Git should probably be added as a hard dependency for all Yay variants now.

grunch commented on 2018-04-24 14:51 (UTC)

To "close" this thread (again, NOT a yay issue), the problem was with freecad-ose. I ran pacman -Sii boost-libs to determine all packages that depend on boost-libs. I looked at each of those packages with pacman -Si and learned that archlinuxcn/freecad-oce (a repo that I added) was the culprit that depends on boost-libs<1.66.0.

So, yay was mostly behaving properly, it was simply not telling me which package could not resolve its dependency.

grunch commented on 2018-04-23 17:44 (UTC)

Thanks for the suggestion @Morganamilo, but using -d made no difference. I'm thinking this is a local package issue due to the other warnings. I just ran trizen -Syu --aur and got similar, but slightly more descriptive warnings:

:: arm-frc-linux-gnueabi-frcmake-hg is unmaintained!
:: js was not found in AUR -- skipping
:: libcloudproviders was not found in AUR -- skipping
:: libhttpseverywhere was not found in AUR -- skipping
I'll spend some time cleaning up my installation and open an issue on github if I continue to have trouble with yay. Thanks!

« First ‹ Previous 1 .. 28 29 30 31 32 33 34 35 Next › Last »