Package Details: yay 9.4.4-1

Git Clone URL: (read-only, click to copy)
Package Base: yay
Description: Yet another yogurt. Pacman wrapper and AUR helper written in go.
Upstream URL:
Keywords: arm AUR go helper pacman wrapper x86
Licenses: GPL
Submitter: jguer
Maintainer: jguer
Last Packager: jguer
Votes: 939
Popularity: 66.97
First Submitted: 2016-10-05 17:20
Last Updated: 2020-01-17 20:18

Required by (8)

Sources (1)

Pinned Comments

jguer commented on 2019-10-23 08:36

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.

jguer commented on 2019-04-16 14:08

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

1 2 3 4 5 6 ... Next › Last »

editicalu commented on 2020-01-22 15:03

@hugo you need to install base-devel. This is assumed hence make is not a dependency.

hugo commented on 2020-01-22 14:59

"make" is missing on makedepends, got an error on a fresh install.

MindfulConsumer commented on 2020-01-20 12:26

On-topic: I've noticed with other packages yay is importing a single GPG key just fine. Could the problem be multiple GPG keys?

Off-topic: @fightcookie; maybe walk the talk? How is you bulky comment not off-topic and without new information? The way I see it is this comment section is the place where end users help each other out to get a particular software working. I can't always tell the difference between a packaging or a software bug.

fightcookie commented on 2020-01-20 08:22

@MindfulConsumer I am subscribed to comments to this aur package, so off-topic comments are kind of distracting and wasting my time (I'm surely not the only one subscribed). Also, these kinds of comments led @jguer to disable comments to this package (according to their pinned message), which is unfortunate I think for support of the package since they are the maintainer currently! It is totally ok of you to boycott GitHub, but please consider only posting packaging related bugs here, to keep the comments readable by everyone interested without being overwhelmed by off topic things :)

MindfulConsumer commented on 2020-01-19 13:27

@swm and @jguer: sadly I had to conclude github should be on my boycott list, I refuse to create an account there. I can manually import the gpg keys without problems with "gpg --recv-keys <key>" and continue installing.

swm commented on 2020-01-19 08:30

@iTanguy and @MindfulConsumer: Seeing jguer's pinned comment from 2019-04-16, you should probably go to the upstream issue tracker, see if the problem has already been reported there and do so if not.

@MindfulConsumer: yay uses sudo which may ask for your user password to execute actions as root (if not already done so in the last x minutes, depending on your sudo configuration). Otherwise it should not ask for passwords. The "permission denied" error you see is from gpg trying to get the keys from a server, which has nothing to do with your local user accounts. (I think yay's usage of gpg will also import the keys to your own gpg keyring, which does not belong to root and does not need sudo usage.) An issue with the same gpg error message has been reported upstream, which might help you solve your problem:

MindfulConsumer commented on 2020-01-18 23:59

I'm pretty sure yay is supposed to ask me for a password here:

 :: Parsing SRCINFO (1/1): palemoon-bin

 ==> PGP keys need importing:
 -> 439F46F42C6AE3D23CF52E70865E6C87C65285EC, required by: palemoon-bin
-> 3DAD8CD107197488D2A2A0BD40481E7B8FCF9CEC, required by: palemoon-bin
==> Import? [Y/n] y
:: Importing keys with gpg......
gpg: keyserver receive failed: Permission denied
==> Error: Problem importing keys

iTanguy commented on 2020-01-18 13:29

License information should be more accurate. I am no packaging expert nor lawyer, just a user who cares about FOSS.

  1. GPL license version used is GLP v3.0, for License should be set to GPL3
  2. The "go-alpm" module is under MIT license, so it should be added to the "License" field (becoming "GPL3 MIT")
  3. the MIT license file should be added to /usr/share/licenses/yay/

sorenvonsarvort commented on 2020-01-15 10:50

EDITED: My apologies, I had installed custom patches for go, so they made the yay package unbuildable. I am also sorry for reporting the bug here, but not at the upstream! Have a nice day.


Hey, I would like to notify this package doesn't build on my workstation anymore! Does this issue apply to someone else's setup?

$ yay -Syu
==> Retrieving sources...
  -> Found yay-9.4.3.tar.gz
==> Starting build()...
go build -v -mod=vendor -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.3"' -gcflags all=-trimpath=/home/FILTERED/.cache/yay/yay/src/yay-9.4.3 -asmflags all=-trimpath=/home/FILTERED/.cache/yay/yay/src/yay-9.4.3 -o yay
go: inconsistent vendoring in /home/FILTERED/.cache/yay/yay/src/yay-9.4.3: is explicitly required in go.mod, but vendor/modules.txt indicates is explicitly required in go.mod, but vendor/modules.txt indicates

run 'go mod vendor' to sync, or use -mod=mod or -mod=readonly to ignore the vendor directory
make: *** [Makefile:47: yay] Error 1
==> ERROR: A failure occurred in build().
Error making: yay

JM9 commented on 2020-01-14 21:12

@nsmcclellan thanks. To whoever marked as out of date, please leave a comment as to why you are marking something out of date. Thanks!