Package Details: yay 11.2.0-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: GPL3
Submitter: jguer
Maintainer: jguer
Last Packager: jguer
Votes: 1788
Popularity: 40.64
First Submitted: 2016-10-05 17:20 (UTC)
Last Updated: 2022-06-17 08:27 (UTC)

Pinned Comments

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

iyanmv commented on 2022-02-04 23:20 (UTC) (edited on 2022-02-04 23:21 (UTC) by iyanmv)

Before writing that yay doesn't work and that you are getting:

response decoding failed: invalid character '<' looking for beginning of value

Check these links:

https://github.com/Jguer/yay/issues/1684

https://github.com/Jguer/yay/issues/1682

dimytch commented on 2022-01-26 23:20 (UTC)

yay -Syu yay ...

go: downloading golang.org/x/text v0.3.7
# runtime/cgo
In file included from /usr/include/errno.h:28,
                 from cgo-gcc-prolog:30:
/usr/include/bits/errno.h:26:11: фатальная ошибка: linux/errno.h: Нет такого файла или каталога
   26 | # include <linux/errno.h>
      |           ^~~~~~~~~~~~~~~
компиляция прервана.
make: *** [Makefile:111: yay] Ошибка 2
==> ОШИБКА: Произошел сбой в build().
    Прерывание...
 -> ошибка сборки: yay

pgoetz commented on 2022-01-08 11:21 (UTC)

@alerque I'm not following your suggestion -- how would one do this with modifying the PKGBUILD, at which point you're not using yay?

alerque commented on 2022-01-08 08:13 (UTC)

@RAMChYLD Just compile with extra-x86_64-build from the devtools package. That way you don't have to worry about what is on your host system at all and the build will just happen with the dependencies it needs and nothing else.

callmejoe commented on 2022-01-05 20:02 (UTC)

@RAMChYLD your comment will probably not be read by the developer. better off creating a new issue on the github page. https://github.com/Jguer/yay

RAMChYLD commented on 2022-01-05 19:55 (UTC)

Can you make it so yay can alternatively use gcc-go as it's compiler? The 11.1.0 package insisted that I uninstall gcc-go and install Google's go compiler instead. After it completed it's task I found that it uninstalled go, but I had to manually reinstall gcc-go. If only it can just skip the step and compile using gcc-go.

yochananmarqos commented on 2021-12-04 23:24 (UTC)

@Danik2343: Sorry, but an AUR helper will never be in the Arch repo. You should already know why if you read the wiki.

Danik2343 commented on 2021-12-04 22:09 (UTC) (edited on 2021-12-04 22:10 (UTC) by Danik2343)

Очень хорошо работает, проверяет обновления в АУРЕ и в ПакМане. В кеше программы сохряняются исходники установленного софта. Голосую за то, чтобы пакет перенаправили в категорию Community /// Works very well, checks for updates in AUR and Pacman. The source codes of the installed software are stored in the program cache. Vote for the package to be redirected to the Community category

jonathon commented on 2021-10-16 17:09 (UTC)

@yschiebelhut, that is not an issue with this PKGBUILD. If you think it is a bug in yay then report on the GitHub issue tracker. if you think it's a bug with the ubridge PKGBUILD then report to that package's maintainer.

yschiebelhut commented on 2021-10-15 13:03 (UTC)

current version (11.0.1-1) of yay won't install packages with an error like

-> error fetching ubridge: fatal: cannot change to '/tmp/yaytmp-1000/': No such file or directory context: exit status 128

installing the named package "ubridge" worked fine by going back two commits in history (a62850c2)

JustinSB commented on 2021-08-19 08:19 (UTC)

It won't compile on a freshly downloaded image of Arm6 Raspberry Pi. All I have installed is base-devel and vim. The only way to get it to build on a stock Arm6 Raspberry Pi is to disable lto, by adding the options=('!lto') line to the PKGBUILD as detailed below by @mikoxyz

timxx commented on 2021-08-16 12:42 (UTC)

I can't access to "https://proxy.golang.org/github.com/%21jguer/aur/@v/v1.0.0.mod", is there any other way to upgrade yay? I can't use it for now because libalpm.so has been upgraded.

jonathon commented on 2021-08-07 01:54 (UTC)

Mr.Tao, if it's not a default option then it's the responsibility of the package builder, not of the PKGBUILD maintainer.

Mr.Tao commented on 2021-07-20 09:07 (UTC)

The package is indeed FTBFS with lto enabled. lto is a legal compiler option, thus the argument that lto is not enabled by default is not valid. It is the responsibility of the maintainer to filter out CFLAGS which are not compatible with the package.

madjoe commented on 2021-07-17 19:08 (UTC)

I encountered this issue with yay, but the maintainer claim it has nothing to do with yay. Could it be a packaging issue?

I tried to update python2-lxml, but for some reason the package is trying to build against python3.

https://github.com/Jguer/yay/issues/1554

masterberg commented on 2021-07-15 22:26 (UTC)

I came here to second what @mikoxyz said; yay should not be broken for users that use lto.

yrlf commented on 2021-07-13 19:09 (UTC)

I came here to second what @mikoxyz said; yay should not be broken for users that use lto.

mikoxyz commented on 2021-06-28 15:40 (UTC)

@yochananmarqos: True, but it doesn't hurt to disable it for those who do have lto enabled in their makepkg.conf

yochananmarqos commented on 2021-06-20 14:15 (UTC)

@mikoxyz: lto is not enabled by default.

mikoxyz commented on 2021-06-20 06:37 (UTC) (edited on 2021-06-20 06:39 (UTC) by mikoxyz)

This package doesn't build with lto enabled; this patch disables lto for this package

diff --git a/PKGBUILD b/PKGBUILD
index 2aa659e..316d638 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -16,6 +16,7 @@ optdepends=(
 makedepends=(
   'go'
 )
+options=('!lto')
 source=("${pkgname}-${pkgver}.tar.gz::https://github.com/Jguer/yay/archive/v${pkgver}.tar.gz")
 sha256sums=('1782cd4f96c56cc3c92b9fc904873a15a95aecba09dc22c8a6a37a092a1d20cf')

crdx commented on 2021-06-12 22:57 (UTC)

@ozz It might be, but the AUR convention is the bare package name is the source build, *-bin is the binary and *-git is the source build of the tip of the git repo. I tend to look for the *-bin versions of packages first if I can find them.

ozz commented on 2021-06-12 22:54 (UTC)

@crdx Yes, yay-bin is much better, thanks! I would argue that should be the default "yay" and there should be a "yay-src" or something. 600MB is a lot of space on constrained systems.

crdx commented on 2021-06-12 09:58 (UTC)

@ozz

You can use yay-bin if you don't want to have to build it locally. Although if you feel it's "not much more than a wrapper around git and makepkg" then maybe you'd rather not use it at all?

ozz commented on 2021-06-12 01:52 (UTC)

A 600MB "go" dependency for something not much more than a wrapper around git and makepkg... seems... wrong.

This is not the way, man.

leccesg commented on 2021-06-10 06:38 (UTC)

I used sudo pacman -Rcsn yay. After uninstalling, I reinstalled, but I received an error.

[taizongh@ZhuFengGeShi ~]$ sudo pacman -S --needed git base-devel
[sudo] taizongh password:
Warning: Git-2.32.0-1 is already up to date -- skip
Warning: autoconf-2.71-1 is already up to date -- skipped
Warning: Automake -1.16.3-1 has been updated -- Skip
Warning: Binutils -2.36.1-3 is already up to date -- skip
Warning: BIS-3.7.6-1 is already up to date -- skip
Warning: Fakeroot -1.25.3-2 has been updated -- Skip
Warning: File -5.40-5 has been updated -- Skip
Warning: findutils-4.8.0-1 is already up to date -- skip
Warning: Flex-2.6.4-3 is already up to date -- skip
Warning: GAWK-5.1.0-1 has been updated -- Skip
Warning: GCC-11.1.0-1 is already up to date -- skip
Warning: gettext-0.21-1 is already up to date -- skipped
Warning: grep-3.6-1 is already up to date -- skip
Warning: Groff-1.22.4-5 is already up to date -- skip
Warning: gzip-1.10-3 is already up to date -- skip
Warning: libtool-2.4.6+42+gb88cebd5-16 has been updated -- Skip
Warning: M4-1.4.18-3 is already up to date -- skip
Warning: make-4.3-3 is already up to date -- skip
Warning: pacman-6.0.0-2 is already up to date -- skip
Warning: Patch-2.7.6-8 is already up to date -- skip
Warning: pkgconf-1.7.3-1 is already up to date -- skipped
Warning: sed-4.8-1 is already up to date -- skipped
Warning: sudo-1.9.7-1 has been updated -- skipped
Warning: Texinfo-6.7-3 has been updated -- Skipped
Warning: Which -2.21-5 is already up to date -- skip
There is nothing to do today
[taizongh@ZhuFengGeShi ~]$ git clone https://aur.archlinux.org/yay.git
Cloning to 'Yay '...
remote: Enumerating objects: 390, done.
remote: Counting objects: 100% (390/390), done.
remote: Compressing objects: 100% (289/289), done.
remote: Total 390 (delta 98), reused 389 (delta 98), pack-reused 0
Receiving object: 100% (390/390), 81.85 KiB | KiB/s, 135.00.
Process delta: 100% (98/98), done.
[taizongh@ZhuFengGeShi ~]$ cd yay
[taizongh@ZhuFengGeShi yay]$ makepkg -si
==> is creating package: yay 10.2.3-1 (Thu Jun 10, 2021 22:18:12)
==> is checking runtime dependencies...
==> is checking compile-time dependencies
==> Get the source code...
-> is downloading yay-10.2.3.tar.gz...
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100 118 100 118 00 34 0 0:00:03 0:00:03 --:--:-- 34
100  346k  100  346k    0     0   4601      0  0:01:17  0:01:17 --:--:--  5808
==> - use SHA256sums...
Yay - 10.2.3. Tar. Gz... through
==> is releasing the source code...
-> is unzipping yay-10.2.3.tar.gz, using bsdtar
==> is starting to build()...
Go build-trimpath -mod= readonly-modcacherw -tags six-ldFlags' -x "main.yayVersion=10.2.3" -x "main.localePath=/usr/share/locale/" -linkmode=external' -buildmode=pie -o yay
Go: github.com/Jguer/go-alpm/v2@v2.0.5: Get "https://proxy.golang.org/github.com/%21jguer/go-alpm/v2/@v/v2.0.5.mod" : Dial TCP 172.217.160.115:443: I/O timeout
Make: *** [Makefile:112: yay] error 1
==> error: An error occurred in build().
Is giving up...

pgoetz commented on 2021-06-06 14:43 (UTC)

@yochananmarqos Ah, ok; so the user's pacman installation is corrupted. In any case, this doesn't have anything to do with yay.

yochananmarqos commented on 2021-06-06 14:34 (UTC)

@pgoetz: Of course you do. libalpm.so is part of pacman. Run pacman -Fx libalpm.so.

pgoetz commented on 2021-06-06 12:02 (UTC) (edited on 2021-06-06 12:04 (UTC) by pgoetz)

@6543 I just rebuilt and used yay yesterday and don't even have libalpm installed:

[pgoetz@gecko ~]$ pacman -Q | grep libalpm
[pgoetz@gecko ~]$

[pgoetz@gecko ~]$ yay -Syu
[sudo] password for pgoetz: 
:: Synchronizing package databases...
...

6543 commented on 2021-06-06 02:32 (UTC)

building yay with makepkg work, using it fail:

yay: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory

there only exist a libalpm.so.13
Pacman v6.0.0 - libalpm v13.0.0

pgoetz commented on 2021-06-05 20:28 (UTC)

@jguer what does the -$i flag do in makepkg?

Yatis commented on 2021-06-05 14:13 (UTC)

@friday13 I have removed yay using pacman -Rns yay. Then, when I'm trying to rebuild it using makepkg -si, the building step throw me an Aborting... because -Werror is used somewhere (makepkg -Cfsi give me the same result).

friday13 commented on 2021-06-05 13:00 (UTC)

@Yatis https://github.com/Jguer/yay/issues/1087

jguer commented on 2021-06-03 19:36 (UTC)

@kseistrup please create an issue on https://github.com/Jguer/yay this issue may require more investigation than a simple reply (I think it's a gcc-go vs go issue)

Yatis commented on 2021-06-03 19:11 (UTC)

I also got a yay error yay: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory. And when I try to rebuild the package, I have some log errors:

go build -trimpath -mod=readonly -modcacherw -tags six -ldflags '-X "main.yayVersion=10.2.2.r5.g059ca9d" -X "main.localePath=/usr/share/locale/" -linkmode=external' -buildmode=pie -o yay
go: downloading github.com/Jguer/go-alpm/v2 v2.0.5
go: downloading github.com/Morganamilo/go-pacmanconf v0.0.0-20210502114700-cff030e927a5
go: downloading github.com/Morganamilo/go-srcinfo v1.0.0
go: downloading github.com/leonelquinteros/gotext v1.4.0
go: downloading github.com/mikkeloscar/aur v0.0.0-20200113170522-1cb4e2949656
go: downloading github.com/pkg/errors v0.9.1
go: downloading golang.org/x/term v0.0.0-20210503060354-a79de5458b56
go: downloading github.com/stretchr/testify v1.7.0
go: downloading golang.org/x/sys v0.0.0-20210507161434-a76c4d0a0096
go: downloading github.com/pmezard/go-difflib v1.0.0
go: downloading gopkg.in/yaml.v3 v3.0.0-20210107192922-496545a6307b
go: downloading github.com/davecgh/go-spew v1.1.1
# runtime/cgo
gcc_fatalf.c: In function ‘fatalf’:
gcc_fatalf.c:17:9: error: implicit declaration of function ‘fprintf’ [-Werror=implicit-function-declaration]
   17 |         fprintf(stderr, "runtime/cgo: ");
      |         ^~~~~~~
gcc_fatalf.c:11:1: note: include ‘<stdio.h>’ or provide a declaration of ‘fprintf’
   10 | #include "libcgo.h"
  +++ |+#include <stdio.h>
   11 |
gcc_fatalf.c:17:9: error: incompatible implicit declaration of built-in function ‘fprintf’ [-Werror=builtin-declaration-mismatch]
   17 |         fprintf(stderr, "runtime/cgo: ");
      |         ^~~~~~~
gcc_fatalf.c:17:9: note: include ‘<stdio.h>’ or provide a declaration of ‘fprintf’
gcc_fatalf.c:19:9: error: implicit declaration of function ‘vfprintf’ [-Werror=implicit-function-declaration]
   19 |         vfprintf(stderr, format, ap);
      |         ^~~~~~~~
gcc_fatalf.c:19:9: note: include ‘<stdio.h>’ or provide a declaration of ‘vfprintf’
gcc_fatalf.c:22:9: error: implicit declaration of function ‘abort’ [-Werror=implicit-function-declaration]
   22 |         abort();
      |         ^~~~~
gcc_fatalf.c:11:1: note: include ‘<stdlib.h>’ or provide a declaration of ‘abort’
   10 | #include "libcgo.h"
  +++ |+#include <stdlib.h>
   11 |
gcc_fatalf.c:22:9: error: incompatible implicit declaration of built-in function ‘abort’ [-Werror=builtin-declaration-mismatch]
   22 |         abort();
      |         ^~~~~
gcc_fatalf.c:22:9: note: include ‘<stdlib.h>’ or provide a declaration of ‘abort’
cc1: all warnings being treated as errors
make: *** [Makefile:112: yay] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

I don't know who is the f** genius which use -Werror in production, but I'm not able to remove the cursed flags because I don't know where it is... Any idea ?

abdulhakeem commented on 2021-06-02 02:51 (UTC) (edited on 2021-06-02 02:53 (UTC) by abdulhakeem)

Got a yay update earlier today and then just got pacman 6 a few moments ago, and now i get this when running yay:

"yay: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory"

Assumed that yay's update earlier today was for pacman 6 but perhaps not lol. Will try jguer's pinned suggestion and rebuild yay

EDIT: rebuilding yay as per jguer's suggestion worked

kseistrup commented on 2021-06-01 08:29 (UTC)

go: parsing $GOFLAGS: non-flag "six"

What can I do about this?

mudkipscience commented on 2021-06-01 05:51 (UTC) (edited on 2021-06-01 05:53 (UTC) by mudkipscience)

Why was this flagged as out-of-date? You just need to reinstall yay manually to resolve the libalpm issues

edolnx commented on 2021-05-26 01:34 (UTC)

@marcelroed I had the same problem, downgraded to pacman 5.x instead of having a pacman 6 pre-release installed and it was fine.

jguer commented on 2021-05-20 11:41 (UTC)

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. I'm bumping the pkgrel so it shows up on the upgrade list (and will do so when pacman transitions from staging->core)

In case you end up with a non-functioning yay after the upgrade:

$ pacman -S --needed git base-devel
$ git clone https://aur.archlinux.org/yay.git
$ cd yay
$ makepkg -si

craftyguy commented on 2021-05-17 19:11 (UTC)

A recent upgrade in gcc-go seems to require a yay rebuild, but yay is incapable of rebuilding itself:

yay: error while loading shared libraries: libgo.so.16: cannot open shared object file: No such file or directory

Downloading the PKGBUILD and building/installing manually resolves this issue.

marcelroed commented on 2021-05-12 19:34 (UTC)

Using yay to update yay (10.2.1-1 -> 10.2.2-1) I get this error for some reason. I have the latest version of Go. What could be going wrong here? I've tried clearing the cache and retrying.

# github.com/Jguer/go-alpm/v2
../gopath/pkg/mod/github.com/!jguer/go-alpm/v2@v2.0.5/handle_six.go:32:10: could not determine kind of name for C.alpm_option_add_architecture
../gopath/pkg/mod/github.com/!jguer/go-alpm/v2@v2.0.5/handle_six.go:20:10: could not determine kind of name for C.alpm_option_get_architectures
../gopath/pkg/mod/github.com/!jguer/go-alpm/v2@v2.0.5/handle_six.go:38:10: could not determine kind of name for C.alpm_option_remove_architecture
../gopath/pkg/mod/github.com/!jguer/go-alpm/v2@v2.0.5/handle_six.go:26:10: could not determine kind of name for C.alpm_option_set_architectures
make: *** [Makefile:112: yay] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
error making: yay

kwaxi commented on 2021-04-20 11:20 (UTC) (edited on 2021-04-20 11:20 (UTC) by kwaxi)

Upgrade aur/yay 10.2.0-1 -> 10.2.1-1 failing on armv6l with the following message:


=> Starting build()...
pacman>6
go build -trimpath -mod=readonly -modcacherw  -ldflags '-X "main.yayVersion=10.2.1" -X "main.localePath=/usr/share/locale/" -linkmode=external' -buildmode=pie -o yay
go: golang.org/x/sys@v0.0.0-20210309074719-68d13333faf2: unrecognized import path "golang.org/x/sys": https fetch: Get "https://golang.org/x/sys?go-get=1": net/http: TLS handshake timeout
make: *** [Makefile:112: yay] Error 1
==> ERROR: A failure occurred in build().
    Aborting...

Turbo commented on 2021-04-13 13:44 (UTC) (edited on 2021-04-13 13:46 (UTC) by Turbo)

hi,

There is this error when trying to build your last update

go build -trimpath -mod=readonly -modcacherw  -ldflags '-X "main.yayVersion=10.2.1" -X "main.localePath=/usr/share/locale/" -linkmode=external' -buildmode=pie -o yay
go: github.com/stretchr/testify@v1.7.0 requires
    github.com/pmezard/go-difflib@v1.0.0: reading github.com/pmezard/go-difflib/go.mod at revision v1.0.0: unknown revision v1.0.0
make: *** [Makefile:112 : yay] Erreur 1

VanClaussen commented on 2021-04-12 14:57 (UTC)

@Spixmaster Scheduled maintenance https://status.gocenter.io/

Spixmaster commented on 2021-04-12 14:32 (UTC)

The following error occurs:

go: github.com/Jguer/go-alpm/v2@v2.0.2: reading https://gocenter.io/github.com/%21jguer/go-alpm/v2/@v/v2.0.2.mod: 405 Not Allowed

Portista commented on 2021-03-29 17:56 (UTC)

@igel

Same for me, i use this for cleaning the orphan package but now i've got this error too

igel commented on 2021-03-21 22:29 (UTC)

Hi :)

since upgrading to 10.2.0, I get

~ $ yay -Qqdt exit status 1

is this a regression? Or am I using it wrong (I want to recursively detect unneeded packages as part of my standard update procedure)?

PanisSupraOmnia commented on 2021-03-14 15:19 (UTC)

@RidderJoris it looks like the date and time on your armv7 machine is way out of date, which lines up with the error message!

RidderJoris commented on 2021-03-14 11:05 (UTC) (edited on 2021-03-14 11:13 (UTC) by RidderJoris)

On armv7 I get the following error (after running yay -Syu):

:: (1/1) Parsing SRCINFO: yay
==> Making package: yay 10.1.2-2 (Thu Feb  4 07:39:03 2021)
==> Retrieving sources...
  -> Downloading yay-10.1.2.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   118  100   118    0     0    761      0 --:--:-- --:--:-- --:--:--   761
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (60) SSL certificate problem: certificate is not yet valid
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
==> ERROR: Failure while downloading https://github.com/Jguer/yay/archive/v10.1.2.tar.gz
    Aborting...
error downloading sources: yay

On x86 it doesn't seem to be a problem

crdx commented on 2021-02-01 09:03 (UTC)

@marcin You may have had something installed that had gcc as a dependency, and removed it? You can try grep gcc /var/log/pacman.log to figure it out.

marcin commented on 2021-02-01 00:09 (UTC)

@RubenKelevra I have been using yay on this PC for over 1 years now. Just yesterday I got this error, so I have base-devel installed. Maybe most recent arch update removed it? I don't know.

RubenKelevra commented on 2021-01-31 11:33 (UTC)

@marcin it's user error. All AUR packages expect you to have base-devel installed.

marcin commented on 2021-01-31 11:06 (UTC)

Suddenly started getting the following error:

runtime/cgo
# runtime/cgo
cgo: exec /missing-cc: fork/exec /missing-cc: no such file or directory
make: *** [Makefile:112: yay] Error 2

To solve the issue, installing gcc was enough:

sudo pacman -S gcc

rageltman commented on 2021-01-31 03:44 (UTC)

Seems to be breaking all of a sudden in a clean chroot build by CI:

# net
cgo: cannot load DWARF output from $WORK/b054//_cgo_.o: decoding dwarf section info at offset 0x0: too short
github.com/Morganamilo/go-pacmanconf/ini
vendor/golang.org/x/sys/cpu
vendor/golang.org/x/crypto/chacha20poly1305
log
github.com/pmezard/go-difflib/difflib
github.com/leonelquinteros/gotext/plurals
net/url
mime
encoding/hex
encoding/json
vendor/golang.org/x/crypto/curve25519
compress/flate
vendor/golang.org/x/net/http2/hpack
encoding/gob
github.com/Jguer/go-alpm/v2
math/big
vendor/golang.org/x/text/unicode/norm
gopkg.in/yaml.v3
github.com/davecgh/go-spew/spew
vendor/golang.org/x/text/unicode/bidi
mime/quotedprintable
net/http/internal
flag
runtime/trace
github.com/Morganamilo/go-srcinfo
github.com/Morganamilo/go-pacmanconf
github.com/pkg/errors
encoding/xml
# github.com/Jguer/go-alpm/v2
cgo: cannot load DWARF output from $WORK/b036//_cgo_.o: decoding dwarf section info at offset 0x0: too short
compress/gzip
testing
vendor/golang.org/x/text/secure/bidirule
golang.org/x/term
vendor/golang.org/x/net/idna
crypto/dsa
encoding/asn1
crypto/rand
crypto/elliptic
crypto/ed25519
crypto/rsa
crypto/x509/pkix
vendor/golang.org/x/crypto/cryptobyte
crypto/ecdsa
make: *** [Makefile:112: yay] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Build failed, check /var/abs/chroot/yay/build

ava1ar commented on 2021-01-27 14:17 (UTC)

@jguer

Can you please make sudo an optional dependency (optdepends). In the light of the critical vulnerability in sudo some people may want to get rid of sudo on their systems and replace it with some alternatives like su, doas or pkexec.

liamtimms commented on 2021-01-27 00:28 (UTC)

@mcdragon "DistroTube" is low info click-bait. Disregard it.

jguer commented on 2021-01-26 10:15 (UTC)

@mcdragon

Yay is still maintained and will keep receiving updates (ex: pacman 6 support).

I am more focused on making the interfaces on yay more stable and developer friendly, of testing components to avoid them breaking between fixes, checking for bottlenecks. In terms of feature amount you may want to try Paru, Morganamilo has a lot of experience and wisdom on the subject.

This last year has been atypical which also hasn't allowed me to dedicate as much time as I wanted to yay but expect this maintainability focus (as opposed to feature focus) to last at least until summer.

mcdragon commented on 2021-01-26 09:54 (UTC)

Distrotube stated that yay not supported anymore. https://www.youtube.com/watch?v=w3j3tivcm50 Is this true? He is advising switching to paru which is maintaned by Morganamilo

chovy commented on 2021-01-04 11:18 (UTC)

golang.org/x/term make: *** [Makefile:112: yay] Error 1 ==> ERROR: A failure occurred in build(). Aborting...

yochananmarqos commented on 2020-12-21 01:13 (UTC)

@cmonty14 Sality HenryM: Please read the pinned comment. I would consider posting unformatted logs spam, myself.

HenryM commented on 2020-12-20 18:53 (UTC)

latest update refused to build because "Program 'a2x' not found" turns out it's a part of "asciidoc" after installing the ascii & asciidoc packages yay updated without a problem.

Sality commented on 2020-12-13 07:06 (UTC)

$ yay -Syu SIGILL: illegal instruction PC=0x55aabe61ee94 m=0 sigcode=2 instruction bytes: 0xc5 0xfa 0x6f 0x3 0x48 0x89 0xc7 0xc5 0xfa 0x7f 0x0 0x48 0x8b 0x43 0x10 0x48

goroutine 0 [idle]: runtime: unknown pc 0x55aabe61ee94 stack: frame={sp:0x7fffe6a61d80, fp:0x0} stack=[0x7fffe6262e70,0x7fffe6a61eb0) 00007fffe6a61c80: 0000000000203000 0000000000203000 00007fffe6a61c90: 0000000000203000 00007f863ce08d59 00007fffe6a61ca0: 000055aabe95f1c0 0000000000000000 00007fffe6a61cb0: 0000000000000000 000000c000000780 00007fffe6a61cc0: 0000000000000020 0000000000000018 00007fffe6a61cd0: 000000c000000002 0000000000000180 00007fffe6a61ce0: 0000000000000178 0000000000000000 00007fffe6a61cf0: 0000003000000002 0000000000000000 00007fffe6a61d00: 0000000000000000 0000000000000000 00007fffe6a61d10: 000000770000005b 0000007c0000006e 00007fffe6a61d20: 000000c000000900 0000000000000000 00007fffe6a61d30: 0000000000000018 ffffffffffffffb0 00007fffe6a61d40: 0000000000000000 000055aabe6891d4 00007fffe6a61d50: 0000000000000000 00007f863ce09d04 00007fffe6a61d60: 00007fffe6a61df8 00007fffe6a61e10 00007fffe6a61d70: 00000000000000f1 000055aabe61ee8f 00007fffe6a61d80: <00007fffe6a61df8 000055aabe3396a7 <runtime.asmcgocall+167> 00007fffe6a61d90: 00007fffe6a61dd0 000055aabe30fbb3 <runtime.malg+51> 00007fffe6a61da0: 000055aabe733f20 000000c000000900 00007fffe6a61db0: 0000000000000400 00007fffe6a61dd8 00007fffe6a61dc0: 0000000000000000 0000e3408a7f87cc 00007fffe6a61dd0: 00007fffe6a61e10 000055aabe30b526 <runtime.newm1+166> 00007fffe6a61de0: 000055aabe61ee80 00007fffe6a61df8 00007fffe6a61df0: 000055aabe30dbf3 <runtime.schedule+403> 000000c000000900 00007fffe6a61e00: 000000c000038488 000055aabe30a140 <runtime.mstart+0> 00007fffe6a61e10: 00007fffe6a61e48 000055aabe30b3dd <runtime.newm+157> 00007fffe6a61e20: 000000c000038400 000055aabe736430 00007fffe6a61e30: ffffffffffffffff 000000c000038400 00007fffe6a61e40: 000000c000038400 00007fffe6a61e70 00007fffe6a61e50: 000055aabe332345 <runtime.main.func1+69> 000055aabe736430 00007fffe6a61e60: 0000000000000000 ffffffffffffffff 00007fffe6a61e70: 000000c0000347d0 000055aabe337d23 <runtime.systemstack+99> runtime: unknown pc 0x55aabe61ee94 stack: frame={sp:0x7fffe6a61d80, fp:0x0} stack=[0x7fffe6262e70,0x7fffe6a61eb0) 00007fffe6a61c80: 0000000000203000 0000000000203000 00007fffe6a61c90: 0000000000203000 00007f863ce08d59 00007fffe6a61ca0: 000055aabe95f1c0 0000000000000000 00007fffe6a61cb0: 0000000000000000 000000c000000780 00007fffe6a61cc0: 0000000000000020 0000000000000018 00007fffe6a61cd0: 000000c000000002 0000000000000180 00007fffe6a61ce0: 0000000000000178 0000000000000000 00007fffe6a61cf0: 0000003000000002 0000000000000000 00007fffe6a61d00: 0000000000000000 0000000000000000 00007fffe6a61d10: 000000770000005b 0000007c0000006e 00007fffe6a61d20: 000000c000000900 0000000000000000 00007fffe6a61d30: 0000000000000018 ffffffffffffffb0 00007fffe6a61d40: 0000000000000000 000055aabe6891d4 00007fffe6a61d50: 0000000000000000 00007f863ce09d04 00007fffe6a61d60: 00007fffe6a61df8 00007fffe6a61e10 00007fffe6a61d70: 00000000000000f1 000055aabe61ee8f 00007fffe6a61d80: <00007fffe6a61df8 000055aabe3396a7 <runtime.asmcgocall+167> 00007fffe6a61d90: 00007fffe6a61dd0 000055aabe30fbb3 <runtime.malg+51> 00007fffe6a61da0: 000055aabe733f20 000000c000000900 00007fffe6a61db0: 0000000000000400 00007fffe6a61dd8 00007fffe6a61dc0: 0000000000000000 0000e3408a7f87cc 00007fffe6a61dd0: 00007fffe6a61e10 000055aabe30b526 <runtime.newm1+166> 00007fffe6a61de0: 000055aabe61ee80 00007fffe6a61df8 00007fffe6a61df0: 000055aabe30dbf3 <runtime.schedule+403> 000000c000000900 00007fffe6a61e00: 000000c000038488 000055aabe30a140 <runtime.mstart+0> 00007fffe6a61e10: 00007fffe6a61e48 000055aabe30b3dd <runtime.newm+157> 00007fffe6a61e20: 000000c000038400 000055aabe736430 00007fffe6a61e30: ffffffffffffffff 000000c000038400 00007fffe6a61e40: 000000c000038400 00007fffe6a61e70 00007fffe6a61e50: 000055aabe332345 <runtime.main.func1+69> 000055aabe736430 00007fffe6a61e60: 0000000000000000 ffffffffffffffff 00007fffe6a61e70: 000000c0000347d0 000055aabe337d23 <runtime.systemstack+99>

goroutine 1 [running]: runtime.systemstack_switch() runtime/asm_amd64.s:330 fp=0xc000034788 sp=0xc000034780 pc=0x55aabe337ca0 runtime.main() runtime/proc.go:134 +0x74 fp=0xc0000347e0 sp=0xc000034788 pc=0x55aabe307534 runtime.goexit() runtime/asm_amd64.s:1374 +0x1 fp=0xc0000347e8 sp=0xc0000347e0 pc=0x55aabe339a61

rax 0x55aac04e4310 rbx 0x7fffe6a61df8 rcx 0x55aac04e4320 rdx 0x21 rdi 0x55aac04e4310 rsi 0x18 rbp 0x7fffe6a61e10 rsp 0x7fffe6a61d80 r8 0x55aac04e4310 r9 0x7f863cf40a60 r10 0x2 r11 0x20 r12 0xf1 r13 0x0 r14 0x55aabe6891d4 r15 0x0 rip 0x55aabe61ee94 rflags 0x10202 cs 0x33 fs 0x0 gs 0x0

cmonty14 commented on 2020-12-03 20:34 (UTC) (edited on 2020-12-03 20:39 (UTC) by cmonty14)

I get error in build:

cmd.go:4:2: read /usr/lib/go/src/bufio/bufio.go: unexpected NUL in input ../gopath/pkg/mod/github.com/leonelquinteros/gotext@v1.4.0/locale.go:9:2: read /usr/lib/go/src/bytes/boundary_test.go: unexpected NUL in input ../gopath/pkg/mod/gopkg.in/yaml.v3@v3.0.0-20200615113413-eeeca48fe776/decode.go:19:2: read /usr/lib/go/src/encoding/encoding.go: unexpected NUL in input ../gopath/pkg/mod/gopkg.in/yaml.v3@v3.0.0-20200615113413-eeeca48fe776/decode.go:20:2: read /usr/lib/go/src/encoding/base64/base64.go: unexpected NUL in input ../gopath/pkg/mod/github.com/leonelquinteros/gotext@v1.4.0/mo.go:11:2: read /usr/lib/go/src/encoding/binary/binary.go: unexpected NUL in input ../gopath/pkg/mod/github.com/leonelquinteros/gotext@v1.4.0/gotext.go:26:2: read /usr/lib/go/src/encoding/gob/codec_test.go: unexpected NUL in input ../gopath/pkg/mod/github.com/davecgh/go-spew@v1.1.1/spew/dump.go:21:2: read /usr/lib/go/src/encoding/hex/example_test.go: unexpected NUL in input ../gopath/pkg/mod/github.com/stretchr/testify@v1.6.1/assert/assertions.go:6:2: read /usr/lib/go/src/encoding/json/bench_test.go: unexpected NUL in input pkg/news/news.go:5:2: read /usr/lib/go/src/encoding/xml/atom_test.go: unexpected NUL in input install.go:4:2: read /usr/lib/go/src/errors/errors.go: unexpected NUL in input clean.go:4:2: read /usr/lib/go/src/fmt/doc.go: unexpected NUL in input pkg/news/news.go:7:2: read /usr/lib/go/src/html/entity.go: unexpected NUL in input ../gopath/pkg/mod/github.com/!jguer/go-alpm/v2@v2.0.1/db.go:17:2: read /usr/lib/go/src/io/example_test.go: unexpected NUL in input ../gopath/pkg/mod/github.com/leonelquinteros/gotext@v1.4.0/mo.go:13:2: read /usr/lib/go/src/io/ioutil/example_test.go: unexpected NUL in input ../gopath/pkg/mod/gopkg.in/yaml.v3@v3.0.0-20200615113413-eeeca48fe776/decode.go:23:2: read /usr/lib/go/src/math/abs.go: unexpected NUL in input ../gopath/pkg/mod/golang.org/x/sys@v0.0.0-20200930185726-fdedc70b468f/unix/affinity_linux.go:10:2: read /usr/lib/go/src/math/bits/bits.go: unexpected NUL in input ../gopath/pkg/mod/github.com/stretchr/testify@v1.6.1/assert/assertion_format.go:9:2: read /usr/lib/go/src/net/http/alpn_test.go: unexpected NUL in input ../gopath/pkg/mod/github.com/stretchr/testify@v1.6.1/assert/http_assertions.go:6:2: read /usr/lib/go/src/net/http/httptest/example_test.go: unexpected NUL in input ../gopath/pkg/mod/github.com/leonelquinteros/gotext@v1.4.0/mo.go:14:2: read /usr/lib/go/src/net/textproto/header.go: unexpected NUL in input ../gopath/pkg/mod/github.com/stretchr/testify@v1.6.1/assert/assertion_format.go:10:2: read /usr/lib/go/src/net/url/example_test.go: unexpected NUL in input ../gopath/pkg/mod/github.com/leonelquinteros/gotext@v1.4.0/locale.go:11:2: read /usr/lib/go/src/os/dir.go: unexpected NUL in input pkg/settings/exe/exec.go:7:2: read /usr/lib/go/src/os/exec/bench_test.go: unexpected NUL in input ../gopath/pkg/mod/github.com/leonelquinteros/gotext@v1.4.0/locale.go:12:2: read /usr/lib/go/src/path/example_test.go: unexpected NUL in input pkg/completion/completion.go:11:2: read /usr/lib/go/src/path/filepath/example_test.go: unexpected NUL in input ../gopath/pkg/mod/github.com/!jguer/go-alpm/v2@v2.0.1/types.go:16:2: read /usr/lib/go/src/reflect/all_test.go: unexpected NUL in input ../gopath/pkg/mod/github.com/leonelquinteros/gotext@v1.4.0/plurals/compiler.go:14:2: read /usr/lib/go/src/regexp/all_test.go: unexpected NUL in input ../gopath/pkg/mod/github.com/stretchr/testify@v1.6.1/assert/assertions.go:13:2: read /usr/lib/go/src/runtime/alg.go: unexpected NUL in input package github.com/Jguer/yay/v10 imports github.com/Jguer/go-alpm/v2: read /usr/lib/go/src/runtime/cgo/asm_amd64.s: unexpected NUL in input ../gopath/pkg/mod/github.com/stretchr/testify@v1.6.1/assert/assertions.go:14:2: read /usr/lib/go/src/runtime/debug/debug.s: unexpected NUL in input ../gopath/pkg/mod/github.com/davecgh/go-spew@v1.1.1/spew/common.go:24:2: read /usr/lib/go/src/sort/example_interface_test.go: unexpected NUL in input pkg/intrange/intrange.go:4:2: read /usr/lib/go/src/strconv/atob.go: unexpected NUL in input pkg/intrange/intrange.go:5:2: read /usr/lib/go/src/strings/builder.go: unexpected NUL in input ../gopath/pkg/mod/github.com/leonelquinteros/gotext@v1.4.0/gotext.go:27:2: read /usr/lib/go/src/sync/cond.go: unexpected NUL in input package github.com/Jguer/yay/v10 imports github.com/Jguer/go-alpm/v2: read /usr/lib/go/src/syscall/asm9_unix1_amd64.s: unexpected NUL in input pkg/text/test_text.go:4:2: read /usr/lib/go/src/testing/allocs.go: unexpected NUL in input ../gopath/pkg/mod/github.com/!jguer/go-alpm/v2@v2.0.1/interfaces.go:4:2: read /usr/lib/go/src/time/embed.go: unexpected NUL in input pkg/intrange/intrange.go:6:2: read /usr/lib/go/src/unicode/casetables.go: unexpected NUL in input ../gopath/pkg/mod/gopkg.in/yaml.v3@v3.0.0-20200615113413-eeeca48fe776/encode.go:28:2: read /usr/lib/go/src/unicode/utf8/example_test.go: unexpected NUL in input ../gopath/pkg/mod/github.com/!jguer/go-alpm/v2@v2.0.1/alpm.go:13:8: read /usr/lib/go/src/unsafe/unsafe.go: unexpected NUL in input make: *** [Makefile:111: yay] Fehler 1 ==> FEHLER: Ein Fehler geschah in build(). Breche ab... error making: yay

I have installed latest go version: go 2:1.15.5-2

yochananmarqos commented on 2020-11-17 00:00 (UTC)

@hellochronix: It was an issue with Go that's fixed now. See Issue 1422.

heliochronix commented on 2020-11-13 18:29 (UTC)

Hello,

I seem to be encountering a build error with go-2:1.15.5-1 today. The error looks to be related to invalid linker flags, as shown here:

go build runtime/cgo: invalid flag in go:cgo_ldflag: -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now

kordru commented on 2020-11-06 21:37 (UTC)

i'm trying to install yay git and i believe a change i made a while ago when installing arch may have messed with makepkg. here's the debug:

==> Making package: yay 10.0.4-1 (Tue 03 Nov 2020 09:32:13 PM GMT) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found yay-10.0.4.tar.gz ==> Validating source files with sha256sums... yay-10.0.4.tar.gz ... Passed ==> Extracting sources... -> Extracting yay-10.0.4.tar.gz with bsdtar ==> Removing existing $pkgdir/ directory... ==> Starting build()... go build -v -trimpath -mod=readonly -modcacherw -ldflags '-s -w -extldflags "-Wl,-O1,- -sort-common,--as-needed,-z,relro,-z,now" -X "main.yayVersion=10.0.4" -X "main.localeP ath=/usr/share/locale/"' -buildmode=pie -o yay runtime/cgo

runtime/cgo

cc1: error: bad value ('native=generic') for '-march=' switch cc1: note: valid arguments to '-march=' switch are: nocona core2 nehalem corei7 westme re sandybridge corei7-avx ivybridge core-avx-i haswell core-avx2 broadwell skylake sky lake-avx512 cannonlake icelake-client icelake-server cascadelake tigerlake cooperlake bonnell atom silvermont slm goldmont goldmont-plus tremont knl knm x86-64 eden-x2 nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 znver 1 znver2 btver1 btver2 native make: *** [Makefile:127: yay] Error 2 ==> ERROR: A failure occurred in build(). Aborting... please help!

morgenstern commented on 2020-10-25 20:16 (UTC)

@Linuxious remove your out-of-date mark - fakeroot is in the base-devel group, which is a prerequisite for building AUR packages. Please familiarise yourself with the AUR building process.

sl13kp commented on 2020-10-24 13:09 (UTC)

This version has become very slow probably due to bugs

radio_rogal commented on 2020-10-22 06:31 (UTC) (edited on 2020-10-22 06:31 (UTC) by radio_rogal)

What is happend with GPG keys?

spotify: gpg: keyserver receive failed: General error\n problem importing keys

caddy2: gpg: keyserver receive failed: General error\n problem importing keys

yochananmarqos commented on 2020-08-24 21:41 (UTC)

@duckdalbe: What are you talking about? Of course gcc is in the base-devel group.

duckdalbe commented on 2020-08-24 21:09 (UTC)

gcc is a makedepends, should be added (and is not included in base-devel).

yochananmarqos commented on 2020-08-22 02:17 (UTC)

@darnir: -flto is not used in the default /etc/makepkg.conf, no changes are necessary except on your end, apparently.

whynothugo commented on 2020-08-21 22:17 (UTC)

@darnir See the pinned comment.

darnir commented on 2020-08-21 22:12 (UTC)

Just in case it helps anyone, the following diff fixed the build for me:

diff --git i/PKGBUILD w/PKGBUILD
index 8325d60..7a9e36b 100644
--- i/PKGBUILD
+++ w/PKGBUILD
@@ -20,8 +20,8 @@ sha256sums=('c0fb3df21a12d87c050317f68cc410b39d40f4af77192688956db67dc036a674')
 build() {
   export GOPATH="$srcdir"/gopath
   export CGO_CPPFLAGS="${CPPFLAGS}"
-  export CGO_CFLAGS="${CFLAGS}"
-  export CGO_CXXFLAGS="${CXXFLAGS}"
+  export CGO_CFLAGS="$(echo "${CFLAGS}" | sed 's/-flto//g')"
+  export CGO_CXXFLAGS="$(echo "${CXXFLAGS}"| sed 's/-flto//g')"
   export CGO_LDFLAGS="${LDFLAGS}"

   cd "$srcdir/$pkgname-$pkgver"

darnir commented on 2020-08-21 22:07 (UTC)

I have been unable to build this package for a few months now. Everytime I try to build I end up with a log similar to: https://pastebin.com/A3KRz8vJ

On digging deeper, this seems to come from the fact that my makepkg.conf contains `CFLAGS="... -flto ...". Apparently, turning on LTO in the C compiler, breaks the build.

If this is the case, the PKGBUILD should probably account for such scenarios

yochananmarqos commented on 2020-07-20 23:16 (UTC) (edited on 2020-07-20 23:16 (UTC) by yochananmarqos)

@masterberg: You should already have the base-devel group installed. Those packages are not required to be in makedepends() as they're assumed to be installed. See here and here.

masterberg commented on 2020-07-20 22:07 (UTC)

Add make package as a requirement as it's a build dependency.

Xavion commented on 2020-06-26 21:04 (UTC) (edited on 2020-06-30 00:11 (UTC) by Xavion)

I can't build v10.0.1-1 for some reason. See the build/error output here: https://pastebin.com/pk9dEAES

The same thing happens in a clean chroot. What can I do to overcome this problem?

Update: I've switched to the "yay-bin" package; that will do for now.

yochananmarqos commented on 2020-06-19 14:58 (UTC)

@Arashk @Slenderchat: Try my PKGBUILD with the export bits removed.

Slenderchat commented on 2020-06-19 14:20 (UTC) (edited on 2020-06-19 14:25 (UTC) by Slenderchat)

I am getting same issue as @Arashk.

Update: Works using VPN. For me may be related with US and EU sanctions over Crimea.

Arashk commented on 2020-06-18 17:11 (UTC)

I get an error while trying to build the package:

==> Making package: yay 10.0.1-1 (Thu 18 Jun 2020 09:33:21 PM +0430) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found yay-10.0.1.tar.gz ==> Validating source files with sha256sums... yay-10.0.1.tar.gz ... Passed ==> Extracting sources... -> Extracting yay-10.0.1.tar.gz with bsdtar ==> Removing existing $pkgdir/ directory... ==> Starting build()... go build -v -trimpath -mod=readonly -modcacherw -ldflags '-s -w -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.yayVersion=10.0.1" -X "main.localePath=/usr/share/locale/"' -buildmode=pie -o yay go: github.com/Jguer/go-alpm@v0.0.0-20200405152916-a3feea4322e9: Get "https://gocenter.io/github.com/%21jguer/go-alpm/@v/v0.0.0-20200405152916-a3feea4322e9.mod": dial tcp 35.230.74.213:443: i/o timeout make: *** [Makefile:134: yay] Error 1 ==> ERROR: A failure occurred in build(). Aborting...

MiniKoala commented on 2020-06-15 15:48 (UTC)

@RubenKelevra @pipep

Thank you! Much appreciated!!

kseistrup commented on 2020-06-14 16:16 (UTC)

@jguer I did read the pinned comment before I submitted my comment here, but just like it is inconvenient for you to receive comments here, it was inconvenient for me to submit at issue at the “upstream URL”, so I reckoned it was better to submit it here that to not submit it at all. That was the good intention.

@yochananmarqos Thanks for submitting the issue on Microsoft Github!

yochananmarqos commented on 2020-06-14 14:53 (UTC)

@kseistrup: I submitted an issue on GitHub.

RubenKelevra commented on 2020-06-14 14:22 (UTC)

@kseistrup please read the pinned comment and report issues with this package via GitHub.

kseistrup commented on 2020-06-14 12:42 (UTC)

This package no longer (at least from 10.0.0, probably earlier) builds a PIE executable.

Please see https://wiki.archlinux.org/index.php/Go_package_guidelines

pipep commented on 2020-06-14 04:11 (UTC)

@MiniKoala: Just type "yay" as a normal user. Yay will ask for the sudo password, then update all repo packages and all AUR packages, including itself.

RubenKelevra commented on 2020-06-14 04:06 (UTC)

@MiniKoala

use your regular user and give sudo permissions as necessary.

yay will run as user and only use root permissions for installation.

MiniKoala commented on 2020-06-13 23:40 (UTC)

Hello, I have a question. I'm new to Arch, I'm from Slackware ^^ this is the first update of an AUR package that I have to execute, I would like to know how should I do it? I read that it is not recommended to use YAY with root, so how to apply updates with yay and what permissions do I have to grant to my user to perform them? Thank you!

RubenKelevra commented on 2020-05-30 15:33 (UTC)

@gui_user yes it does. It's just a wrapper for the usual tooling you would use to build packages.

If you for example change the compression in makepkg.conf and you build a package with yay, it will change the compression for them.

gui_user commented on 2020-05-30 15:15 (UTC)

I was wondering, does yay respect the settings in /etc/makepkg.conf?

masterkorp commented on 2020-05-21 13:44 (UTC)

Hello, I cannot commpile:

==> Starting build()... go build -v -mod=mod -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.7"' -modcacherw -trimpath -o yay bytes strings crypto/cipher

bytes

/usr/lib/go/src/bytes/bytes_decl.go:10:6: IndexByte redeclared in this block previous declaration at /usr/lib/go/src/bytes/bytes.go:90:34 /usr/lib/go/src/bytes/bytes_decl.go:17:6: Equal redeclared in this block previous declaration at /usr/lib/go/src/bytes/bytes.go:18:25 /usr/lib/go/src/bytes/bytes_decl.go:24:6: Compare redeclared in this block previous declaration at /usr/lib/go/src/bytes/bytes.go:26:27 crypto/rc4

strings

/usr/lib/go/src/strings/strings_decl.go:8:6: IndexByte redeclared in this block previous declaration at /usr/lib/go/src/strings/strings.go:150:34 /usr/lib/go/src/strings/strings_decl.go:8:6: missing function body

crypto/cipher

/usr/lib/go/src/crypto/cipher/xor_amd64.go:9:6: xorBytes redeclared in this block previous declaration at /usr/lib/go/src/crypto/cipher/xor.go:58:33 /usr/lib/go/src/crypto/cipher/xor_amd64.go:22:6: xorWords redeclared in this block previous declaration at /usr/lib/go/src/crypto/cipher/xor.go:83:27

crypto/rc4

/usr/lib/go/src/crypto/rc4/rc4_asm.go:15:18: (Cipher).XORKeyStream redeclared in this block previous declaration at /usr/lib/go/src/crypto/rc4/rc4.go:61:6 make: ** [Makefile:50: yay] Error 2

r4start commented on 2020-05-04 11:44 (UTC)

Hi, I am getting the following build error: go build -v -mod=mod -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.7"' -modcacherw -trimpath -o yay flag provided but not defined: -modcacherw

Had the same issue. I had to build yay manually. Changing -modcacherw to -mod=readonly helped.

MikeD commented on 2020-05-01 21:07 (UTC)

Hi, I am getting the following build error: go build -v -mod=mod -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.7"' -modcacherw -trimpath -o yay flag provided but not defined: -modcacherw

sphere101 commented on 2020-04-22 14:12 (UTC)

Having these issues when building latest update.. Any thoughts?

go build -v -mod=mod -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.6"' -modcacherw -gcflags all=-trimpath=/home/andy/.cache/yay/yay/src/yay-9.4.6 -asmflags all=-trimpath=/home/andy/.cache/yay/yay/src/yay-9.4.6 -o yay flag provided but not defined: -mod usage: build [-o output] [-i] [build flags] [packages] Run 'go help build' for details. make: *** [Makefile:49: yay] Error 2 ==> ERROR: A failure occurred in build(). Aborting... Error making: yay

RubenKelevra commented on 2020-04-18 08:17 (UTC)

@bkb you can select the sudo-loop functionality to let yay handle this situation more gracefully:

yay -Y --sudo-loop --save

See this comment, for the reasoning behind that:

https://github.com/Jguer/yay/issues/1221#issuecomment-606465266

whynothugo commented on 2020-04-17 10:06 (UTC)

The build process runs in the same terminal, so the sudo ticket is valid. This allows scripts to potentially sudo, which is something you don't want when building.

Also, the ticket might expire by the time building is done.

uffe commented on 2020-04-17 08:22 (UTC)

@brb by asking for sudo password early - won't you risk that the "sudo"privs have timed out if the update takes a long time to process (download etc) ?

bkb commented on 2020-04-17 07:40 (UTC) (edited on 2020-04-17 07:44 (UTC) by bkb)

yay asks for root rights way too late

Sometimes you run a big update and go take your coffee, yay will ask nothing and make his compilations... And when you're far away from keyboard he will launch pacman at the very end who asks fur sudo rights (so your passsword) and that expires fast. So you return and nothing has been done, you have to relaunch and stay by the computer watching for the exact moment the computer will ask for the pswd. For example it's particularly annoying with ffmpeg-git who is very slow to compile and that if you don't give the passsword, you have to recompile the whole thing

Nevermind, yay should ask the password at the very beginning if he know he will need rights at some point

Link to upstream: https://github.com/Jguer/yay/issues/1244

RubenKelevra commented on 2020-04-12 14:27 (UTC) (edited on 2020-04-12 14:32 (UTC) by RubenKelevra)

Can you remove the sudo dependency, and make it optional, please?

I like to use yay just with opendoas, but this package keeps pulling sudo as dependency, while it's not necessary at all.

mr.benedikt commented on 2020-03-22 23:40 (UTC)

Does not build on WSL in Windows if the path contains spaces. The $PWD is then split into multiple strings.

wangrongda commented on 2020-03-09 01:58 (UTC)

detecting dependences incorrectly when setting an alternate installation root with -r

Falkenber9 commented on 2020-03-08 15:10 (UTC)

@jachymb: I had the same issue. I replaced gcc-go-9.2.1+20200130-2 by installing go (go-2:1.14-1) from the community repo. Afterwards, yay-package builds like a charm.

jachymb commented on 2020-03-07 08:40 (UTC)

Last version build crashed with:

go build -v -mod=mod -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.6"' -modcacherw -gcflags all=-trimpath=/home/jachym/.cache/yay/yay/src/yay-9.4.6 -asmflags all=-trimpath=/home/jachym/.cache/yay/yay/src/yay-9.4.6 -o yay

flag provided but not defined: -modcacherw

usage: go build [-o output] [-i] [build flags] [packages]

Run 'go help build' for details.

make: *** [Makefile:49: yay] Error 2

==> ERROR: A failure occurred in build().

Aborting...

slash170 commented on 2020-03-07 07:08 (UTC) (edited on 2020-03-07 07:08 (UTC) by slash170)

I have encounted same issue.I guess that cause of issue is version of Go at local environment.

I have succeeded to build yay with Go 1.14.

Go 1.14 was released last month and new option(modcacherw) was added for go build command.Please check URL bellow.

I think that yay needs Go1.14 for go build task. Thank you.

jose1711 commented on 2020-03-05 18:36 (UTC)

@menta thank you for the hint, worked for me!

menta commented on 2020-03-03 14:49 (UTC)

Specifying -mod=readonly instead of -modcacherw as the first parameter of EXTRA_GOFLAGS has solved the "flag provided but not defined: -modcacherw" error for me.

Ergus commented on 2020-03-02 12:43 (UTC)

Same problem here!!

go build -v -mod=mod -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.6"' -modcacherw -gcflags all=-trimpath=/tmp/aurman/yay/src/yay-9.4.6 -asmflags all=-trimpath=/tmp/aurman/yay/src/yay-9.4.6 -o yay
flag provided but not defined: -modcacherw
usage: go build [-o output] [-i] [build flags] [packages]
Run 'go help build' for details.
make: *** [Makefile:49: yay] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
2020-03-02 13:39:01,941 - wrappers - makepkg - ERROR - makepkg query ['makepkg', '-cf', '--noconfirm'] failed in directory /tmp/aurman/yay

mokkurkalve commented on 2020-03-01 23:09 (UTC)

Yes, with gcc-go 9.2.1+20200130-2 I get:

go build -v -mod=mod -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.6"' -modcacherw -gcflags all=-trimpath=/tmp/makepkg/yay/src/yay-9.4.6 -asmflags all=-trimpath=/tmp/makepkg/yay/src/yay-9.4.6 -o yay
flag provided but not defined: -modcacherw
usage: go build [-o output] [-i] [build flags] [packages]
Run 'go help build' for details.
make: *** [Makefile:49: yay] Error 2

MagicAndWires commented on 2020-03-01 02:19 (UTC)

Cheers! A final small change would be to change the trimpath flags from $PWD to $srcdir, in order to clean up leftover references to $GOPATH from the binary.

chungy commented on 2020-03-01 00:35 (UTC)

Fails to build with gccgo:

==> Starting build()...
go build -v -mod=mod -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.6"' -modcacherw -gcflags all=-trimpath=/home/chungy/.cache/yay/yay/src/yay-9.4.6 -asmflags all=-trimpath=/home/chungy/.cache/yay/yay/src/yay-9.4.6 -o yay
flag provided but not defined: -modcacherw
usage: go build [-o output] [-i] [build flags] [packages]
Run 'go help build' for details.
make: *** [Makefile:49: yay] Error 2

MagicAndWires commented on 2020-02-29 19:34 (UTC)

Currently go dependencies are currently still stored in the default GOPATH, (usually a go directory in $HOME).

Please provide a custom $GOPATH variable to avoid contaminating home folders and building outside of srcdir.

mvertes commented on 2020-02-28 16:59 (UTC)

Please add 'arm' to supported arch targets. Tested ok on a Tonido2.

surf.bluecrab commented on 2020-02-28 04:06 (UTC) (edited on 2020-02-28 04:22 (UTC) by surf.bluecrab)

Problem with go too:


==> Making package: yay 9.4.5-1 (Fri 28 Feb 2020 12:02:50 AM)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found yay-9.4.5.tar.gz
==> Validating source files with sha1sums...
    yay-9.4.5.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting yay-9.4.5.tar.gz with bsdtar
==> Sources are ready.
==> Making package: yay 9.4.5-1 (Fri 28 Feb 2020 12:02:56 AM)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting build()...
go build -v -mod=vendor -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.5"' -gcflags all=-trimpath=/tmp/makepkg/yay/src/yay-9.4.5 -asmflags all=-trimpath=/tmp/makepkg/yay/src/yay-9.4.5 -o yay
/usr/lib/go/src/internal/reflectlite/value.go:8:2: read /usr/lib/go/src/runtime/mgclarge.go: unexpected NUL in input
/usr/lib/go/src/internal/syscall/unix/at.go:10:2: read /usr/lib/go/src/syscall/tables_nacljs.go: unexpected NUL in input
/usr/lib/go/src/crypto/tls/key_schedule.go:16:2: read /usr/lib/go/src/vendor/golang.org/x/crypto/curve25519/ladderstep_amd64.s: unexpected NUL in input
make: *** [Makefile:47: yay] Error 1
==> ERROR: A failure occurred in build().
    Aborting...
Error making: yay

Update:

I uninstalled go then manualy removed * from /usr/lib/go then resintalled go and yay. Seems to have fixed the problem.

jguer commented on 2020-02-27 17:07 (UTC)

probably because of the new go version, I'll take a look at it

leanhtai01 commented on 2020-02-27 16:12 (UTC)

Having issues installing yay:


==> Making package: yay 9.4.4-1 (Thu 27 Feb 2020 11:10:31 PM +07)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found yay-9.4.4.tar.gz
==> Validating source files with sha1sums...
    yay-9.4.4.tar.gz ... Passed
==> Extracting sources...
  -> Extracting yay-9.4.4.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
go build -v -mod=vendor -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.4"' -gcflags all=-trimpath=/home/leanhtai01/Downloads/yay/src/yay-9.4.4 -asmflags all=-trimpath=/home/leanhtai01/Downloads/yay/src/yay-9.4.4 -o yay
go: inconsistent vendoring in /home/leanhtai01/Downloads/yay/src/yay-9.4.4:
    github.com/Jguer/go-alpm@v0.0.0-20191122171459-5cffc6e8fc69: is explicitly required in go.mod, but vendor/modules.txt indicates github.com/Jguer/go-alpm@v0.0.0-20191021114528-e11e8a60f385
    github.com/mikkeloscar/aur@v0.0.0-20191216074712-ebecb34b95b4: is explicitly required in go.mod, but vendor/modules.txt indicates github.com/mikkeloscar/aur@v0.0.0-20190912174111-183f80a38525

run 'go mod vendor' to sync, or use -mod=mod or -mod=readonly to ignore the vendor directory make: *** [Makefile:47: yay] Error 1 ==> ERROR: A failure occurred in build(). Aborting...

aniketd commented on 2020-02-24 07:29 (UTC) (edited on 2020-02-24 07:31 (UTC) by aniketd)

nerd-fonts-fantasque-sans-mono package and other packages in the nerd family including fira etc, are no longer verifying correctly.

❯ yay -S nerd-fonts-fantasque-sans-mono
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur: 1]  nerd-fonts-fantasque-sans-mono-2.1.0-1

  1 nerd-fonts-fantasque-sans-mono           (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>
:: PKGBUILD up to date, Skipping (1/1): nerd-fonts-fantasque-sans-mono
  1 nerd-fonts-fantasque-sans-mono           (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>
:: Parsing SRCINFO (1/1): nerd-fonts-fantasque-sans-mono

==> Making package: nerd-fonts-fantasque-sans-mono 2.1.0-1 (Sun 23 Feb 2020 08:27:56 PM IST)
==> Retrieving sources...
  -> Found FantasqueSansMono.zip
  -> Found LICENSE
==> Validating source files with sha1sums...
    FantasqueSansMono.zip ... FAILED
    LICENSE ... Passed
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: nerd-fonts-fantasque-sans-mono

The same package is installed without problems using the aura package manager

❯ sudo aura -A nerd-fonts-fantasque-sans-mono
[sudo] password for aniketd:
aura >>= Determining dependencies...
aura >>= AUR Packages:
nerd-fonts-fantasque-sans-mono
aura >>= Continue? [Y/n]
loading packages...
warning: nerd-fonts-fantasque-sans-mono-2.1.0-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) nerd-fonts-fantasque-sans-mono-2.1.0-1

Total Installed Size:  7.55 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                                                                                                                  [########################################################################################] 100%
(1/1) checking package integrity                                                                                                                [########################################################################################] 100%
(1/1) loading package files                                                                                                                     [########################################################################################] 100%
(1/1) checking for file conflicts                                                                                                               [########################################################################################] 100%
(1/1) checking available disk space                                                                                                             [########################################################################################] 100%
:: Processing package changes...
(1/1) reinstalling nerd-fonts-fantasque-sans-mono                                                                                               [########################################################################################] 100%
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating fontconfig cache...
(3/4) Updating 32-bit fontconfig cache...
(4/4) Updating X fontdir indices...

normalname012 commented on 2020-02-14 15:18 (UTC)

I am not able to upgrade development packages, shows cannot rm permission denied when trying to remove cache of it

editicalu commented on 2020-01-22 15:03 (UTC)

@hugo you need to install base-devel. This is assumed hence make is not a dependency.

hugo commented on 2020-01-22 14:59 (UTC)

"make" is missing on makedepends, got an error on a fresh install.

MindfulConsumer commented on 2020-01-20 12:26 (UTC) (edited on 2020-01-20 12:29 (UTC) by MindfulConsumer)

On-topic: I've noticed with other packages yay is importing a single GPG key just fine. Could the problem be multiple GPG keys?

Off-topic: @fightcookie; maybe walk the talk? How is you bulky comment not off-topic and without new information? The way I see it is this comment section is the place where end users help each other out to get a particular software working. I can't always tell the difference between a packaging or a software bug.

xuiqzy commented on 2020-01-20 08:22 (UTC)

@MindfulConsumer I am subscribed to comments to this aur package, so off-topic comments are kind of distracting and wasting my time (I'm surely not the only one subscribed). Also, these kinds of comments led @jguer to disable comments to this package (according to their pinned message), which is unfortunate I think for support of the package since they are the maintainer currently! It is totally ok of you to boycott GitHub, but please consider only posting packaging related bugs here, to keep the comments readable by everyone interested without being overwhelmed by off topic things :)

MindfulConsumer commented on 2020-01-19 13:27 (UTC)

@swm and @jguer: sadly I had to conclude github should be on my boycott list, I refuse to create an account there. I can manually import the gpg keys without problems with "gpg --recv-keys <key>" and continue installing.

swm commented on 2020-01-19 08:30 (UTC) (edited on 2020-01-19 08:32 (UTC) by swm)

@iTanguy and @MindfulConsumer: Seeing jguer's pinned comment from 2019-04-16, you should probably go to the upstream issue tracker, see if the problem has already been reported there and do so if not.

@MindfulConsumer: yay uses sudo which may ask for your user password to execute actions as root (if not already done so in the last x minutes, depending on your sudo configuration). Otherwise it should not ask for passwords. The "permission denied" error you see is from gpg trying to get the keys from a server, which has nothing to do with your local user accounts. (I think yay's usage of gpg will also import the keys to your own gpg keyring, which does not belong to root and does not need sudo usage.) An issue with the same gpg error message has been reported upstream, which might help you solve your problem: https://github.com/Jguer/yay/issues/656

MindfulConsumer commented on 2020-01-18 23:59 (UTC) (edited on 2020-01-19 00:08 (UTC) by MindfulConsumer)

I'm pretty sure yay is supposed to ask me for a password here:

 :: Parsing SRCINFO (1/1): palemoon-bin

 ==> PGP keys need importing:
 -> 439F46F42C6AE3D23CF52E70865E6C87C65285EC, required by: palemoon-bin
-> 3DAD8CD107197488D2A2A0BD40481E7B8FCF9CEC, required by: palemoon-bin
==> Import? [Y/n] y
:: Importing keys with gpg......
gpg: keyserver receive failed: Permission denied
==> Error: Problem importing keys

iTanguy commented on 2020-01-18 13:29 (UTC)

License information should be more accurate. I am no packaging expert nor lawyer, just a user who cares about FOSS.

  1. GPL license version used is GLP v3.0, for License should be set to GPL3
  2. The "go-alpm" module is under MIT license, so it should be added to the "License" field (becoming "GPL3 MIT")
  3. the MIT license file should be added to /usr/share/licenses/yay/

sorenvonsarvort commented on 2020-01-15 10:50 (UTC) (edited on 2020-01-20 09:55 (UTC) by sorenvonsarvort)

EDITED: My apologies, I had installed custom patches for go, so they made the yay package unbuildable. I am also sorry for reporting the bug here, but not at the upstream! Have a nice day.

...

Hey, I would like to notify this package doesn't build on my workstation anymore! Does this issue apply to someone else's setup?

$ yay -Syu
...
==> Retrieving sources...
  -> Found yay-9.4.3.tar.gz
...
==> Starting build()...
go build -v -mod=vendor -ldflags '-s -w -linkmode external -extldflags "-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" -X "main.version=9.4.3"' -gcflags all=-trimpath=/home/FILTERED/.cache/yay/yay/src/yay-9.4.3 -asmflags all=-trimpath=/home/FILTERED/.cache/yay/yay/src/yay-9.4.3 -o yay
go: inconsistent vendoring in /home/FILTERED/.cache/yay/yay/src/yay-9.4.3:
    github.com/Jguer/go-alpm@v0.0.0-20191122171459-5cffc6e8fc69: is explicitly required in go.mod, but vendor/modules.txt indicates github.com/Jguer/go-alpm@v0.0.0-20191021114528-e11e8a60f385
    github.com/mikkeloscar/aur@v0.0.0-20191216074712-ebecb34b95b4: is explicitly required in go.mod, but vendor/modules.txt indicates github.com/mikkeloscar/aur@v0.0.0-20190912174111-183f80a38525

run 'go mod vendor' to sync, or use -mod=mod or -mod=readonly to ignore the vendor directory
make: *** [Makefile:47: yay] Error 1
==> ERROR: A failure occurred in build().
    Aborting...
Error making: yay

JM9 commented on 2020-01-14 21:12 (UTC)

@nsmcclellan thanks. To whoever marked as out of date, please leave a comment as to why you are marking something out of date. Thanks!

nsmcclellan commented on 2020-01-13 22:36 (UTC)

I didn't flag it, but it was likely flagged because it IS technically out of date: https://github.com/Jguer/yay/releases (just be patient - github release was yesterday; this will likely be resolved soon)

JM9 commented on 2020-01-13 18:27 (UTC)

Why is this flagged out of date?

f1she3 commented on 2019-11-30 22:54 (UTC)

@psltn : Yes that's right, I suggested it because I somehow didn't have the base-devel package installed on my raspberry pi, but I in fact only needed fakeroot to build yay, so adding it would save a few minutes ;)

As you wish

psltn commented on 2019-11-03 02:13 (UTC)

@f1she3: No need to. Read the "Note" here: https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

f1she3 commented on 2019-11-02 23:56 (UTC) (edited on 2019-11-03 00:00 (UTC) by f1she3)

Hi !

I think that fakeroot (https://www.archlinux.org/packages/core/x86_64/fakeroot/) should be added as a dependency, am I wrong ?

brando56894 commented on 2019-10-26 21:10 (UTC)

looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: installing pacman (5.2.0-2) breaks dependency 'pacman<=5.1.3' required by yay

jguer commented on 2019-10-25 10:48 (UTC)

@gdude2002 you sure your pacman cache was not symlinked? I have only seen this in those cases. The only other reason for that to happen is for pacman to be set as a dependency instead of an explicit, which yay does not do.

gdude2002 commented on 2019-10-25 10:43 (UTC)

@jguer Just to let you know that trying to do that (install yay-bin then update as normal with pacman) ended up actually removing pacman from my system for some reason - luckily the dependencies were still there so I could manually copy the files in from a manually downloaded copy from the package repos, and now everything is fine.

soloturn commented on 2019-10-24 23:07 (UTC) (edited on 2019-10-24 23:09 (UTC) by soloturn)

if one does not like binary packages, copied from https://www.reddit.com/r/archlinux/comments/dlpng7/cant_pacman_syu_because_of_yay/

yay -G yay #clones new yay from git
yay -R yay #removes old yay
sudo pacman -Syu
cd yay/
makepkg -si #install the yay you cloned

dgmulf commented on 2019-10-24 20:25 (UTC)

Is anyone else getting problems with the diff functionality in 9.4.2? When upgrading a package, the diff behaves as if every version is an initial commit, e.g.:

diff --git /home/dgmulf/build/aur/st/PKGBUILD /home/dgmulf/build/aur/st/PKGBUILD
new file mode 100644
index 0000000..7ad8f2e
--- /dev/null
+++ /home/dgmulf/build/aur/st/PKGBUILD
[...]

Jake commented on 2019-10-23 19:17 (UTC) (edited on 2019-10-23 19:19 (UTC) by Jake)

Is it really necessary to put the specific pacman version in the dependency list? It might be not totally clean, but can't you just expect that it is built with the current versions from the official repo? Then yay would as usual upgrade from the offical repos first, build the AUR stuff afterwards and everything would be fine.

Also if we are really strict, if yay-bin is compiled against v5.2 (libalpm.so.12) it will also not run with 5.1.x. So it should also depend on pacman>=5.2, or not? If you fix this that workaround would also not work.

wooptoo commented on 2019-10-23 17:16 (UTC)

@jguer Another method is to fetch the latest yay PKGBUILD yay -G yay, update pacman, then build the new yay with makepkg.

AlexWayfer commented on 2019-10-23 12:41 (UTC)

@jguer, thank you, sorry.

jguer commented on 2019-10-23 12:12 (UTC) (edited on 2019-10-23 12:12 (UTC) by jguer)

WARNING: PACKAGER should have the format 'Example Name <email@address.invalid>'

https://github.com/Jguer/yay/issues/1085

AlexWayfer commented on 2019-10-23 12:09 (UTC)

WARNING: PACKAGER should have the format 'Example Name <email@address.invalid>'

flower commented on 2019-10-23 10:36 (UTC) (edited on 2019-10-23 10:39 (UTC) by flower)

sudo pacman -R yay

sudo pacman -Syu

cd yay # your old yay dir... otherwise follow new install

git pull

makepkg -si

cd ..

yay -Syu

worked for me :)

jguer commented on 2019-10-23 08:36 (UTC) (edited on 2019-10-23 08:45 (UTC) by jguer)

Having issues upgrading yay and pacman at the same time? Here is the proposed workaround for now.

yay -S yay-bin
sudo pacman -Syu
yay -S yay

yay-bin is a binary ready package with yay already compiled against v5.2, it does not require go to build. https://github.com/Jguer/yay/issues/1084

WSDMatty commented on 2019-10-22 14:42 (UTC) (edited on 2019-10-22 14:47 (UTC) by WSDMatty)

For those on the testing branch needing to manually update yay for the newest pacman. Here's a PKGBUILD.

# Maintainer: Jguer <joaogg3@gmail.com>
pkgname=yay
pkgver=9.4.0
pkgrel=1
pkgdesc="Yet another yogurt. Pacman wrapper and AUR helper written in go."
arch=('i686' 'x86_64' 'armv7h' 'armv6h' 'aarch64')
url="https://github.com/Jguer/yay"
license=('GPL')
depends=(
  'pacman>=5.2.0'
  'sudo'
  'git'
)
makedepends=(
  'go'
)
source=("${pkgname}-${pkgver}.tar.gz::https://github.com/Jguer/yay/archive/v${pkgver}.tar.gz")
sha1sums=('9e62c6e3d0bae7b6687717b07e3455ac9aa451cd')

build() {
  cd "$srcdir/$pkgname-$pkgver"
  EXTRA_GOFLAGS="-gcflags all=-trimpath=${PWD} -asmflags all=-trimpath=${PWD}" \
    LDFLAGS="-linkmode external -extldflags \"${LDFLAGS}\"" \
    make VERSION=$pkgver DESTDIR="$pkgdir" build
}

package() {
  cd "$srcdir/$pkgname-$pkgver"
  make VERSION=$pkgver DESTDIR="$pkgdir" PREFIX=/usr install
}

gardotd426 commented on 2019-10-22 13:27 (UTC)

On the testing branch, the latest update of Pacman breaks yay (and pamac)

tthynnin commented on 2019-09-26 10:46 (UTC)

yay v9.3.1 - libalpm v11.0.3 ==> ERROR: PKGBUILD contains CRLF characters and cannot be sourced. for every package i try

commented on 2019-08-21 09:23 (UTC)

For FREE Skin Warts Solution - https://www.newsworldlab.com/how-can-apple-cider-vinegar-help-you-remove-warts/

FREE FREE GIFTS To WIN :- https://www.newsworldlab.com/

conan commented on 2019-07-01 14:09 (UTC)

yay 9.2.0-1, which I had installed, complains about libgo missing, though it doesn't appears as dependency here or in libgo page.

A full system upgrade doesn't solve the issue.

Downloading PKGBUILD for current version (9.2.1-1), building with makepkg and installing with pacman -U solves the issue, however there's no automatic upgrade path that works.

damachine commented on 2019-05-25 17:44 (UTC)

@Anty0 thanks your tip it works after reinstall

Anty0 commented on 2019-05-24 20:11 (UTC) (edited on 2019-05-24 20:12 (UTC) by Anty0)

@damachine Did you try to manually rebuild and reinstall yay package?

damachine commented on 2019-05-23 11:27 (UTC)

yay: error while loading shared libraries: libgo.so.13: cannot open shared object file: No such file or directory.

After install libtool 2.4.6+42+gb88cebd5-4 glibc 2.29-2 gcc 9.1.0-1 binutils 2.32-2 linux-api-headers 5.1-1

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.

Chrissss commented on 2019-04-16 13:35 (UTC)

Can someone delete the last two comments? Looks like spam...

johnnybash commented on 2019-02-20 05:58 (UTC)

@adomol yay -Sc deletes everything you wont need anymore.

adomol commented on 2019-02-18 19:10 (UTC)

Hello... what is the proper way to clear the Yay cache?

Thanks.

Morganamilo commented on 2019-01-13 18:40 (UTC)

My guess is on https://github.com/Jguer/yay/issues/812

yay --bottomup --save should correct it.

jguer commented on 2019-01-13 18:35 (UTC)

==> Packages to NOT upgrade: (eg: 1 2 3, 1-3, ^4 or repo name)

Don't see anything wrong there

Thermi commented on 2019-01-13 17:37 (UTC)

Hi, I think the numbers in the "Packages to upgrade" menu aren't right. See the following.

:: 2 Packages to upgrade.
2  aur/python-cli_helpers  1.0.2-1 -> 1.1.0-1
1  aur/qemu-user-static    3.1-2   -> 3.1.0-1
==> Packages to not upgrade: (eg: 1 2 3, 1-3, ^4 or repo name)
==> 1
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur: 1]  python-cli_helpers-1.1.0-1

  1 python-cli_helpers               (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 

Nyutag commented on 2019-01-05 17:00 (UTC)

@hringriin. I was having the same issue. Also freshly installed ArchLinux 32bit.

Solved by using another repo from https://git.archlinux32.org/archlinux32/packages/raw/branch/master/core/pacman-mirrorlist/mirrorlist and pacman -Syyu

I get the last go package and successfully install yay.

hringriin commented on 2019-01-03 23:03 (UTC) (edited on 2019-01-03 23:05 (UTC) by hringriin)

>$ makepkg
[...]
go build -v -ldflags '-s -w -X main.version=9.0.1' -o yay -mod=vendor
flag provided but not defined: -mod
make: *** [Makefile:51: build] Error 2

This is the output of makepkg on A freshly installed Arch Linux 32 bit.

I could see, that my version of the go package is 2:1.10.3-1.1 whereas the latest go version is 2:1.11.4-1, but, as of yet only for 64 bit architectures.

Is this due to my older version of go or am I missing something else?

Morganamilo commented on 2018-12-28 17:01 (UTC)

By default sudo will cache your password for 5 minutes.

WFV commented on 2018-12-28 16:26 (UTC)

Thanks for yay. Is it normal when running % yay -Sua for some packages to simply install but others ask for sudo password? (I've never used any wrappers for doing bulk aur package updates, nor system updates.)

schimicata commented on 2018-12-25 00:16 (UTC)

@twnaing I had the same error. I could fix it upgrading my installed package of "go".

eschwartz commented on 2018-12-24 18:44 (UTC)

@adizero you're not supposed to source this yourself. This installs a completion spec, but users who wish to use completions are supposed to install the bash-completion package as that both sets up the automatic lazy loading of completion specs, and contains the shared helper functions relied on by many command completions.

adizero commented on 2018-12-21 08:24 (UTC)

Shouldn't the bash-completion package be listed as an optional dependency? Without it an attempt to use the completion (after pressing <TAB>) fails. E.g.: $ source /usr/share/bash-completion/completions/yay $ yay bash: _get_comp_words_by_ref: command not found

twnaing commented on 2018-12-11 12:54 (UTC)

I am having the following error trying to update from version 8 to 9 using yay

==> Starting build()... go build -v -ldflags '-s -w -X main.version=9.0.1' -o yay -mod=vendor flag provided but not defined: -mod usage: build [-o output] [-i] [build flags] [packages] Run 'go help build' for details. make: *** [Makefile:51: build] Error 2 ==> ERROR: A failure occurred in build(). Aborting... Error making: yay

Morganamilo commented on 2018-12-08 21:22 (UTC)

@SirCmpwn Also are you building yay with makepkg or yay?

jguer commented on 2018-12-08 20:41 (UTC) (edited on 2018-12-08 20:41 (UTC) by jguer)

I cannot reproduce that, can you create an issue in the upstream URL? Something is turning off the GOCHACHE. I may have to revert the go modules patch

commented on 2018-12-08 20:16 (UTC)

==> Extracting sources... -> Extracting yay-9.0.1.tar.gz with bsdtar ==> Starting build()... go build -v -ldflags '-s -w -X main.version=9.0.1' -o yay -mod=vendor go: disabling cache (/root/.cache/go-build) due to initialization failure: mkdir /root/.cache: permission denied go: cannot use modules with build cache disabled make: *** [Makefile:51: build] Error 1 ==> ERROR: A failure occurred in build().

Despite appearances, I'm not running makepkg as root.

jguer commented on 2018-12-07 14:09 (UTC)

Issue should be fixed in yay 9.0.1. pkg-rel was not changed because of auto update script screwing up but go and go-pie users should now be able to compile using go mod and gcc-go users will default to the old method of symlinking gopath to vendor

jguer commented on 2018-12-07 12:39 (UTC) (edited on 2018-12-07 12:48 (UTC) by jguer)

You're right, it will also break gcc-go, I'm reverting this. EDIT: Actually I know the problem now, gcc-go does not have mod support. We don't offer support for gcc-go but I think this needs to be fixed for next version. I'll create an issue on the issue tracker.

egrupled commented on 2018-12-07 11:47 (UTC) (edited on 2018-12-07 11:51 (UTC) by egrupled)

@jguer specifying min go version breaks go-pie as dependency, please fix or revert this. Partial upgrades with ancient go version aren't supported anyway.

jguer commented on 2018-12-07 11:11 (UTC)

I didn't specify the minimum version for go but I will change it now. go -mod is only introduced in go1.11

mokkurkalve commented on 2018-12-07 10:40 (UTC)

Building 9.0.0-1 failes thus:

==> Starting build()... go build -mod=vendor -v -ldflags '-s -w -X main.version=9.0.0' -o yay flag provided but not defined: -mod usage: build [-o output] [-i] [build flags] [packages] Run 'go help build' for details. make: *** [Makefile:43: build] Error 2 ==> ERROR: A failure occurred in build(). Aborting... Error making: yay

mchoji commented on 2018-12-07 04:22 (UTC)

Thx! Running yay -Syu --requestsplitn 20 fixed the problem. Maybe this should be set as default?

Morganamilo commented on 2018-12-06 19:11 (UTC)

Actually requestsplitn just dictates how many packages to pack into a single requests.

GOAWAY means you've made too many requests in too short of a time. The AUR has blacklisted you for 24hrs.

This is usually the cause of running an helper in some sort of automated timer.

jguer commented on 2018-12-06 18:08 (UTC)

try running it as yay -Syu --requestsplitn 20 otherwise try deleting your ~/.config/yay/config.json

mchoji commented on 2018-12-06 17:25 (UTC)

I'm getting a GOAWAY http message every time I try a sysupgrade. Is it normal? The output is like that: https://pastebin.com/0TMF4NSv

commented on 2018-11-29 02:45 (UTC)

where is the config file for yay?

jguer commented on 2018-11-24 20:07 (UTC)

fakeroot is part of the base-devel group that is a requirement for makepkg therefore it is not necessary to add it as a dependency (I mean if you're using yay only for pacman because it's pretty I guess that's a too specific use case we've never taken into account). https://wiki.archlinux.org/index.php/PKGBUILD#makedepends

commented on 2018-11-24 16:09 (UTC)

fakeroot is a dependency aswell

bscubed commented on 2018-11-18 02:11 (UTC)

It's a shame someone missed the opportunity to name this AUR helper "ayy" instead. This is the best aur helper out there. Thanks for the package!

Alad commented on 2018-10-27 10:02 (UTC)

It's the nature of the beast. Pacman wrappers attract the kind of helpless users that can't work with basic tools shipped with the distribution.

johnnybash commented on 2018-10-08 15:53 (UTC)

During the installation phase there is no point in using an aur helper

ftfy ;)

lefsha commented on 2018-10-08 11:41 (UTC)

Surely it works if all deps packages are installed. It doesn't though on a clean system. Filed a bug report. It makes me mad, that yay deny to work under root. That is the only possibility on a new chrooted system. I have to make a new user and su to it just to be able use yay. At the same time pacman doesn't work under user and I have to switch back to root or use sudo. Being a root initially it is perverse to pretend to be another user and then call sudo. During the installation phase there is no point to be non root user. 100% of work requires root privileges. And again yaourt doesn't have such an issue. It just works. Good lesson - new is not always better than old.

jguer commented on 2018-10-08 11:04 (UTC)

I passed all of the initial phase of build and it works, please report this kind of issue in the upstream URL, also, we're very sorry to see you go, you will be missed.

lefsha commented on 2018-10-08 09:55 (UTC)

Unable to use YAY just to install a single package. Simple construction "yay -S ffmpeg-libfdk_aac" didn't work YAY reports problem each time at different place: "Inner conflicts found" My guess the problem is that single package libva provides libva.so, libva-x11.so and libva-drm.so at the same time. Yaourt doesn't have that issue and works perfect. I've droped yay from my system.

HighValueWarrior commented on 2018-08-25 05:54 (UTC)

Solid and Straight Forward. Thanks.

Morganamilo commented on 2018-08-01 12:26 (UTC)

For the bug, try clean building, if it persists open an issue.

For the second point, see the FAQ.

themoosemachine commented on 2018-08-01 11:39 (UTC)

Firstly, the following error pops up a lot when trying to upgrade certain AUR files: fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'</file></revision>

Google Chrome is one of the packages affected by this bug.

Secondly, the previous package was easier since all options were selected at the start. In the current version, we have to wait for all core, extra, community and multilib packages to update first, and then select the AUR packages. This is not a biggie, but just annoying; whereas earlier it was smoother and an overall nicer experience.

ilfabri commented on 2018-07-12 06:39 (UTC) (edited on 2018-07-12 07:14 (UTC) by ilfabri)

When performing 'yay -Syua', if there are aur updates, it performs only these ones skipping the standard repository updates. You need to run the command once more to complete the upgrade. Thank you for the awesome work, btw!

EDIT: I figured out that running 'yay' is enough

Morganamilo commented on 2018-07-05 20:37 (UTC)

It's part of the debug symbols the go compiler puts into the binary. If you manage to make Yay stack trace it will tell you which file the error occurred in. Using the pwd of where it was compiled.

grawlinson commented on 2018-07-05 20:33 (UTC)

Just got this warning when installing Yay.

==> WARNING: Package contains reference to $srcdir

It seems to be embedded in the yay binary.

$ grep -R "$(pwd)/src" pkg/ Binary file pkg/yay/usr/bin/yay matches

MinzordYT commented on 2018-07-01 19:33 (UTC)

thanks

arx commented on 2018-06-23 22:16 (UTC)

Yeah I found that, thanks :D

go get -u github.com/Jguer/yay

Morganamilo commented on 2018-06-23 22:15 (UTC)

The AUR repository just contains a pkgbuild. If you want to use go get you'll have to use the actual yay repo.

arx commented on 2018-06-23 22:13 (UTC)

Can someone make this installable w/ Go?

go get -u aur.archlinux.org/yay.git

Morganamilo commented on 2018-06-04 22:38 (UTC)

@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 (UTC)

I'm getting TLS handshake timeouts from time to time

jguer commented on 2018-06-01 09:04 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC) (edited on 2018-06-01 03:16 (UTC) by psi-jack)

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 (UTC)

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

jguer commented on 2018-04-29 11:17 (UTC)

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 (UTC)

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 (UTC)

True, I'll add it and increase the pkgrel

Morganamilo commented on 2018-04-26 20:24 (UTC)

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

grunch commented on 2018-04-24 14:51 (UTC)

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 (UTC)

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

egrupled commented on 2017-12-04 09:53 (UTC) (edited on 2017-12-05 10:55 (UTC) by egrupled)

Doesn't build after https://aur.archlinux.org/cgit/aur.git/commit/?h=yay&id=c36666539b51 and https://aur.archlinux.org/cgit/aur.git/commit/?h=yay&id=1cec81f1f8e5

completions.go:9:2: cannot find package "github.com/jguer/go-alpm" in any of:

/usr/lib/go/src/github.com/jguer/go-alpm (from $GOROOT)

/home/user/go/src/github.com/jguer/go-alpm (from $GOPATH)

dependencies.go:7:2: cannot find package "github.com/mikkeloscar/aur" in any of:

/usr/lib/go/src/github.com/mikkeloscar/aur (from $GOROOT)

/home/user/go/src/github.com/mikkeloscar/aur (from $GOPATH)

install.go:9:2: cannot find package "github.com/mikkeloscar/gopkgbuild" in any of:

/usr/lib/go/src/github.com/mikkeloscar/gopkgbuild (from $GOROOT)

/home/user/go/src/github.com/mikkeloscar/gopkgbuild (from $GOPATH)

==> ERROR: A failure occurred in build().

jguer commented on 2017-10-25 11:55 (UTC)

You're right, will remove it next minor release.

egrupled commented on 2017-10-21 14:04 (UTC)

GPL3 is license already included in https://www.archlinux.org/packages/core/any/licenses/ you don't have to install it separately for each package. Please remove it from PKGBUILD

jguer commented on 2017-04-25 15:43 (UTC)

yay doesn't use checksums since it compiles from a git source and it's building fine over here but I've regenerated the .SRCINFO to make sure there is no missing field.

klingt.net commented on 2017-04-25 08:10 (UTC) (edited on 2017-04-25 08:10 (UTC) by klingt.net)

Did you forgot to run `updpkgsums`? ``` ... :: Installing yay package(s)... :: yay package(s) failed to install. Check .SRCINFO for mismatching data with PKGBUILD. ```