Affected Version
9.4.4
Issue
On fresh arch install, there is an issue about inconsistent vendoring
Steps to reproduce
sudo pacman -Syu git base-devel
git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si
Output
[jscherrerl@gcp-arch-linux yay]$ makepkg -si
==> Making package: yay 9.4.4-1 (Wed 26 Feb 2020 10:05:21 PM UTC)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Installing missing dependencies...
9resolving dependencies...
looking for conflicting packages...
Packages (1) go-2:1.14-1
Total Download Size: 127.20 MiB
Total Installed Size: 487.74 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
go-2:1.14-1-x86_64 127.2 MiB 13.9 MiB/s 00:09 [#####################################################################################################################################################] 100%
(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) installing go [#####################################################################################################################################################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
==> Retrieving sources...
-> Downloading yay-9.4.4.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 117 100 117 0 0 1158 0 --:--:-- --:--:-- --:--:-- 1158
100 351k 0 351k 0 0 865k 0 --:--:-- --:--:-- --:--:-- 865k
==> Validating source files with sha1sums...
yay-9.4.4.tar.gz ... Passed
==> Extracting sources...
-> Extracting yay-9.4.4.tar.gz with bsdtar
==> 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/jscherrerl/yay/src/yay-9.4.4 -asmflags all=-trimpath=/home/jscherrerl/yay/src/yay-9.4.4 -o yay
go: inconsistent vendoring in /home/jscherrerl/yay/src/yay-9.4.4:
github.com/Jguer/[email protected]: is explicitly required in go.mod, but vendor/modules.txt indicates github.com/Jguer/[email protected]
github.com/mikkeloscar/[email protected]: is explicitly required in go.mod, but vendor/modules.txt indicates github.com/mikkeloscar/[email protected]
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...
joscherrer
All 10 comments
A workaround would be to add "-mod=mod" in the EXTRA_GOFLAGS variable in PKGBUILD so that it looks like this:
EXTRA_GOFLAGS="-mod=mod -gcflags all=-trimpath=${PWD} -asmflags all=-trimpath=${PWD}" \
LDFLAGS="-linkmode external -extldflags \"${LDFLAGS}\"" \
make VERSION=$pkgver DESTDIR="$pkgdir" build
ALX99
on 26 Feb 2020
Came to post the same issue, but @ALX99 workaround doesn't work for dockerfile builds that a human isn't in the loop to edit the PKG on the fly.. is it possible to add this to the yay package itself?
tommyjcarpenter
on 27 Feb 2020
Working on it
Jguer
on 27 Feb 2020
yay v9.4.5 fixes this issue, CI broke so no arm releases, I'll update yay-bin as soon as possible
Jguer
on 27 Feb 2020
do you happen to know if https://aur.archlinux.org/yay.git is an up to date pointer of this repo? Or does some other update process need to run?
thank you for your help and contributions from all of us
tommyjcarpenter
on 27 Feb 2020
yay-git should be pointing to the latest commit in the next branch which is always the most up-to-date version of yay
Jguer
on 27 Feb 2020
worked now, thanks!
tommyjcarpenter
on 27 Feb 2020
yay-gitshould be pointing to the latest commit in the next branch which is always the most up-to-date version of yay
It's actually pointing to the master branch, so the package is kind of pointless right now as it only gets updated on new releases anyway (if I understood this right)
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=yay-git#n19
kattjevfel
on 29 Feb 2020
:sweat_smile: absolutely right, I thought it was just point to the default branch, I'll change it soon enough
Jguer
on 29 Feb 2020
Closing this as I've removed vendoring
Jguer
on 29 Feb 2020
Related issues
makeworld-the-better-one
路
3Comments
nivaca
路
4Comments
Qyriad
路
4Comments
GhostKraft
路
4Comments
ricochet1k
路
4Comments
Most helpful comment
A workaround would be to add "-mod=mod" in the EXTRA_GOFLAGS variable in PKGBUILD so that it looks like this: