AUR (en) - yay

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: yay 12.4.2-1

Package Actions

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:	2239
Popularity:	29.97
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 .. 12 13 14 15 16 17 18 19 20 21 22 .. 35 Next › Last »

darnir commented on 2020-08-21 22:07 (UTC)

I have been unable to build this package for a few months now. Everytime I try to build I end up with a log similar to: https://pastebin.com/A3KRz8vJ

On digging deeper, this seems to come from the fact that my makepkg.conf contains `CFLAGS="... -flto ...". Apparently, turning on LTO in the C compiler, breaks the build.

If this is the case, the PKGBUILD should probably account for such scenarios

yochananmarqos commented on 2020-07-20 23:16 (UTC) (edited on 2020-07-20 23:16 (UTC) by yochananmarqos)

@masterberg: You should already have the base-devel group installed. Those packages are not required to be in makedepends() as they're assumed to be installed. See here and here.

masterberg commented on 2020-07-20 22:07 (UTC)

Add make package as a requirement as it's a build dependency.

Xavion commented on 2020-06-26 21:04 (UTC) (edited on 2020-06-30 00:11 (UTC) by Xavion)

I can't build v10.0.1-1 for some reason. See the build/error output here: https://pastebin.com/pk9dEAES

The same thing happens in a clean chroot. What can I do to overcome this problem?

Update: I've switched to the "yay-bin" package; that will do for now.

yochananmarqos commented on 2020-06-19 14:58 (UTC)

@Arashk @Slenderchat: Try my PKGBUILD with the export bits removed.

slenderchat commented on 2020-06-19 14:20 (UTC) (edited on 2020-06-19 14:25 (UTC) by slenderchat)

I am getting same issue as @Arashk.

Update: Works using VPN. For me may be related with US and EU sanctions over Crimea.

Arashk commented on 2020-06-18 17:11 (UTC)

I get an error while trying to build the package:

==> Making package: yay 10.0.1-1 (Thu 18 Jun 2020 09:33:21 PM +0430) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found yay-10.0.1.tar.gz ==> Validating source files with sha256sums... yay-10.0.1.tar.gz ... Passed ==> Extracting sources... -> Extracting yay-10.0.1.tar.gz with bsdtar ==> Removing existing $pkgdir/ directory... ==> Starting build()... go build -v -trimpath -mod=readonly -modcacherw -ldflags '-s -w -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.yayVersion=10.0.1" -X "main.localePath=/usr/share/locale/"' -buildmode=pie -o yay go: github.com/Jguer/go-alpm@v0.0.0-20200405152916-a3feea4322e9: Get "https://gocenter.io/github.com/%21jguer/go-alpm/@v/v0.0.0-20200405152916-a3feea4322e9.mod": dial tcp 35.230.74.213:443: i/o timeout make: *** [Makefile:134: yay] Error 1 ==> ERROR: A failure occurred in build(). Aborting...

MiniKoala commented on 2020-06-15 15:48 (UTC)

@RubenKelevra @pipep

Thank you! Much appreciated!!

kseistrup commented on 2020-06-14 16:16 (UTC)

@jguer I did read the pinned comment before I submitted my comment here, but just like it is inconvenient for you to receive comments here, it was inconvenient for me to submit at issue at the “upstream URL”, so I reckoned it was better to submit it here that to not submit it at all. That was the good intention.

@yochananmarqos Thanks for submitting the issue on Microsoft Github!