Package Details: yay 12.4.2-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: 2251
Popularity: 23.92
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 .. 29 30 31 32 33 34 35 Next › Last »

Morganamilo commented on 2018-04-23 17:10 (UTC)

You can try to pass -d to skip versioned dependency checking but it's likely that there's a version specified for a reason.

You should open an issue on the GitHub page if you want to look for other fixes.

grunch commented on 2018-04-23 17:03 (UTC) (edited on 2018-04-23 17:15 (UTC) by grunch)

Encountering a similar error to @eimis: when I say yay -Syu, yay says:

Error: Could not find all required packages:
    boost-libs<1.66.0
https://pastebin.com/L1UDMz1B

When I say yay -Ss boost, I see these (descriptions removed): 

extra/boost-libs 1.66.0-2 (2.3 MiB 11.0 MiB) (Installed)
extra/boost 1.66.0-2 (11.3 MiB 152.4 MiB) (Installed)
There is no package boost-libs with a lower version number. Thoughts on how to fix this?

Thanks!

Det commented on 2018-04-16 07:57 (UTC)

Can't see why is that, if that stuff indeed would get replaced? They'd be most likely just AUR packages, otherwise it'd be a official repo problem and can't see how that'd pass [testing] (don't recall last time I had it in there either).

Morganamilo commented on 2018-04-09 00:36 (UTC)

git-core is ancient and was replaced by git a long time ago, so long ago infact that the git package no longer bothers to say it replaces git-core

You should remove git-core and install git then proceed with the update.

Or you can install yay-git where this has been fixed for a while. The fix should make it into the normal yay very soon.

Also looking at your log please NEVER use --force unless you know exactly what you are doing and especially never use it on a whole sysupgrade otherwise you're going to break your system.

eimis commented on 2018-04-08 23:46 (UTC)

yay says: Error: Could not find all required packages: git-core. And I can't upgrade packages. https://bpaste.net/show/1851079d09ce how can I fix this?

rkubosz commented on 2018-02-15 14:45 (UTC) (edited on 2018-02-15 14:46 (UTC) by rkubosz)

Hi! The patch below adds support for another ARM architecture: armv6h. I built it on my RaspberryPi v1 and it works so far. Feel free to apply it to PKGBUILD :-)

diff --git a/PKGBUILD b/PKGBUILD
index 12cb592..64a4155 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,7 +3,7 @@ pkgname=yay
 pkgver=2.303
 pkgrel=1
 pkgdesc="Yet another yogurt. Pacman wrapper and AUR helper written in go."
-arch=('i686' 'x86_64' 'armv7h' 'aarch64')
+arch=('i686' 'x86_64' 'armv7h' 'armv6h' 'aarch64')
 url="https://github.com/Jguer/yay"
 license=('GPL')
 options=('!strip' '!emptydirs')

jguer commented on 2017-12-06 01:00 (UTC)

Updated the PKGBUILD to export in the two scopes. Still haven't found a way to make package vendoring easier to use in PKGBUILDs.

egrupled commented on 2017-12-05 11:12 (UTC) (edited on 2017-12-05 11:14 (UTC) by egrupled)

I think I found it. At first I tried build it with pacaur and it failed. I tried then manually with makepkg and it worked.

It seems that pacaur discards env variables between prepare and build sections. It means it's better to set them twice like this:

prepare() {
  export GOPATH="${srcdir}/.go"
  export GOBIN="$GOPATH/bin"
  mkdir -p "$GOPATH"
  rm -rf "$GOPATH/src"
  ln -sf "$srcdir/$pkgname-$pkgver/vendor" "$GOPATH/src"
}

build() {
  export GOPATH="${srcdir}/.go"
  export GOBIN="$GOPATH/bin"
  cd "$srcdir/$pkgname-$pkgver"
  go build -v -o ${pkgname} -ldflags "-s -w -X main.version=${pkgver}"
}

jguer commented on 2017-12-05 03:20 (UTC)

Weird, just tried a clean build and it worked. It appears your $GOPATH is not being changed to the temporary one. I'm trying to reproduce it.

« First ‹ Previous 1 .. 29 30 31 32 33 34 35 Next › Last »