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: 2327
Popularity: 26.77
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 .. 24 25 26 27 28 29 30 31 32 33 34 .. 36 Next › Last »

Morganamilo commented on 2018-12-28 17:01 (UTC)

By default sudo will cache your password for 5 minutes.

WFV commented on 2018-12-28 16:26 (UTC)

Thanks for yay. Is it normal when running % yay -Sua for some packages to simply install but others ask for sudo password? (I've never used any wrappers for doing bulk aur package updates, nor system updates.)

dosenpils commented on 2018-12-25 00:16 (UTC)

@twnaing I had the same error. I could fix it upgrading my installed package of "go".

eschwartz commented on 2018-12-24 18:44 (UTC)

@adizero you're not supposed to source this yourself. This installs a completion spec, but users who wish to use completions are supposed to install the bash-completion package as that both sets up the automatic lazy loading of completion specs, and contains the shared helper functions relied on by many command completions.

adizero commented on 2018-12-21 08:24 (UTC)

Shouldn't the bash-completion package be listed as an optional dependency? Without it an attempt to use the completion (after pressing <TAB>) fails. E.g.: $ source /usr/share/bash-completion/completions/yay $ yay bash: _get_comp_words_by_ref: command not found

twnaing commented on 2018-12-11 12:54 (UTC)

I am having the following error trying to update from version 8 to 9 using yay

==> Starting build()... go build -v -ldflags '-s -w -X main.version=9.0.1' -o yay -mod=vendor flag provided but not defined: -mod usage: build [-o output] [-i] [build flags] [packages] Run 'go help build' for details. make: *** [Makefile:51: build] Error 2 ==> ERROR: A failure occurred in build(). Aborting... Error making: yay

Morganamilo commented on 2018-12-08 21:22 (UTC)

@SirCmpwn Also are you building yay with makepkg or yay?

jguer commented on 2018-12-08 20:41 (UTC) (edited on 2018-12-08 20:41 (UTC) by jguer)

I cannot reproduce that, can you create an issue in the upstream URL? Something is turning off the GOCHACHE. I may have to revert the go modules patch

<deleted-account> commented on 2018-12-08 20:16 (UTC)

==> Extracting sources... -> Extracting yay-9.0.1.tar.gz with bsdtar ==> Starting build()... go build -v -ldflags '-s -w -X main.version=9.0.1' -o yay -mod=vendor go: disabling cache (/root/.cache/go-build) due to initialization failure: mkdir /root/.cache: permission denied go: cannot use modules with build cache disabled make: *** [Makefile:51: build] Error 1 ==> ERROR: A failure occurred in build().

Despite appearances, I'm not running makepkg as root.

« First ‹ Previous 1 .. 24 25 26 27 28 29 30 31 32 33 34 .. 36 Next › Last »