Source: golang-github-influxdata-influxql Version: 0.0~git20180330.145e067-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20180502 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=golang --with=golang > dh_update_autotools_config -O--buildsystem=golang > dh_autoreconf -O--buildsystem=golang > dh_auto_configure -O--buildsystem=golang > dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install > -gcflags=\"-trimpath=/<<BUILDDIR>>/golang-github-influxdata-influxql-0.0\~git20180330.145e067/obj-x86_64-linux-gnu/src\" > > -asmflags=\"-trimpath=/<<BUILDDIR>>/golang-github-influxdata-influxql-0.0\~git20180330.145e067/obj-x86_64-linux-gnu/src\" > -v -p 8 github.com/influxdata/influxql > github.com/influxdata/influxql/internal > github.com/gogo/protobuf/proto > github.com/influxdata/influxql/internal > github.com/influxdata/influxql > dh_auto_test -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 > github.com/influxdata/influxql github.com/influxdata/influxql/internal > panic: open /usr/lib/go-1.10/lib/time/zoneinfo.zip: no such file or directory > > goroutine 1 [running]: > github.com/influxdata/influxql_test.mustLoadLocation(0x78a024, 0x13, > 0xc4200a6060) > > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/influxdata/influxql/parser_test.go:4041 > +0x6f > FAIL github.com/influxdata/influxql 0.004s > ? github.com/influxdata/influxql/internal [no test files] > dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 > github.com/influxdata/influxql github.com/influxdata/influxql/internal > returned exit code 1 The full build log is available from: http://aws-logs.debian.net/2018/05/02/golang-github-influxdata-influxql_0.0~git20180330.145e067-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
