| 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: | 2282 |
| Popularity: | 25.43 |
| First Submitted: | 2016-10-05 17:20 (UTC) |
| Last Updated: | 2024-09-19 14:27 (UTC) |
Got a yay update earlier today and then just got pacman 6 a few moments ago, and now i get this when running yay:
"yay: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory"
Assumed that yay's update earlier today was for pacman 6 but perhaps not lol. Will try jguer's pinned suggestion and rebuild yay
EDIT: rebuilding yay as per jguer's suggestion worked
go: parsing $GOFLAGS: non-flag "six"
What can I do about this?
Why was this flagged as out-of-date? You just need to reinstall yay manually to resolve the libalpm issues
@marcelroed I had the same problem, downgraded to pacman 5.x instead of having a pacman 6 pre-release installed and it was fine.
With pacman 6 arriving a rebuild of yay will be necessary, if you upgrade pacman without upgrading yay at the same time, yay will not run after. I'm bumping the pkgrel so it shows up on the upgrade list (and will do so when pacman transitions from staging->core)
In case you end up with a non-functioning yay after the upgrade:
$ pacman -S --needed git base-devel
$ git clone https://aur.archlinux.org/yay.git
$ cd yay
$ makepkg -si
A recent upgrade in gcc-go seems to require a yay rebuild, but yay is incapable of rebuilding itself:
yay: error while loading shared libraries: libgo.so.16: cannot open shared object file: No such file or directory
Downloading the PKGBUILD and building/installing manually resolves this issue.
Using yay to update yay (10.2.1-1 -> 10.2.2-1) I get this error for some reason. I have the latest version of Go. What could be going wrong here? I've tried clearing the cache and retrying.
# github.com/Jguer/go-alpm/v2
../gopath/pkg/mod/github.com/!jguer/go-alpm/v2@v2.0.5/handle_six.go:32:10: could not determine kind of name for C.alpm_option_add_architecture
../gopath/pkg/mod/github.com/!jguer/go-alpm/v2@v2.0.5/handle_six.go:20:10: could not determine kind of name for C.alpm_option_get_architectures
../gopath/pkg/mod/github.com/!jguer/go-alpm/v2@v2.0.5/handle_six.go:38:10: could not determine kind of name for C.alpm_option_remove_architecture
../gopath/pkg/mod/github.com/!jguer/go-alpm/v2@v2.0.5/handle_six.go:26:10: could not determine kind of name for C.alpm_option_set_architectures
make: *** [Makefile:112: yay] Error 2
==> ERROR: A failure occurred in build().
Aborting...
error making: yay
Upgrade aur/yay 10.2.0-1 -> 10.2.1-1 failing on armv6l with the following message:
=> Starting build()...
pacman>6
go build -trimpath -mod=readonly -modcacherw -ldflags '-X "main.yayVersion=10.2.1" -X "main.localePath=/usr/share/locale/" -linkmode=external' -buildmode=pie -o yay
go: golang.org/x/sys@v0.0.0-20210309074719-68d13333faf2: unrecognized import path "golang.org/x/sys": https fetch: Get "https://golang.org/x/sys?go-get=1": net/http: TLS handshake timeout
make: *** [Makefile:112: yay] Error 1
==> ERROR: A failure occurred in build().
Aborting...
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.