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

MinzordYT commented on 2018-07-01 19:33 (UTC)

thanks

arx commented on 2018-06-23 22:16 (UTC)

Yeah I found that, thanks :D

go get -u github.com/Jguer/yay

Morganamilo commented on 2018-06-23 22:15 (UTC)

The AUR repository just contains a pkgbuild. If you want to use go get you'll have to use the actual yay repo.

arx commented on 2018-06-23 22:13 (UTC)

Can someone make this installable w/ Go?

go get -u aur.archlinux.org/yay.git

Morganamilo commented on 2018-06-04 22:38 (UTC)

@emacsomancer That seems a little out of scale for AUR comments, you probably want to open an issue on github.

Two things do come to mind though, do you use any sort of vpn/proxies? And is your system time correct?

emacsomancer commented on 2018-06-04 22:32 (UTC)

I'm getting TLS handshake timeouts from time to time

jguer commented on 2018-06-01 09:04 (UTC)

I agree with Morganamilo, aurutils is a lot more thought around local repos. As for yay-git transition to yay, A lot of stuff has changed, not particularly breaking changes, but some staging time delivers a more stable release here. yay-git is rarely broken though so it should be ok to use most of the time, just with some incomplete or not optimized features.

Morganamilo commented on 2018-06-01 04:16 (UTC)

Then yay-git should work fine for you. There's also aurutils which I would say fits the whole local repo approach a lot more.

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

Well, the reason I use PKGDEST is because I build once and deploy into a custom repository that other systems install from. I use yay as my automation means to do this because during updates, it gets everything, and when its done, I have fully updated system and AUR packages re-distributed.

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

A ton of changes went into -git recently to probably a while. The -git should be stable enough to use though.

If you want you can just keep to this version. Unsetting PKGDEST / Removing it from your makepkg.conf should get it working.