Package Details: yay 11.0.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: GPL3
Submitter: jguer
Maintainer: jguer
Last Packager: jguer
Votes: 1581
Popularity: 39.48
First Submitted: 2016-10-05 17:20
Last Updated: 2021-10-16 20:48

Required by (19)

Sources (1)

Pinned Comments

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 »

jonathon commented on 2021-10-16 17:09

@yschiebelhut, that is not an issue with this PKGBUILD. If you think it is a bug in yay then report on the GitHub issue tracker. if you think it's a bug with the ubridge PKGBUILD then report to that package's maintainer.

yschiebelhut commented on 2021-10-15 13:03

current version (11.0.1-1) of yay won't install packages with an error like

-> error fetching ubridge: fatal: cannot change to '/tmp/yaytmp-1000/': No such file or directory context: exit status 128

installing the named package "ubridge" worked fine by going back two commits in history (a62850c2)

JustinSB commented on 2021-08-19 08:19

It won't compile on a freshly downloaded image of Arm6 Raspberry Pi. All I have installed is base-devel and vim. The only way to get it to build on a stock Arm6 Raspberry Pi is to disable lto, by adding the options=('!lto') line to the PKGBUILD as detailed below by @mikoxyz

timxx commented on 2021-08-16 12:42

I can't access to "https://proxy.golang.org/github.com/%21jguer/aur/@v/v1.0.0.mod", is there any other way to upgrade yay? I can't use it for now because libalpm.so has been upgraded.

jonathon commented on 2021-08-07 01:54

Mr.Tao, if it's not a default option then it's the responsibility of the package builder, not of the PKGBUILD maintainer.

Mr.Tao commented on 2021-07-20 09:07

The package is indeed FTBFS with lto enabled. lto is a legal compiler option, thus the argument that lto is not enabled by default is not valid. It is the responsibility of the maintainer to filter out CFLAGS which are not compatible with the package.

madjoe commented on 2021-07-17 19:08

I encountered this issue with yay, but the maintainer claim it has nothing to do with yay. Could it be a packaging issue?

I tried to update python2-lxml, but for some reason the package is trying to build against python3.

https://github.com/Jguer/yay/issues/1554

masterberg commented on 2021-07-15 22:26

I came here to second what @mikoxyz said; yay should not be broken for users that use lto.

yrlf commented on 2021-07-13 19:09

I came here to second what @mikoxyz said; yay should not be broken for users that use lto.

mikoxyz commented on 2021-06-28 15:40

@yochananmarqos: True, but it doesn't hurt to disable it for those who do have lto enabled in their makepkg.conf