Anyone else getting this error while trying to upgrade this package?
-> error fetching yay-bin: fatal: not a git repository (or any of the parent directories): .git
context: exit status 128
Search Criteria
Package Details: yay-bin 12.1.3-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/yay-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | yay-bin |
| Description: | Yet another yogurt. Pacman wrapper and AUR helper written in go. Pre-compiled. |
| Upstream URL: | https://github.com/Jguer/yay |
| Keywords: | AUR go helper pacman wrapper |
| Licenses: | GPL3 |
| Conflicts: | yay |
| Provides: | yay |
| Submitter: | jguer |
| Maintainer: | jguer |
| Last Packager: | jguer |
| Votes: | 247 |
| Popularity: | 6.54 |
| First Submitted: | 2016-12-03 15:06 (UTC) |
| Last Updated: | 2023-09-15 09:32 (UTC) |
Dependencies (4)
- git (git-vfs, git-run-command-patch-git, git-git, git-fc)
- pacman (pacman-pb, pacman-fancy-progress-git, pacman-git)
- doas (opendoas) (optional) – privilege elevation
- sudo (nosudo, fake-sudo, polkit-fakesudo, sudo-git, doas-sudo-shim, fudo-git, sudo-selinux, doas-sudo-shim-minimal, sudo-hg) (optional) – privilege elevation
Required by (31)
- aconfmgr-git (requires yay) (optional)
- arch-update (requires yay) (optional)
- cleanupdate-git (requires yay) (optional)
- cmd-not-found (requires yay) (optional)
- fuzzy-pkg-finder (requires yay) (optional)
- fzpac-git (requires yay) (optional)
- idos-package-updater-script (requires yay)
- klaus-bin (requires yay)
- meta-package-manager (requires yay) (optional)
- octopi (requires yay) (optional)
- octopi-dev (requires yay) (optional)
- pac-util (requires yay) (optional)
- pac-util-git (requires yay) (optional)
- pacbro (requires yay) (optional)
- pacup-arch-git (requires yay) (optional)
- pak-bin (requires yay)
- pak-git (requires yay)
- parui-git (requires yay) (optional)
- pcmn-git (requires yay)
- pkg-listn (requires yay) (optional)
- Show 11 more...
Sources (3)
bbaster commented on 2022-06-20 16:24 (UTC)
tech commented on 2021-12-06 21:54 (UTC)
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")
Alterego commented on 2021-06-04 12:22 (UTC)
Oh yes i forgot to do that, thanks
kuluse commented on 2021-06-04 07:55 (UTC)
Alterego, I just reinstalled yay-bin following the pinned comment and there is no conflict anymore. Maybe you have another error
bulletmark commented on 2021-06-03 23:36 (UTC) (edited on 2021-06-03 23:41 (UTC) by bulletmark)
I've been using yay-bin on my Arch and Arch ARM boxes for ages. All of these have updated to pacman 6 and I have updated yay-bin to work on the Arch boxes but it fails to install on my Arch ARM boxes because of error yay-bin and pacman are in conflict (libalpm.so<13-64). On my Arch boxes, pacman 6 provides libalpm.so=13-64 but on Arch ARM pacman 6 provides libalpm.so=13-32. Changing the PKGBUILD to conflicts=('yay' 'libalpm.so<13') fixes this.
Alterego commented on 2021-06-03 23:29 (UTC)
Still conflicting after latest release
hexhu commented on 2021-06-01 03:15 (UTC)
pacman 6.0.0-2 conflicts with yay-bin
==> Installing package yay-bin with pacman -U...
loading packages...
resolving dependencies...
looking for conflicting packages...
:: yay-bin and pacman are in conflict (libalpm.so). Remove pacman? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: yay-bin and pacman are in conflict (libalpm.so>12-64)
==> WARNING: Failed to install built package(s).
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 support
Once they're released (and if you installed pacman 6 before)
# pacman -S --needed git base-devel
$ git clone https://aur.archlinux.org/yay-bin.git
# pacman -R yay-bin
$ cd yay-bin
$ makepkg -si
jpegxguy commented on 2021-01-11 21:36 (UTC)
If v10.1.2 supports pacman > 6, why the < 6 check in the depends array?
jguer commented on 2020-12-15 08:41 (UTC)
@maverick1 yay is built with versioned bindings meaning it requires a recompile when libalpm is updated. Right now building yay with -tags six will use the pacman6 bindings. This yay-bin was compiled without -tags six so will only be compatible with pacman5, once pacman6 is released I'll update yay-bin to build using -tags six by default
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-binbinaries compiled with pacman 6 supportOnce they're released (and if you installed pacman 6 before)