go build github.com/prometheus/prometheus/tsdb/cmd/tsdb: build output "tsdb" already exists and is a directory !! exit status 1 command failed: build -o tsdb -ldflags -X github.com/prometheus/common/version.Version=2.13.1 -X github.com/prometheus/common/version.Revision=6f92ce5 -X github.com/prometheus/common/version.Branch=non-git -X github.com/prometheus/common/version.BuildUser=portage@mr-fox -X github.com/prometheus/common/version.BuildDate=20191018-04:05:19 -extldflags '-static' -mod=vendor -a -tags netgo github.com/prometheus/prometheus/tsdb/cmd/tsdb github.com/prometheus/promu/cmd.buildBinary /var/tmp/portage/dev-util/promu-0.5.0/work/promu-0.5.0/src/github.com/prometheus/promu/cmd/build.go:85 github.com/prometheus/promu/cmd.buildAll ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-20191015-081535 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * clang: clang version 9.0.0 (tags/RELEASE_900/final) Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/9/bin llvm: 9.0.0 Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) [3] pypy3 (fallback) [4] pypy (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.38.0 * repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Fri, 18 Oct 2019 02:06:02 +0000 emerge -qpvO app-metrics/prometheus [ebuild N ] app-metrics/prometheus-2.13.1
Created attachment 593206 [details] emerge-info.txt
Created attachment 593208 [details] app-metrics:prometheus-2.13.1:20191018-040515.log
Created attachment 593210 [details] emerge-history.txt
Created attachment 593212 [details] environment
Created attachment 593214 [details] etc.portage.tbz2
Now that this package version is marked 'stable' (and also the only version available), I'm also trying to build this package. I'm getting the same error in a native, amd64-keyworded setup. I can't really offer much more, I just wanted to say that the issue also crops up in a 'stable' system.
I should add sorry, that I can chase up some log files, however I'm not sure that you need everyone confirming a bug to add more of the same.
Sorry, overlooked this bug. Issue is fixed in 5e31382fb440eec96fa7e0a8f6a5b8f42b138b9a
Thanks, Manuel.