@jguer Another method is to fetch the latest yay PKGBUILD yay -G yay
, update pacman, then build the new yay with makepkg
.
Search Criteria
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) |
Dependencies (5)
- git (git-gitAUR, git-glAUR)
- pacman (pacman-gitAUR, pacman-stable-fancy-progressAUR)
- go (go-gitAUR, gcc-go-gitAUR, gcc-go-snapshotAUR, gcc-go) (make)
- doasAUR (opendoas) (optional) – privilege elevation
- sudo (fake-sudoAUR, polkit-fakesudoAUR, sudo-gitAUR, doas-sudo-shimAUR, doas-sudo-shim-minimalAUR, sudo-hgAUR, sudo-selinuxAUR, fudo-gitAUR) (optional) – privilege elevation
Required by (37)
- aconfmgr-git (optional)
- arch-update (optional)
- arch-update-git (optional)
- axu
- axu-bin
- blender-launcher-git
- cleanupdate-git (optional)
- cmd-not-found (optional)
- etwas
- fuzzy-pkg-finder (optional)
- fzpac-git (optional)
- idos-package-updater-script
- kdeplasma-arch-update-notifier-git (optional)
- kdeplasma5-arch-update-notifier-git
- klaus-bin
- meta-package-manager (optional)
- octopi (optional)
- pac-util (optional)
- pac-util-git (optional)
- pacup-arch-git (optional)
- Show 17 more...
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 35 Next › Last »
wooptoo commented on 2019-10-23 17:16 (UTC)
AlexWayfer commented on 2019-10-23 12:41 (UTC)
@jguer, thank you, sorry.
jguer commented on 2019-10-23 12:12 (UTC) (edited on 2019-10-23 12:12 (UTC) by jguer)
WARNING: PACKAGER should have the format 'Example Name <email@address.invalid>'
AlexWayfer commented on 2019-10-23 12:09 (UTC)
WARNING: PACKAGER should have the format 'Example Name <email@address.invalid>'
flower commented on 2019-10-23 10:36 (UTC) (edited on 2019-10-23 10:39 (UTC) by flower)
sudo pacman -R yay
sudo pacman -Syu
cd yay # your old yay dir... otherwise follow new install
git pull
makepkg -si
cd ..
yay -Syu
worked for me :)
jguer commented on 2019-10-23 08:36 (UTC) (edited on 2019-10-23 08:45 (UTC) by jguer)
Having issues upgrading yay and pacman at the same time? Here is the proposed workaround for now.
yay -S yay-bin
sudo pacman -Syu
yay -S yay
yay-bin is a binary ready package with yay already compiled against v5.2, it does not require go to build. https://github.com/Jguer/yay/issues/1084
WSDMatty commented on 2019-10-22 14:42 (UTC) (edited on 2019-10-22 14:47 (UTC) by WSDMatty)
For those on the testing branch needing to manually update yay for the newest pacman. Here's a PKGBUILD.
# Maintainer: Jguer <joaogg3@gmail.com>
pkgname=yay
pkgver=9.4.0
pkgrel=1
pkgdesc="Yet another yogurt. Pacman wrapper and AUR helper written in go."
arch=('i686' 'x86_64' 'armv7h' 'armv6h' 'aarch64')
url="https://github.com/Jguer/yay"
license=('GPL')
depends=(
'pacman>=5.2.0'
'sudo'
'git'
)
makedepends=(
'go'
)
source=("${pkgname}-${pkgver}.tar.gz::https://github.com/Jguer/yay/archive/v${pkgver}.tar.gz")
sha1sums=('9e62c6e3d0bae7b6687717b07e3455ac9aa451cd')
build() {
cd "$srcdir/$pkgname-$pkgver"
EXTRA_GOFLAGS="-gcflags all=-trimpath=${PWD} -asmflags all=-trimpath=${PWD}" \
LDFLAGS="-linkmode external -extldflags \"${LDFLAGS}\"" \
make VERSION=$pkgver DESTDIR="$pkgdir" build
}
package() {
cd "$srcdir/$pkgname-$pkgver"
make VERSION=$pkgver DESTDIR="$pkgdir" PREFIX=/usr install
}
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.