[pkg-go] Bug#792053: prometheus: FTBFS w/ test suite errors
Source: prometheus Version: 0.14.0+ds-1 Severity: serious Justification: fails to build from source Builds of prometheus on those architectures on which its build dependencies are available (so far just armel, armhf, and i386, aside from amd64) have been failing with assorted test suite errors: https://buildd.debian.org/status/logs.php?pkg=prometheus&ver=0.14.0%2Bds-1 Architectural differences might play a part here (all attempted builds were 32-bit), but I suspect buildd configuration quirks may also be relevant, so I've gone with a severity of serious. Could you please take a look? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#792053: Bug#792053: prometheus: FTBFS w/ test suite errors
Martín Ferrari writes: > This is pretty weird.. There are a few precision mismatches, but many > instances of "expected 1, got 0". I will get some 32 bit machine and > take a look. Great, thanks. As I said, I suspect at least some of the errors are due to buildd quirks rather than architectural differences, so you might need to install sbuild and perhaps also adjust its configuration to match the autobuilders more closely. (I'm not familiar with the setup details myself, so I can't offer any specifics here, sorry.) > Thanks for reporting! Thanks for following up right away! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#792053: prometheus: FTBFS w/ test suite errors
found 792053 0.15.1+ds-1 notfixed 792053 0.15.1+ds-1 thanks "Aaron M. Ucko" writes: > Builds of prometheus on those architectures on which its build > dependencies are available (so far just armel, armhf, and i386, aside > from amd64) have been failing with assorted test suite errors: I'm happy to confirm that 0.15.1+ds-1 fixes the original errors. However, new ones have cropped up, per https://buildd.debian.org/status/logs.php?pkg=prometheus&ver=0.15.1%2Bds-1 : TestEvictAndLoadChunkDescsType0 fails on armhf, and TestEvictAndLoadChunkDescsType1 fails on armel and i386. Could you please take another look? Incidentally, I did not explicitly request an update to a new upstream release (though I certainly don't object!), so best practice would have been to note in the changelog what this bug report was actually about. You'll get a chance yet. ;-) Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#798135: gb: FTBFS: insists on building with -m64
Source: gb Version: 0.1.0-1 Severity: important Justification: fails to build from source Builds of gb for 32-bit architectures (armel, armhf, and i386) all failed because the compilation command lines in cgo.go specify -m64. Please remove this option, since it is always either redundant or inappropriate (depending on the architecture). Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#798725: golang-github-vbatts-tar-split: FTBFS: B-D favors nonexistent packages over real ones
Source: golang-github-vbatts-tar-split Version: 0.9.7-1 Severity: serious Justification: fails to build from source Automatic builds of golang-github-vbatts-tar-split have been failing because its build dependencies include golang-github-codegangsta-cli-dev | golang-codegangsta-cli-dev and golang-github-sirupsen-logrus-dev | golang-logrus-dev These terms are both technically satisfiable because golang-codegangsta-cli-dev and golang-logrus-dev both exist in the archive. However, for the sake of reproducibility, the autobuilders only ever try the first option (modulo explicit architectural constraints), and consequently fail. Please either remove the references to golang-github-*-dev or swap them to appear after the packages that are actually available. Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#798725: Bug#798725: golang-github-vbatts-tar-split: FTBFS: B-D favors nonexistent packages over real ones
Michael Stapelberg writes: > I think the better fix is to actually upload > golang-github-codegangsta-cli-dev and > golang-github-sirupsen-logrus-dev. Go for it (no pun intended), but bear in mind that this issue will persist until the uploads clear NEW. Meanwhile, rawdns's build dependency on golang-github-miekg-dns-dev | golang-dns-dev is similarly problematic. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#802507: runc: FTBFS on non-amd64: undefined: jumpEqualTo et al.
Source: runc Version: 0.0.3~dfsg2-1 Severity: important Justification: fails to build from source Builds of runc for architectures other than amd64 have been failing: # github.com/opencontainers/runc/libcontainer/seccomp src/github.com/opencontainers/runc/libcontainer/seccomp/filter.go:93: undefined: jumpEqualTo src/github.com/opencontainers/runc/libcontainer/seccomp/filter.go:95: undefined: jumpNotEqualTo src/github.com/opencontainers/runc/libcontainer/seccomp/filter.go:97: undefined: jumpGreaterThan src/github.com/opencontainers/runc/libcontainer/seccomp/filter.go:99: undefined: jumpLessThan src/github.com/opencontainers/runc/libcontainer/seccomp/filter.go:101: undefined: jumpMaskEqualTo The issue appears to be that these functions are defined only for that architecture (by .../jump_amd64.go), but then used unconditionally. Could you please take a look? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#802787: golang-github-tinylib-msgp: FTBFS: constant 2147483747 overflows int
Source: golang-github-tinylib-msgp Version: 1.0~alpha-1 Severity: important Justification: fails to build from source Builds of golang-github-tinylib-msgp for 32-bit architectures such as i386 have been failing: # github.com/tinylib/msgp/msgp src/github.com/tinylib/msgp/msgp/write_test.go:15: constant 2147483747 overflows int ... okgithub.com/tinylib/msgp/_generated 0.004s ? github.com/tinylib/msgp [no test files] ? github.com/tinylib/msgp/gen [no test files] FAIL github.com/tinylib/msgp/msgp [build failed] ? github.com/tinylib/msgp/parse [no test files] ? github.com/tinylib/msgp/printer [no test files] dh_auto_test: go test -v github.com/tinylib/msgp/_generated github.com/tinylib/msgp github.com/tinylib/msgp/gen github.com/tinylib/msgp/msgp github.com/tinylib/msgp/parse github.com/tinylib/msgp/printer returned exit code 2 debian/rules:13: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 2 make[1]: Leaving directory '/«PKGBUILDDIR»' debian/rules:16: recipe for target 'build-arch' failed make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Could you please take a look? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#802793: golang-github-miekg-mmark: FTBFS: favors unavailable packages
Source: golang-github-miekg-mmark Version: 1.2+git20150919.694.bc8de59+dfsg-1 Severity: serious Justification: fails to build from source Automated builds of golang-github-miekg-mmark have been failing due to the autobuilders' policy of disregarding alternatives in most cases for the sake of reproducibility (as in golang-github-vbatts-tar-split bug #798725): The following packages have unmet dependencies: sbuild-build-depends-golang-github-miekg-mmark-dummy : Depends: golang-github-burntsushi-toml-dev but it is not installable Please accommodate this policy by flipping the build dependency golang-github-burntsushi-toml-dev | golang-toml-dev until golang-github-burntsushi-toml-dev hits unstable. Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#802794: golang-github-xordataexchange-crypt: FTBFS: favors unavailable packages
Source: golang-github-xordataexchange-crypt Version: 0.0.2+git20150523.17.749e360-1 Severity: serious Justification: fails to build from source Automated builds of golang-github-xordataexchange-crypt have been failing due to the autobuilders' policy of disregarding alternatives in most cases for the sake of reproducibility (as in golang-github-vbatts-tar-split bug #798725): The following packages have unmet dependencies: sbuild-build-depends-golang-github-xordataexchange-crypt-dummy : Depends: golang-github-coreos-go-etcd-dev but it is not installable Depends: golang-golang-x-crypto-dev but it is not installable Please accommodate this policy by flipping the build dependencies golang-github-coreos-go-etcd-dev | golang-etcd-dev and golang-golang-x-crypto-dev | golang-go.crypto-dev until packages with the new names hit unstable. Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#802796: docker-registry: FTBFS: favors unavailable package versions
Source: docker-registry Version: 2.1.1~ds1-1 Severity: serious Justification: fails to build from source Automated builds of docker-registry have been failing due to the autobuilders' policy of disregarding alternatives in most cases for the sake of reproducibility (as in golang-github-vbatts-tar-split bug #798725): The following packages have unmet dependencies: sbuild-build-depends-docker-registry-dummy : Depends: golang-github-docker-docker-dev but it is not installable Depends: golang-golang-x-crypto-dev but it is not installable Depends: golang-gopkg-check.v1-dev but it is not installable Depends: golang-gopkg-yaml.v2-dev but it is not installable Please flip the relevant Build-Depends clauses until packages with the new names hit unstable. Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#803496: fleet: FTBFS w/golang(-github-docker)-docker-dev 1.8
Source: fleet Version: 0.11.5+dfsg-1 Severity: serious Justification: fails to build from source Builds of fleet against current unstable have been failing with errors along the lines of src/github.com/coreos/fleet/machine/coreos.go:26:2: cannot find package "github.com/docker/libcontainer/netlink" in any of: /usr/lib/go/src/github.com/docker/libcontainer/netlink (from $GOROOT) /«BUILDDIR»/fleet-0.11.5+dfsg/obj-i586-linux-gnu/src/github.com/docker/libcontainer/netlink (from $GOPATH) I see that golang-docker-dev 1.8.3~ds1-1 is a transitional package for golang-github-docker-docker-dev, which installs to a somewhat different location and no longer supplies libcontainer/netlink at all. The new home for that code appears to be golang-github-opencontainers-runc-dev, which provides github.com/opencontainers/runc/libcontainer/netlink. Could you please take a look? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#805039: consul-migrate: FTBFS (32-bit): MDB_INVALID: File is not an LMDB file
Source: consul-migrate Version: 0.1.0-1 Severity: important Justification: fails to build from source Builds of consul-migrate for 32-bit architectures (armel, armhf, and i386) all failed: === RUN TestMigrator_data --- FAIL: TestMigrator_data (0.00s) migrator_test.go:60: err: MDB_INVALID: File is not an LMDB file === RUN TestMigrator_new --- PASS: TestMigrator_new (0.00s) === RUN TestMigrator_migrate --- FAIL: TestMigrator_migrate (0.00s) migrator_test.go:130: err: Failed to connect MDB: MDB_INVALID: File is not an LMDB file %!s(MISSING) Could you please take a look? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#805040: consul-migrate: FTBFS on ppc64: undefined: maxMapSize
Source: consul-migrate Version: 0.1.0-1 Severity: important Justification: fails to build from source The consul-migrate build for (big-endian) ppc64 failed: # github.com/boltdb/bolt src/github.com/boltdb/bolt/db.go:85: undefined: maxMapSize src/github.com/boltdb/bolt/db.go:85: invalid array bound maxMapSize Could you please take a look? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#810949: ITP: ncbi-entrez-direct -- NCBI Entrez utilities on the command line
Package: wnpp Severity: wishlist Owner: "Aaron M. Ucko" * Package name: ncbi-entrez-direct Version : 3.60 Upstream Author : Jonathan Kans * URL : http://www.ncbi.nlm.nih.gov/books/NBK179288 * License : Public Domain Programming Lang: Perl, Go, Bourne shell Description : NCBI Entrez utilities on the command line Entrez Direct (EDirect) is an advanced method for accessing NCBI's set of interconnected databases (publication, sequence, structure, gene, variation, expression, etc.) from a terminal window or script. Functions take search terms from command-line arguments. Individual operations are combined to build multi-step queries. Record retrieval and formatting normally complete the process. EDirect also provides an argument-driven function that simplifies the extraction of data from document summaries or other results that are returned in structured XML format. This can eliminate the need for writing custom software to answer ad hoc questions. Queries can move seamlessly between EDirect commands and UNIX utilities or scripts to perform actions that cannot be accomplished entirely within Entrez. With all due respect to the Go packaging team, I feel that maintaining EDirect within Debian Med or perhaps Debian Science would be more appropriate, as it falls outside the mainstream Go ecosystem. Yes, one individual tool happens to be written in Go, but EDirect otherwise consists of a mixture of Perl and shell scripts, and the Go tool has no dependencies beyond the standard library. Also, I am inclined to build the tool in question with gccgo rather than golang-go, which is available for fewer architectures and provides no obvious way to obtain dynamic linkage against system libraries, for which Policy 10.1 calls. I'm debating whether to go fully dynamic (yielding, on amd64, a 228K executable depending on a 34M library with hardly any other reverse dependencies) or to link libgo statically (yielding a 3.2M executable with no exotic dependencies). I suppose the fully dynamic approach is better practice, but would appreciate feedback on this point. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#819994: golang-gogoprotobuf: FTBFS (32-bit or BE): many tests fail
Source: golang-gogoprotobuf Version: 0.0~git20150426-1 Severity: important Justification: fails to build from source Builds of golang-gogoprotobuf on 32-bit architectures such as i386 and on ppc64 (the only big-endian architecture on which its build dependencies were available) all failed with test suite errors because various results weren't as expected. The details vary by architecture, per https://buildd.debian.org/status/logs.php?pkg=golang-gogoprotobuf&ver=0.2-1 Could you please take a look? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#820466: golang-github-shirou-gopsutil-dev: not configured for ppc64(el)
Package: golang-github-shirou-gopsutil-dev Version: 1.0.0+git20160112-1 Severity: important The ppc64el build of nomad failed: # github.com/shirou/gopsutil/host src/github.com/shirou/gopsutil/host/host_linux.go:108: undefined: utmp src/github.com/shirou/gopsutil/host/host_linux.go:109: invalid expression unsafe.Sizeof(u) src/github.com/shirou/gopsutil/host/host_linux.go:117: undefined: utmp The issue appears to be that there's no appropriate host_linux_*.go for this architecture, on which Go is available nowadays. I anticipate a similar failure on ppc64 (though that's not a release architecture, FTR). Could you please take a look? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#820466: golang-github-shirou-gopsutil-dev: not configured for ppc64(el)
"Aaron M. Ucko" writes: > # github.com/shirou/gopsutil/host > src/github.com/shirou/gopsutil/host/host_linux.go:108: undefined: utmp > src/github.com/shirou/gopsutil/host/host_linux.go:109: invalid expression > unsafe.Sizeof(u) > src/github.com/shirou/gopsutil/host/host_linux.go:117: undefined: utmp These same errors showed up on arm64. It looks like the existing host_linux_arm.go is actually meant for arm64; please recharacterize it appropriately and add a version suitable for 32-bit ARM (armel/armhf). Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#828767: toxiproxy: FTBFS: B-D favors old mux, logrus packages
Source: toxiproxy Version: 2.0.0+dfsg1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Automated builds of toxiproxy have been failing to start because its build dependencies include golang-mux-dev | golang-github-gorilla-mux-dev golang-github-gorilla-mux-dev has replaced golang-mux-dev in the archive, but the autobuilders don't care because they ignore alternative dependencies for the sake of determinism (unless architecture qualifiers explicitly eliminate earlier options). Please either flip this dependency or specify just golang-github-gorilla-mux-dev. Likewise for golang-logrus-dev | golang-github-sirupsen-logrus-dev; although there's still a transitional golang-logrus-dev package in the archive, you shouldn't count on its long-term availability. Thanks! -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#828808: syncthing: FTBFS: FAIL: TestGithubRelease
Source: syncthing Version: 0.13.4+dfsg1-1 Severity: important Justification: fails to build from source Builds of syncthing failed on arm64, ppc64el, and ppc64 because the TestGithubRelease test failed: === RUN TestGithubRelease --- FAIL: TestGithubRelease (0.01s) upgrade_test.go:83: Error retrieving latest version couldn't find a release to download upgrade_test.go:86: Invalid upgrade release: v0.10.0-alpha -> v0.10.30, but got upgrade_test.go:83: Error retrieving latest version couldn't find a release to download upgrade_test.go:86: Invalid upgrade release: v0.10.0-beta -> v0.10.30, but got upgrade_test.go:83: Error retrieving latest version couldn't find a release to download upgrade_test.go:86: Invalid upgrade release: v0.11.0-beta0+40-g53cb66e-dirty -> v0.11.0-beta0, but got upgrade_test.go:83: Error retrieving latest version couldn't find a release to download upgrade_test.go:86: Invalid upgrade release: v0.10.21 -> v0.10.30, but got upgrade_test.go:83: Error retrieving latest version couldn't find a release to download upgrade_test.go:86: Invalid upgrade release: v0.10.29 -> v0.10.30, but got Could you please take a look? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#828767: toxiproxy: FTBFS: B-D favors old mux, logrus packages
notfixed 828767 2.0.0+dfsg1-2 found 828767 2.0.0+dfsg1-2 thanks "Aaron M. Ucko" writes: > Please either flip this dependency or specify just > golang-github-gorilla-mux-dev. > > Likewise for golang-logrus-dev | golang-github-sirupsen-logrus-dev; Thanks for the quick upload, but these failures are still occurring -- it looks like you accidentally left this change out of -2. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#828767: closed by Alexandre Viau (Fixed in 2.0.0+dfsg1-2)
notfixed 828767 2.0.0+dfsg1-2 found 828767 2.0.0+dfsg1-2 thanks Debian Bug Tracking System writes: > I have fixed this issue in 2.0.0+dfsg1-2. I understand you meant to, but AFAICT you accidentally left the fix out. https://anonscm.debian.org/cgit/pkg-go/packages/toxiproxy.git/commit/?id=48c8abb3bb1cf2fedd0b61415d79633a00de1e44 shows a changelog entry with no corresponding change to debian/control, and the autobuilders are still complaining about golang-mux-dev: https://buildd.debian.org/status/fetch.php?pkg=toxiproxy&arch=i386&ver=2.0.0%2Bdfsg1-2&stamp=1467219777 The following packages have unmet dependencies: sbuild-build-depends-toxiproxy-dummy : Depends: golang-mux-dev but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#830936: prometheus-alertmanager: FTBFS on arm64: dispatch_test.go:132: received batch to[o] early
Source: prometheus-alertmanager Version: 0.3.0+ds-1 Severity: important Justification: fails to build from source The arm64 build of prometheus-alertmanager failed: === RUN TestAggrGroup --- FAIL: TestAggrGroup (1.30s) dispatch_test.go:132: received batch to early after 299.982ms === RUN TestInhibitRuleHasEqual --- PASS: TestInhibitRuleHasEqual (0.00s) === RUN TestInhibitRuleGC --- PASS: TestInhibitRuleGC (0.00s) === RUN TestRouteMatch --- PASS: TestRouteMatch (0.00s) FAIL FAIL github.com/prometheus/alertmanager 1.314s Could you please take a look? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#831334: golang-glide: FTBFS on i386: cannot create 'obj-i386-linux-gnu/...'
Source: golang-glide Version: 0.11.0-1 Severity: important Justification: fails to build from source The i386 build of golang-glide failed: debian/rules override_dh_auto_test make[1]: Entering directory '/«PKGBUILDDIR»' cp -a testdata obj-i386-linux-gnu/src/github.com/Masterminds/glide/. cp: cannot create directory 'obj-i386-linux-gnu/src/github.com/Masterminds/glide/.': No such file or directory debian/rules:12: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 Please try substituting DEB_HOST_GNU_TYPE for DEB_HOST_MULTIARCH here. Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#831724: mtail: FTBFS on non-amd64: go test -race unsupported
Package: mtail Version: 0.0+git20160704.35c4023-1 Severity: important Justification: fails to build from source Builds of mtail for architectures other than amd64 all failed: GOPATH=/«BUILDDIR»/mtail-0.0+git20160704.35c4023/build go test -v -timeout 5m -race github.com/google/mtail go test: -race and -msan are only supported on linux/amd64, freebsd/amd64, darwin/amd64 and windows/amd64 debian/rules:25: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 2 make[1]: Leaving directory '/«BUILDDIR»/mtail-0.0+git20160704.35c4023' debian/rules:17: recipe for target 'build-arch' failed make: *** [build-arch] Error 2 Could you please arrange to skip this test for these architectures? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#834459: gitlab-ci-multi-runner: FTBFS: TestMachineLimitMax fails on several architectures
Source: gitlab-ci-multi-runner Version: 1.4.1+dfsg-1 Severity: important Justification: fails to build from source Builds of gitlab-ci-multi-runner failed on the release architectures armel, armhf, and i386, and the non-release architecture ppc64, with errors in TestMachineLimitMax, as detailed at https://buildd.debian.org/status/logs.php?pkg=gitlab-ci-multi-runner&ver=1.4.1%2Bdfsg-1 Could you please take a look? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#834785: golang-github-xenolf-lego: FTBFS (32-bit): gandi_test unmarshal error
Source: golang-github-xenolf-lego Version: 0.3.1-1 Severity: important Justification: fails to build from source Builds of golang-github-xenolf-lego for 32-bit architectures such as i386 have been failing: === RUN TestDNSProvider --- FAIL: TestDNSProvider (0.02s) gandi_test.go:86: Gandi DNS: Unmarshal Error: strconv.ParseInt: parsing "33": value out of range Could you please take a look? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#836805: gobgp: FTBFS (i386): undefined: syscall.SYS_SETSOCKOPT
Source: gobgp Version: 1.10-1 Severity: important Justification: fails to build from source The i386 build of gobgp failed: # github.com/osrg/gobgp/server src/github.com/osrg/gobgp/server/sockopt.go:66: undefined: syscall.SYS_SETSOCKOPT src/github.com/osrg/gobgp/server/sockopt_linux.go:95: undefined: syscall.SYS_SETSOCKOPT AFAICT, this error stems from the fact that early Linux architectures such as i386 historically multiplexed setsockopt and several other functions through a special "socketcall" syscall. i386 did eventually develop a dedicated setsockopt syscall (number 366), but zsysnum_linux_386.go doesn't (yet) reflect that, and I don't know what the runtime portability considerations of using it would be anyway. Instead, I'd recommend using the predefined syscall.setsockopt wrapper. Could you please take a look? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#840031: gobgp: FTBFS (32-bit): constant 4294967295 overflows int
Source: gobgp Version: 1.12-1 Severity: important Justification: fails to build from source Builds of gobgp for 32-bit architectures are doing better now that you've addressed #836805 (thanks!), but still ultimately fail: # github.com/osrg/gobgp/table src/github.com/osrg/gobgp/table/policy_test.go:2338: constant 4294967295 overflows int FAIL github.com/osrg/gobgp/table [build failed] Could you please take a look? Thanks! ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#843674: gocryptfs: FTBFS: "pkg-config": executable file not found in $PATH
Source: gocryptfs Version: 1.0-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of gocryptfs in minimal environments (as on the autobuilders) have been failing: pkg-config: exec: "pkg-config": executable file not found in $PATH Please declare a build dependency on pkg-config, and confirm with pbuilder or the like that you haven't missed anything else. Thanks! FTR, I classified this bug as a regression because it would affect any binNMUs that might be necessary. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#843786: gocryptfs: FTBFS on arm64: undefined: syscall.Dup2
Source: gocryptfs Version: 1.1.1-1 Severity: important Justification: fails to build from source Thanks for promptly fixing gocryptfs's build dependencies. Alas, the arm64 build is still failing: obj-aarch64-linux-gnu/src/github.com/rfjakob/gocryptfs/mount.go:99: undefined: syscall.Dup2 obj-aarch64-linux-gnu/src/github.com/rfjakob/gocryptfs/mount.go:100: undefined: syscall.Dup2 Per https://github.com/golang/go/issues/11981, this is apparently a known limitation of the standard syscall package; please substitute Dup3 here, perhaps by way of golang-golang-x-sys-dev. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#843787: golang-github-jacobsa-crypto-dev: hash_64bit.go misses ppc64(el)
Package: golang-github-jacobsa-crypto-dev Version: 0.0~git20160410.0.42daa9d-2 Severity: important Builds of gocryptfs on ppc64el and the non-release architecure ppc64 have been failing: obj-powerpc64le-linux-gnu/src/github.com/jacobsa/crypto/cmac/hash.go:97: undefined: xorBlock The issue appears to be that the "// +build" setting in hash_64bit.go misses these architectures. Per https://golang.org/pkg/go/build/, it looks like there's no generic tag you can use here. Instead, I suppose you'll just have to add ppc64 and ppc64le there, per https://github.com/golang/go/issues/8654#user-content-c27. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#846037: rclone: FTBFS: cannot find "golang.org/x/oauth2/google"
Source: rclone Version: 1.34-1 Severity: serious Justification: fails to build from source Builds of rclone in minimal environments (as on the autobuilders) have been failing with errors along the lines of src/github.com/ncw/rclone/drive/drive.go:25:2: cannot find package "golang.org/x/oauth2/google" in any of: /usr/lib/go-1.7/src/golang.org/x/oauth2/google (from $GOROOT) /«PKGBUILDDIR»/obj-aarch64-linux-gnu/src/golang.org/x/oauth2/google (from $GOPATH) Please adjust the build dependency on golang-golang-x-oauth2-dev to golang-golang-x-oauth2-google-dev and confirm with pbuilder or the like that you haven't missed anything else. Please also ensure that golang-github-ncw-rclone-dev's runtime dependencies are complete. Thanks! Please note that I classified this bug as a regression even though rclone is new to Debian because the bug would affect binNMUs. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#854743: golang-github-mailru-easyjson: FTBFS (32-bit): constant 4294967295 overflows int
Source: golang-github-mailru-easyjson Version: 0.0~git20161103.0.159cdb8-1 Severity: important Justification: fails to build from source Builds of golang-github-mailru-easyjson for 32-bit architectures such as i386 have been failing: # github.com/mailru/easyjson/tests src/github.com/mailru/easyjson/tests/data.go:91: constant 4294967295 overflows int src/github.com/mailru/easyjson/tests/data.go:94: constant 4294967295 overflows int src/github.com/mailru/easyjson/tests/data.go:103: constant 4294967295 overflows int src/github.com/mailru/easyjson/tests/data.go:106: constant 4294967295 overflows int src/github.com/mailru/easyjson/tests/data.go:194: constant 4294967295 overflows int src/github.com/mailru/easyjson/tests/data.go:197: constant 4294967295 overflows int Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#854813: tendermint: FTBFS: MustWriteFile failed
Source: tendermint Version: 0.8.0+git20170113.0.764091d-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Automated builds of tendermint have been failing, because they deliberately run without home directories, much less writable ones: [...] MustWriteFile failed: open /sbuild-nonexistent/.tendermint_test/consensus_byzantine_test/config.toml: no such file or directory exit status 1 FAIL github.com/tendermint/tendermint/consensus 0.091s [...] Please arrange for these tests to use a fake $HOME in the build area. Thanks! FTR, even though tendermint is new to Debian, I'm classifying this bug as a regression because it would affect binNMUs. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#855487: tendermint: FTBFS (32-bit): TestByzantine index out of range
Source: tendermint Version: 0.8.0+git20170113.0.764091d-2 Severity: important Justification: fails to build from source Thanks for taking care of #854813, which allowed the automatic builds on arm64 and ppc64 to succeed. Alas, 32-bit builds (on armel, armhf, and i386) are still failing -- on i386, for instance, I see --- FAIL: TestByzantine (0.12s) panic: runtime error: index out of range [recovered] panic: runtime error: index out of range goroutine 14 [running]: panic(0x8582780, 0x18c2a028) /usr/lib/go-1.7/src/runtime/panic.go:500 +0x331 testing.tRunner.func1(0x18c6d900) /usr/lib/go-1.7/src/testing/testing.go:579 +0x14f panic(0x8582780, 0x18c2a028) /usr/lib/go-1.7/src/runtime/panic.go:458 +0x40b github.com/tendermint/tendermint/consensus.TestByzantine(0x18c6d900) /«BUILDDIR»/tendermint-0.8.0+git20170113.0.764091d/obj-i686-linux-gnu/src/github.com/tendermint/tendermint/consensus/byzantine_test.go:109 +0x154f testing.tRunner(0x18c6d900, 0x8769d30) /usr/lib/go-1.7/src/testing/testing.go:610 +0x8c created by testing.(*T).Run /usr/lib/go-1.7/src/testing/testing.go:646 +0x2a5 exit status 2 FAILgithub.com/tendermint/tendermint/consensus 0.237s from https://buildd.debian.org/status/fetch.php?pkg=tendermint&arch=i386&ver=0.8.0%2Bgit20170113.0.764091d-2&stamp=1487431593&raw=0 Could you please take a look? (The consensus test also failed on ppc64el for an apparently unrelated reason, which I'll report separately.) Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#855488: tendermint: FTBFS on ppc64el: consensus test times out (hangs?)
Source: tendermint Version: 0.8.0+git20170113.0.764091d-2 Severity: important Justification: fails to build from source The ppc64el build of tendermint failed, as detailed in https://buildd.debian.org/status/fetch.php?pkg=tendermint&arch=ppc64el&ver=0.8.0%2Bgit20170113.0.764091d-2&stamp=1487432110&raw=0: *** Test killed with quit: ran too long (10m0s). FAILgithub.com/tendermint/tendermint/consensus 600.013s Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#870643: golang-github-pierrec-lz4-dev: please split off test data
Package: golang-github-pierrec-lz4-dev Version: 0.0~git20170519.0.5a3d224-1 Severity: minor The golang-github-pierrec-lz4-dev binary package now consists of 9+ MB of test data and a much smaller quantity of actual code. I acknowledge the value of automated regression testing, but would appreciate it if you could please split the test data into a separate binary package. Thanks! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, x32 Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#871447: golang-github-gogo-protobuf-dev: please split off test data
Package: golang-github-gogo-protobuf-dev Version: 0.3+git20170120.144.265e960d-1 Severity: minor Following up on #870643, I see that several other go packages, notably golang-github-gogo-protobuf-dev, contain much more test data (nearly 22M in this case) than actual code. Once again, I acknowledge the value of automated regression testing, but would appreciate it if you could please split the test data into a separate binary package. Thanks! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, x32 Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) golang-github-gogo-protobuf-dev depends on no packages. Versions of packages golang-github-gogo-protobuf-dev recommends: ii gogoprotobuf 0.3+git20170120.144.265e960d-1 golang-github-gogo-protobuf-dev suggests no packages. -- no debconf information ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#871448: golang-github-mattn-go-sqlite3-dev: please unbundle SQLite
Package: golang-github-mattn-go-sqlite3-dev Version: 1.2.0+git20170710.100.47fc4e5~dfsg1-1 Severity: normal golang-github-mattn-go-sqlite3-dev now includes a full copy of the SQLite3 amalgamation, roughly 7.5 MB in size. Per Policy 4.13, please omit it from the binary package, and consider dropping it from the source package (which you're evidently already repacking) as well. Thanks! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, x32 Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages golang-github-mattn-go-sqlite3-dev depends on: ii libsqlite3-dev 3.19.3-3 golang-github-mattn-go-sqlite3-dev recommends no packages. golang-github-mattn-go-sqlite3-dev suggests no packages. -- no debconf information ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#870643: Bug#870643: golang-github-pierrec-lz4-dev: please split off test data
Paul Tagliamonte writes: > As with the other bug, I don't see the point in this. This package is > used as a Build-Dependency, and not used by either end-users, or > developers working on Go source code on Debian, so splitting this off > will add space in the archive, and add a lot of complexity. Hi, Paul. Thanks for clarifying; I'd thought there was more of a use case for having these packages installed locally. Does everyone just use private GitHub checkouts? -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#873889: elvish: FTBFS on ppc64(el): several tests fail
Source: elvish Version: 0.9+git20170829.a2ab19c-1 Severity: important Tags: upstream Justification: fails to build from source Builds of elvish for ppc64el and the non-release architecture ppc64 have been failing with test suite errors as detailed at https://buildd.debian.org/status/fetch.php?pkg=elvish&arch=ppc64el&ver=0.9%2Bgit20170829.a2ab19c-1&stamp=1504173324&raw=0 and https://buildd.debian.org/status/fetch.php?pkg=elvish&arch=ppc64&ver=0.9%2Bgit20170829.a2ab19c-1&stamp=1504174088&raw=0 respectively. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#882450: golang-github-alecthomas-chroma: FTBFS w/gccgo: Name undefined
Source: golang-github-alecthomas-chroma
Version: 0.1.1+git20171116.9c81d25-1
Severity: important
Justification: fails to build from source
Builds of golang-github-alecthomas-chroma for architectures using
gccgo on which the compiler didn't crash altogether failed with a pile
of errors of the form
src/github.com/alecthomas/chroma/lexers/c.go:46:21: error: reference to
undefined name 'Name'
{`[a-zA-Z_]\w*`, Name, nil},
as detailed in
https://buildd.debian.org/status/fetch.php?pkg=golang-github-alecthomas-chroma&arch=mips&ver=0.1.1%2Bgit20171116.9c81d25-1&stamp=1511279629&raw=0
https://buildd.debian.org/status/fetch.php?pkg=golang-github-alecthomas-chroma&arch=mips64el&ver=0.1.1%2Bgit20171116.9c81d25-1&stamp=1511288473&raw=0
https://buildd.debian.org/status/fetch.php?pkg=golang-github-alecthomas-chroma&arch=s390x&ver=0.1.1%2Bgit20171116.9c81d25-1&stamp=1511278679&raw=0
https://buildd.debian.org/status/fetch.php?pkg=golang-github-alecthomas-chroma&arch=alpha&ver=0.1.1%2Bgit20171116.9c81d25-1&stamp=1511292496&raw=0
https://buildd.debian.org/status/fetch.php?pkg=golang-github-alecthomas-chroma&arch=powerpc&ver=0.1.1%2Bgit20171116.9c81d25-1&stamp=1511278856&raw=0
I'm not sure offhand why s390x used gccgo, since golang-1.9 does
appear to be available there.
At any rate, could you please take a look?
Thanks!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#882450: Bug#882450: golang-github-alecthomas-chroma: FTBFS w/gccgo: Name undefined
"Dr. Tobias Quathamer" writes: > Hm, unfortunately, the new upload didn't do the trick. Thanks for trying to address these errors. I suspect we're looking at a case of using Go 1.9 functionality that isn't yet in gccgo, which is still at a compatibility level of 1.8 as of GCC 7. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#886142: gitea: FTBFS on mips*: -buildmode=pie not supported
Source: gitea Version: 1.3.2+dfsg-1 Severity: important Justification: fails to build from source User: debian-m...@lists.debian.org Usertags: mips mips64el mipsel Builds of gitea for mips* have been failing with errors along the lines of -buildmode=pie not supported on linux/mips Please either conditionalize the use of this option or restrict the package's architecture setting appropriately. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#892429: irtt: FTBFS w/gccgo
Package: irtt Version: 0.9.0-2 Severity: important Justification: fails to build from source Builds of irtt with gccgo (on s390x and most non-release architectures) failed with various errors, as detailed at [1]. Perhaps some of these architectures will be able to do better now that we have gccgo 8, but if they don't, you may wish to consider specifically build-depending on golang-go. Could you please take a look? Thanks! [1] https://buildd.debian.org/status/logs.php?pkg=irtt&ver=0.9.0-2 -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] gccgo bug reports
John Paul Adrian Glaubitz writes: > Can we agree on some usertag for any bug reports in which a Go package > builds fine on golang-go but not gccgo-go? Hi, Adrian! How about User: debian-...@lists.debian.org Usertags: gccgo (debian-gcc rather than pkg-go-maintainers so that Alioth's upcoming retirement won't be an issue). I'm open to other suggestions, though. > The plan is that gccgo-go builds all packages that golang-go builds. Definitely a worthy goal. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#893741: golang-golang-x-net-dev: misses support for some (non-release, gccgo) architectures
Package: golang-golang-x-net-dev Version: 1:0.0+git20170629.c81e7f2+dfsg-2 Severity: normal Tags: upstream Control: affects -1 src:irtt golang-golang-x-net-dev lacks support for most or all gccgo architectures (none of which are release architectures, granted), leading to heavy errors when trying to build dependent packages such as irtt on these architectures, as in [1]: # golang.org/x/net/internal/socket src/golang.org/x/net/internal/socket/cmsghdr.go:9:10: error: use of undefined type 'cmsghdr' [...] Could you please take a look? Thanks! [1] https://buildd.debian.org/status/fetch.php?pkg=irtt&arch=alpha&ver=0.9.0-2&stamp=1519744561&raw=0 -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
