Closed vixus0 closed 3 years ago
The only relevant command is likely to be
go install -p "$XBPS_MAKEJOBS" -mod="${go_mod_mode}" -x -tags "${go_build_tags}" -ldflags "${go_ldflags}" ${go_package}
Figured out the issue, looks like the root package name had changed.
System
Expected behavior
I coincidentally discovered this issue while trying some newer functionality available in recent versions of aws-vault.
Here's the correct output using a manual
go build .
from the archive downloaded intohostddir/sources
:Actual behavior
Incorrect output from the binary built by the package.
Steps to reproduce the behavior
It's sufficient to search for the string
Skipping session token
in the resulting aws-vault binary because it was removed from the source in 2019 but shows up in the latest void-packages build:Additional information
I tracked the issue down to the go modules that get populated during the
xbps-src
build. The output ofgo mod graph | grep 99designs/aws-vault
reveals an old v4.5.1 version of the module being pulled in.This doesn't appear when we just run
go build .
in the source directory, so there must be something in xbps-src's go build method that causes this. I'll do some more investigation and add anything I find here.