AUR (en) - yay

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: yay 12.4.2-1

Package Actions

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:	2239
Popularity:	29.97
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 2 3 4 5 6 7 .. 35 Next › Last »

fwcd commented on 2024-08-21 22:01 (UTC)

The build failures relating to telemetry files may be an upstream issue: https://github.com/golang/go/issues/68946

carlosal1015 commented on 2024-08-17 01:08 (UTC) (edited on 2024-08-17 01:12 (UTC) by carlosal1015)

Not sure why when makepkg --noconfirm -si && rm -rf /tmp/makepkg.

==> Finished making: yay 12.3.5-1 (Fri Aug 16 20:05:36 2024)
==> Installing package yay with pacman -U...
loading packages...
resolving dependencies...
looking for conflicting packages...

Package (1)  New Version  Net Change

yay          12.3.5-1       8.85 MiB

Total Installed Size:  8.85 MiB

:: Proceed with installation? [Y/n] 
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
:: Processing package changes...
installing yay...
Optional dependencies for yay
    sudo: privilege elevation [installed]
    doas: privilege elevation
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
rm: cannot remove '/tmp/makepkg/yay/src/gopath/pkg/mod/golang.org/x/telemetry/config@v0.29.0/doc.go': Permission denied
rm: cannot remove '/tmp/makepkg/yay/src/gopath/pkg/mod/golang.org/x/telemetry/config@v0.29.0/go.mod': Permission denied
rm: cannot remove '/tmp/makepkg/yay/src/gopath/pkg/mod/golang.org/x/telemetry/config@v0.29.0/config.json': Permission denied
rm: cannot remove '/tmp/makepkg/yay/src/gopath/pkg/mod/golang.org/x/telemetry/config@v0.29.0/LICENSE': Permission denied

gromit commented on 2024-06-07 10:49 (UTC)

@kolay.ne, you are expected to have base-devel installed when building things from the AUR: https://wiki.archlinux.org/title/Arch_User_Repository#Getting_started

Please see my comment below which answers the exact same question :)

kolay.ne commented on 2024-06-07 10:41 (UTC)

yay makedepends on the make package. Please, add it to PKGBUILD

gromit commented on 2024-05-21 11:29 (UTC)

@jpoppe, you are expected to have base-devel installed when building things from the AUR: https://wiki.archlinux.org/title/Arch_User_Repository#Getting_started

jpoppe commented on 2024-05-21 09:52 (UTC)

FYI: make is missing from the build dependencies

talleyhoe commented on 2024-04-24 18:30 (UTC) (edited on 2024-04-24 18:32 (UTC) by talleyhoe)

If you're getting 'connection refused' errors, similar to @trougnouf, it's likely a DNS resolution issue. 'Go' queries /etc/resolv.conf directly. You may need to create a symbolic link if using iwd or another tool that uses systemd-resolved. See https://wiki.archlinux.org/title/Systemd-resolved#DNS

# sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

Not sure why building in a clean chroot would help... but it shouldn't be necessary!

whaler commented on 2024-04-04 21:20 (UTC) (edited on 2024-04-04 21:42 (UTC) by whaler)

I succeded in installing yay by changing 'SigLevel = Required DatabaseOptional' to 'SigLevel = Never'. This has not been a problem before. What should I put in 'SigLevel = ' in order to avoid this problem.

Also, when I start yay, it keeps repeating this question:

:: Synkroniserer pakkedatabaser... core er oppdatert extra 8,1 MiB 1898 KiB/s 00:04 [############################################################################] 100% :: Searching AUR for updates... :: There are 7 providers available for java-runtime: :: Repository extra 1) jdk-openjdk 2) jdk21-openjdk 3) jre-openjdk 4) jre11-openjdk 5) jre17-openjdk 6) jre21-openjdk 7) jre8-openjdk

It does not matter which number I choose, it repeats the question.

I don't have any Java installed at this time, so what is this?

whaler commented on 2024-03-29 05:49 (UTC) (edited on 2024-03-29 05:52 (UTC) by whaler)

Regarding the libalpm.so.13 problem: When using the git clone method, I am told the package (yay) is missing required signature. This has not been an issue before.