| 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: | 2286 |
| Popularity: | 26.53 |
| First Submitted: | 2016-10-05 17:20 (UTC) |
| Last Updated: | 2024-09-19 14:27 (UTC) |
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)
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
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.
Mr.Tao, if it's not a default option then it's the responsibility of the package builder, not of the PKGBUILD maintainer.
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.
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.
I came here to second what @mikoxyz said; yay should not be broken for users that use lto.
I came here to second what @mikoxyz said; yay should not be broken for users that use lto.
Pinned Comments
jguer commented on 2024-03-16 08:06 (UTC)
This will happen if you upgrade pacman and yay separately If you have this error you need to manually recompile yay
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.