Package Details: yay 7.887-1

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: 139
Popularity: 46.409885
First Submitted: 2016-10-05 17:20
Last Updated: 2018-06-19 22:26

Latest Comments

Morganamilo commented on 2018-06-04 22:38

@emacsomancer That seems a little out of scale for AUR comments, you probably want to open an issue on github.

Two things do come to mind though, do you use any sort of vpn/proxies? And is your system time correct?

emacsomancer commented on 2018-06-04 22:32

I'm getting TLS handshake timeouts from time to time

jguer commented on 2018-06-01 09:04

I agree with Morganamilo, aurutils is a lot more thought around local repos. As for yay-git transition to yay, A lot of stuff has changed, not particularly breaking changes, but some staging time delivers a more stable release here. yay-git is rarely broken though so it should be ok to use most of the time, just with some incomplete or not optimized features.

Morganamilo commented on 2018-06-01 04:16

Then yay-git should work fine for you. There's also aurutils which I would say fits the whole local repo approach a lot more.

psi-jack commented on 2018-06-01 03:48

Well, the reason I use PKGDEST is because I build once and deploy into a custom repository that other systems install from. I use yay as my automation means to do this because during updates, it gets everything, and when its done, I have fully updated system and AUR packages re-distributed.

Morganamilo commented on 2018-06-01 03:40

A ton of changes went into -git recently to probably a while. The -git should be stable enough to use though.

If you want you can just keep to this version. Unsetting PKGDEST / Removing it from your makepkg.conf should get it working.

psi-jack commented on 2018-06-01 03:34

Yep, I was just reading about that in the issues, from discussions in the #archlinux-pacman channel (meant to be in #archlinux, but, oops)

And yep.. yay-git does resolve the problem. When will that be released to here?

Morganamilo commented on 2018-06-01 03:18

If you're using PKGDEST at all then Pacman 5.1 changed some stuff with that. Should be fixed in -git if you want to try that.

psi-jack commented on 2018-06-01 03:16

Recently I've been getting, since pacman 5.1.0 update, all AUR packages failing to install after being built:

==> Leaving fakeroot environment.
==> Signing package(s)...
  -> Created signature file google-chrome-67.0.3396.62-1-x86_64.pkg.tar.xz.sig.
==> Finished making: google-chrome 67.0.3396.62-1 (Thu 31 May 2018 11:04:43 PM EDT)
==> Cleaning up...
Could not find built package google-chrome-67.0.3396.62-1-x86_64.pkg

And yet, it's there in my specifically configured directory in makepkg.conf:

-rw-r--r-- 1 psi-jack users 53835768 May 31 23:04 google-chrome-67.0.3396.62-1-x86_64.pkg.tar.xz

jonathon commented on 2018-04-29 15:53

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

All comments