Hi,
This package fails to do build a binary-only build (not source) after a
successful build (dpkg-buildpackage ; dpkg-buildpackage -b).
This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.
More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/DoubleBuild
Relevant part of the build log:
[1A[K[32mLoading:[0m 0 packages loaded
[1A[K[31m[1mERROR: [0mno such package '@io_bazel_skydoc//': The repository's path is "io_bazel_skydoc" (absolute: "/<<PKGBUILDDIR>>/mock_repos/bazel_skydoc") but this directory does not exist.
[1A[K[32mINFO: [0mElapsed time: 1.043s
[1A[K[32mINFO: [0m0 processes.
[1A[K[31m[1mFAILED:[0m Build did NOT complete successfully (0 packages loaded)
[1A[K[31m[1mFAILED:[0m Build did NOT complete successfully (0 packages loaded)
The full build log is available from:
http://qa-logs.debian.net/2023/08/16/bazel-bootstrap_4.2.3+ds-9_unstable.log
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.