Bug#976907: golang-github-boltdb-bolt: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 -short github.com/boltdb/bolt github.co

> Can simply replacing the dependency in all of them with bbolt work? I don't know myself, but some upstream think it's not a trivial change. For example, see: https://github.com/hashicorp/raft-boltdb/pull/19#issuecomment-703732437 In short: hashicorp-raft-boltdb wants to make sure there's no is

Bug#979546: docker.io: version in Bullseye does not support "rootless mode", makes privilege escalation trivial

Hi Chris, I believe what you refer to is a well-known issue with docker. I have this reference from Apr. 2015: https://fosterelli.co/privilege-escalation-via-docker.html This is how docker works. The most easy mitigation is NOT to add a user to the docker group. This way, you will always invoke d

Bug#971789: FTBFS: Could not determine section for ./.gopath/src/github.com/docker/cli/man/man1/docker-attach.1

I could solve the issue by patching spf13/cobra as suggested by Tianon. See [1] for the patch. I just uploaded the package. Since docker.io has to embed spf13/cobra, I could patch it there. But if other packages in Debian have the same issue, then maybe this patch should be applied to golang-githu

Bug#969227: FTBFS with new runc 1.0.0~rc92 and libcap2 2.43

The patch test--fix-against-libcap2-2.43.patch actually fails the build for me, in a sid chroot with libcap 2.43. === RUN TestTarUntarWithXattr archive_unix_test.go:267: assertion failed: string "/tmp/docker-test-untar-origin293876876/2 = cap_block_suspend+ep\n" does not contain "cap_bl