#929721 golang-github-gin-gonic-gin: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/gin-gonic/gin github.com/gin-gonic/gin/binding github.com/gin-gonic/gin/ginS github.com/gin-gonic/gin/json github.com/gin-gonic/gin/render returned exit code 1 #929721
- Package:
- src:golang-github-gin-gonic-gin
- Source:
- golang-github-gin-gonic-gin
- Submitter:
- Lucas Nussbaum
- Date:
- 2026-04-27 20:19:03 UTC
- Severity:
- normal
- Tags:
Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): http://qa-logs.debian.net/2019/05/29/golang-github-gin-gonic-gin_1.3.0+dfsg1-3_testing.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.
Control: severity -1 normal [...] This test needs to listen on 9999. I don't think this would be RC, so I will downgrade this bug.
From the build log it seems that the system used to build the package had an apt proxy listening on port 9999. The output of the apt commands is like: Get:1 http://127.0.0.1:9999/debian testing InRelease [163 kB] I tried a sbuild build and it passed all the tests fine. I think this is not a bug. Paride
I'm also unconvinced this is a real bug -- it builds fine in buildd/debci/salsa and locally for me. It seems the build environment used in the report had port 9999 bound to something else. We could patch the code to use port 9998 instead, but this is just a cat'n'mouse play waiting for someone else to build the package with port 9998 bound to something... we could ask upstream to improve the code to pick random ports retrying 10 times before failing, if anyone feels strongly that binding to 9999 is not permitted by test code. /Simon