Package Details: yay 12.5.0-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: GPL-3.0-or-later
Submitter: jguer
Maintainer: jguer
Last Packager: jguer
Votes: 2326
Popularity: 27.01
First Submitted: 2016-10-05 17:20 (UTC)
Last Updated: 2025-04-24 09:06 (UTC)

Pinned Comments

jguer commented on 2024-03-16 08:06 (UTC)

yay: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory

This will happen if you upgrade pacman and yay separately If you have this error you need to manually recompile yay

pacman -S --needed git base-devel
git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si

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.

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 36 Next › Last »

craftyguy commented on 2021-05-17 19:11 (UTC)

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.

marcelroed commented on 2021-05-12 19:34 (UTC)

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

kwaxi commented on 2021-04-20 11:20 (UTC) (edited on 2021-04-20 11:20 (UTC) by kwaxi)

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...

Turbo commented on 2021-04-13 13:44 (UTC) (edited on 2021-04-13 13:46 (UTC) by Turbo)

hi,

There is this error when trying to build your last update

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: github.com/stretchr/testify@v1.7.0 requires
    github.com/pmezard/go-difflib@v1.0.0: reading github.com/pmezard/go-difflib/go.mod at revision v1.0.0: unknown revision v1.0.0
make: *** [Makefile:112 : yay] Erreur 1

VanClaussen commented on 2021-04-12 14:57 (UTC)

@Spixmaster Scheduled maintenance https://status.gocenter.io/

Spixmaster commented on 2021-04-12 14:32 (UTC)

The following error occurs:

go: github.com/Jguer/go-alpm/v2@v2.0.2: reading https://gocenter.io/github.com/%21jguer/go-alpm/v2/@v/v2.0.2.mod: 405 Not Allowed

Portista commented on 2021-03-29 17:56 (UTC)

@igel

Same for me, i use this for cleaning the orphan package but now i've got this error too

igel commented on 2021-03-21 22:29 (UTC)

Hi :)

since upgrading to 10.2.0, I get

~ $ yay -Qqdt exit status 1

is this a regression? Or am I using it wrong (I want to recursively detect unneeded packages as part of my standard update procedure)?