Package Details: yay 6.777-2

Git Clone URL: https://aur.archlinux.org/yay.git (read-only)
Package Base: yay
Description: Yet another yogurt. Pacman wrapper and AUR helper written in go.
Upstream URL: https://github.com/Jguer/yay
Keywords: AUR go helper pacman wrapper
Licenses: GPL
Conflicts: yay-bin, yay-git
Submitter: jguer
Maintainer: jguer
Last Packager: jguer
Votes: 99
Popularity: 30.818788
First Submitted: 2016-10-05 17:20
Last Updated: 2018-05-20 15:24

Latest Comments

jonathon commented on 2018-04-29 15:53

Sounds good. An AUR helper without git support isn't much of an AUR helper. ;)

jguer commented on 2018-04-29 11:17

Will do :)

Yay can still function, albeit limped, without git. We decided to change git to a hard dependency as unless you change the settings before first run to --nogitclone yay will crash and we've committed to making git a first class citizen.

I would only feel comfortable changing git to an optdepend if the source is changed to never crash in the absence of git (which is not that hard, just low priority right now).

jonathon commented on 2018-04-29 10:18

Please switch the source line to

source=("${pkgname}-${pkgver}.tar.gz::https://github.com/Jguer/yay/archive/v${pkgver}.tar.gz")

to avoid potential $SRCDEST conflicts with other packages which have the same version.

Is git a hard dependency for yay operation? If not, it's an optdepend rather than a depend. Otherwise carry on. :)

jguer commented on 2018-04-26 21:25

True, I'll add it and increase the pkgrel

Morganamilo commented on 2018-04-26 20:24

Git should probably be added as a hard dependency for all Yay variants now.

grunch commented on 2018-04-24 14:51

To "close" this thread (again, NOT a yay issue), the problem was with freecad-ose. I ran pacman -Sii boost-libs to determine all packages that depend on boost-libs. I looked at each of those packages with pacman -Si and learned that archlinuxcn/freecad-oce (a repo that I added) was the culprit that depends on boost-libs<1.66.0.

So, yay was mostly behaving properly, it was simply not telling me which package could not resolve its dependency.

grunch commented on 2018-04-23 17:44

Thanks for the suggestion @Morganamilo, but using -d made no difference. I'm thinking this is a local package issue due to the other warnings. I just ran trizen -Syu --aur and got similar, but slightly more descriptive warnings:

:: arm-frc-linux-gnueabi-frcmake-hg is unmaintained!
:: js was not found in AUR -- skipping
:: libcloudproviders was not found in AUR -- skipping
:: libhttpseverywhere was not found in AUR -- skipping
I'll spend some time cleaning up my installation and open an issue on github if I continue to have trouble with yay. Thanks!

Morganamilo commented on 2018-04-23 17:10

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

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

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).

All comments