Package Details: yay 12.4.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: 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)

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 .. 35 Next › Last »

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)?

PanisSupraOmnia commented on 2021-03-14 15:19 (UTC)

@RidderJoris it looks like the date and time on your armv7 machine is way out of date, which lines up with the error message!

RidderJoris commented on 2021-03-14 11:05 (UTC) (edited on 2021-03-14 11:13 (UTC) by RidderJoris)

On armv7 I get the following error (after running yay -Syu):

:: (1/1) Parsing SRCINFO: yay
==> Making package: yay 10.1.2-2 (Thu Feb  4 07:39:03 2021)
==> Retrieving sources...
  -> Downloading yay-10.1.2.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   118  100   118    0     0    761      0 --:--:-- --:--:-- --:--:--   761
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (60) SSL certificate problem: certificate is not yet valid
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
==> ERROR: Failure while downloading https://github.com/Jguer/yay/archive/v10.1.2.tar.gz
    Aborting...
error downloading sources: yay

On x86 it doesn't seem to be a problem

crdx commented on 2021-02-01 09:03 (UTC)

@marcin You may have had something installed that had gcc as a dependency, and removed it? You can try grep gcc /var/log/pacman.log to figure it out.

marcin commented on 2021-02-01 00:09 (UTC)

@RubenKelevra I have been using yay on this PC for over 1 years now. Just yesterday I got this error, so I have base-devel installed. Maybe most recent arch update removed it? I don't know.