Package Details: yay 8.1173.0-1

Git Clone URL: (read-only)
Package Base: yay
Description: Yet another yogurt. Pacman wrapper and AUR helper written in go.
Upstream URL:
Keywords: AUR go helper pacman wrapper
Licenses: GPL
Submitter: jguer
Maintainer: jguer
Last Packager: jguer
Votes: 362
Popularity: 70.277118
First Submitted: 2016-10-05 17:20
Last Updated: 2018-10-18 08:33

Required by (5)

Sources (1)

Latest Comments

1 2 3 4 5 Next › Last »

Alad commented on 2018-10-27 10:02

It's the nature of the beast. Pacman wrappers attract the kind of helpless users that can't work with basic tools shipped with the distribution.

johnnybash commented on 2018-10-08 15:53

During the installation phase there is no point in using an aur helper

ftfy ;)

lefsha commented on 2018-10-08 11:41

Surely it works if all deps packages are installed. It doesn't though on a clean system. Filed a bug report. It makes me mad, that yay deny to work under root. That is the only possibility on a new chrooted system. I have to make a new user and su to it just to be able use yay. At the same time pacman doesn't work under user and I have to switch back to root or use sudo. Being a root initially it is perverse to pretend to be another user and then call sudo. During the installation phase there is no point to be non root user. 100% of work requires root privileges. And again yaourt doesn't have such an issue. It just works. Good lesson - new is not always better than old.

jguer commented on 2018-10-08 11:04

I passed all of the initial phase of build and it works, please report this kind of issue in the upstream URL, also, we're very sorry to see you go, you will be missed.

lefsha commented on 2018-10-08 09:55

Unable to use YAY just to install a single package. Simple construction "yay -S ffmpeg-libfdk_aac" didn't work YAY reports problem each time at different place: "Inner conflicts found" My guess the problem is that single package libva provides, and at the same time. Yaourt doesn't have that issue and works perfect. I've droped yay from my system.

HighValueWarrior commented on 2018-08-25 05:54

Solid and Straight Forward. Thanks.

Morganamilo commented on 2018-08-01 12:26

For the bug, try clean building, if it persists open an issue.

For the second point, see the FAQ.

themoosemachine commented on 2018-08-01 11:39

Firstly, the following error pops up a lot when trying to upgrade certain AUR files: fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'</file></revision>

Google Chrome is one of the packages affected by this bug.

Secondly, the previous package was easier since all options were selected at the start. In the current version, we have to wait for all core, extra, community and multilib packages to update first, and then select the AUR packages. This is not a biggie, but just annoying; whereas earlier it was smoother and an overall nicer experience.

ilfabri commented on 2018-07-12 06:39

When performing 'yay -Syua', if there are aur updates, it performs only these ones skipping the standard repository updates. You need to run the command once more to complete the upgrade. Thank you for the awesome work, btw!

EDIT: I figured out that running 'yay' is enough

Morganamilo commented on 2018-07-05 20:37

It's part of the debug symbols the go compiler puts into the binary. If you manage to make Yay stack trace it will tell you which file the error occurred in. Using the pwd of where it was compiled.