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: 2282
Popularity: 25.43
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 .. 14 15 16 17 18 19 20 21 22 23 24 .. 35 Next › Last »

MiniKoala commented on 2020-06-13 23:40 (UTC)

Hello, I have a question. I'm new to Arch, I'm from Slackware ^^ this is the first update of an AUR package that I have to execute, I would like to know how should I do it? I read that it is not recommended to use YAY with root, so how to apply updates with yay and what permissions do I have to grant to my user to perform them? Thank you!

RubenKelevra commented on 2020-05-30 15:33 (UTC)

@gui_user yes it does. It's just a wrapper for the usual tooling you would use to build packages.

If you for example change the compression in makepkg.conf and you build a package with yay, it will change the compression for them.

gui_user commented on 2020-05-30 15:15 (UTC)

I was wondering, does yay respect the settings in /etc/makepkg.conf?

masterkorp commented on 2020-05-21 13:44 (UTC)

Hello, I cannot commpile:

==> Starting build()... go build -v -mod=mod -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.7"' -modcacherw -trimpath -o yay bytes strings crypto/cipher

bytes

/usr/lib/go/src/bytes/bytes_decl.go:10:6: IndexByte redeclared in this block previous declaration at /usr/lib/go/src/bytes/bytes.go:90:34 /usr/lib/go/src/bytes/bytes_decl.go:17:6: Equal redeclared in this block previous declaration at /usr/lib/go/src/bytes/bytes.go:18:25 /usr/lib/go/src/bytes/bytes_decl.go:24:6: Compare redeclared in this block previous declaration at /usr/lib/go/src/bytes/bytes.go:26:27 crypto/rc4

strings

/usr/lib/go/src/strings/strings_decl.go:8:6: IndexByte redeclared in this block previous declaration at /usr/lib/go/src/strings/strings.go:150:34 /usr/lib/go/src/strings/strings_decl.go:8:6: missing function body

crypto/cipher

/usr/lib/go/src/crypto/cipher/xor_amd64.go:9:6: xorBytes redeclared in this block previous declaration at /usr/lib/go/src/crypto/cipher/xor.go:58:33 /usr/lib/go/src/crypto/cipher/xor_amd64.go:22:6: xorWords redeclared in this block previous declaration at /usr/lib/go/src/crypto/cipher/xor.go:83:27

crypto/rc4

/usr/lib/go/src/crypto/rc4/rc4_asm.go:15:18: (Cipher).XORKeyStream redeclared in this block previous declaration at /usr/lib/go/src/crypto/rc4/rc4.go:61:6 make: ** [Makefile:50: yay] Error 2

r4start commented on 2020-05-04 11:44 (UTC)

Hi, I am getting the following build error: go build -v -mod=mod -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.7"' -modcacherw -trimpath -o yay flag provided but not defined: -modcacherw

Had the same issue. I had to build yay manually. Changing -modcacherw to -mod=readonly helped.

MikeD commented on 2020-05-01 21:07 (UTC)

Hi, I am getting the following build error: go build -v -mod=mod -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.7"' -modcacherw -trimpath -o yay flag provided but not defined: -modcacherw

sphere101 commented on 2020-04-22 14:12 (UTC)

Having these issues when building latest update.. Any thoughts?

go build -v -mod=mod -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.6"' -modcacherw -gcflags all=-trimpath=/home/andy/.cache/yay/yay/src/yay-9.4.6 -asmflags all=-trimpath=/home/andy/.cache/yay/yay/src/yay-9.4.6 -o yay flag provided but not defined: -mod usage: build [-o output] [-i] [build flags] [packages] Run 'go help build' for details. make: *** [Makefile:49: yay] Error 2 ==> ERROR: A failure occurred in build(). Aborting... Error making: yay

RubenKelevra commented on 2020-04-18 08:17 (UTC)

@bkb you can select the sudo-loop functionality to let yay handle this situation more gracefully:

yay -Y --sudo-loop --save

See this comment, for the reasoning behind that:

https://github.com/Jguer/yay/issues/1221#issuecomment-606465266

whynothugo commented on 2020-04-17 10:06 (UTC)

The build process runs in the same terminal, so the sudo ticket is valid. This allows scripts to potentially sudo, which is something you don't want when building.

Also, the ticket might expire by the time building is done.

uffe commented on 2020-04-17 08:22 (UTC)

@brb by asking for sudo password early - won't you risk that the "sudo"privs have timed out if the update takes a long time to process (download etc) ?

« First ‹ Previous 1 .. 14 15 16 17 18 19 20 21 22 23 24 .. 35 Next › Last »