It seems redundent to strip a binary that is already stripped in upstream. Unless this goes against the AUR submition guidelines for binary packages, why not remove this from the build? This patch works for me.
diff --git a/PKGBUILD b/PKGBUILD
index 06df7aa..7281848 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -14,6 +14,7 @@ optdepends=(
)
provides=('yay')
conflicts=('yay' 'libalpm.so<13')
+options=('!strip')
source_x86_64=("https://github.com/Jguer/yay/releases/download/v${pkgver}/${pkgname/-bin/}_${pkgver}_x86_64.tar.gz")
source_aarch64=("https://github.com/Jguer/yay/releases/download/v${pkgver}/${pkgname/-bin/}_${pkgver}_aarch64.tar.gz")
Pinned Comments
jguer commented on 2021-05-20 11:48 (UTC) (edited on 2021-06-04 16:36 (UTC) by jguer)
With pacman 6 arriving a rebuild of yay will be necessary, if you upgrade pacman without upgrading yay at the same time, yay will not run after.
It will take a bit to release the
yay-bin
binaries compiled with pacman 6 supportOnce they're released (and if you installed pacman 6 before)