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.
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: | 2319 |
Popularity: | 28.62 |
First Submitted: | 2016-10-05 17:20 (UTC) |
Last Updated: | 2024-09-19 14:27 (UTC) |
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.
@mikoxyz: lto
is not enabled by default.
@ozz It might be, but the AUR convention is the bare package name is the source build, *-bin
is the binary and *-git
is the source build of the tip of the git repo. I tend to look for the *-bin
versions of packages first if I can find them.
@crdx Yes, yay-bin is much better, thanks! I would argue that should be the default "yay" and there should be a "yay-src" or something. 600MB is a lot of space on constrained systems.
@ozz
You can use yay-bin if you don't want to have to build it locally. Although if you feel it's "not much more than a wrapper around git and makepkg" then maybe you'd rather not use it at all?
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.