[pkg-go] Bug#871566: swarmkit FTBFS: cannot find package "github.com/docker/docker/api/types"
swarmkit should build-dep on golang-github-docker-docker-dev (>= 1.13.1~), or something like that. ___ 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#871566: swarmkit FTBFS: cannot find package "github.com/docker/docker/api/types"
I was able to build swarmkit on arm64 after I manually installed a newer golang-github-docker-docker-dev. There's some kind of circular dependency between swarmkit and docker.io. I think someone will have to break it with a binary upload. (There was a binary upload on amd64, I notice.) According to my "history", I did something like: apt-get build-dep docker.io apt-get build-dep swarmkit apt-get install golang-github-docker-docker-dev wget http://ftp.uk.debian.org/debian/pool/main/d/docker.io/golang-github-docker-docker-dev_1.13.1~ds2-3_all.deb dpkg -i golang-github-docker-docker-dev_1.13.1~ds2-3_all.deb apt-get install golang-github-opencontainers-docker-runc-dev apt --fix-broken install dpkg -i golang-github-docker-docker-dev_1.13.1~ds2-3_all.deb apt-get source swarmkit cd swarmkit-1.12.0+git20170111.763.296fcfcf dpkg-buildpackage -b ___ 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#871566: swarmkit FTBFS: cannot find package "github.com/docker/docker/api/types"
The build failure quoted above is not reproducible with the current state of sid, I think. However, it is still not possible to build swarmkit for a different reason: an indirect dependency on golang-github-juju-ansiterm. See #886613 and the "Dependency installability problem for swarmkit" on arm64 and other architectures: https://buildd.debian.org/status/package.php?p=swarmkit=sid ___ 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#803133: etcd: FTBFS on arm64, ppc64, ppc64el
Source: etcd Version: 2.2.0+dfsg-2 It failed to build: https://buildd.debian.org/status/package.php?p=etcd=sid In each case the error was: # 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 It appears that this may have been fixed upstream, though the patch is not exactly perspicuous: https://github.com/glevand/coreos--coreos-overlay/commit/5ecd5f6be491e50fc55a9ad1fbfd89dd21ee988c ___ 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#803099: golang-ginkgo: FTBFS on arm64
Source: golang-ginkgo Version: 1.2.0-1 It failed to build on arm64: https://buildd.debian.org/status/package.php?p=golang-ginkgo=sid The error was: src/github.com/onsi/ginkgo/internal/remote/output_interceptor_unix.go:34: undefined: syscall.Dup2 src/github.com/onsi/ginkgo/internal/remote/output_interceptor_unix.go:35: undefined: syscall.Dup2 On arm64 there is no dup2 system call; there's only dup3: dup2(oldfd, newfd) is equivalent to dup3(oldfd, newfd, 0) unless oldfd == newfd. I don't know whether you can use dup3 on all the architectures you care about or whether there's a Go package that already provides a Dup2 wrapper that works on all architectures. If you're not interested in errors and don't care about the performance cost of an additional system call then you could probably just call Dup2 and Dup3: one will do what you want and the other won't do any damage even if both are implemented, as far as I can tell. ___ 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#803099: golang-ginkgo: FTBFS on arm64
I must have been thinking of an entirely different programming language. For some reason I was thinking that the undefined syscall was a run-time rather than a compile-time error. Clearly you can't use Dup2 at all on arm64. Does that mean you need two additional source files, one with "// +build arm64", one with "// +build !arm64", if there isn't already a wrapper defined somewhere else? ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
