Source: bazel-bootstrap
Version: 4.2.3+ds-9
Severity: minor
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build
User: [email protected]
Usertags: qa-doublebuild

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:
> Building Bazel with Bazel.
> .OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> Loading: 
> 
Loading: 0 packages loaded
> 
ERROR: no 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.
> Loading: 0 packages loaded
> 
INFO: Elapsed time: 1.043s
> Loading: 0 packages loaded
> 
INFO: 0 processes.
> Loading: 0 packages loaded
> 
FAILED: Build did NOT complete successfully (0 packages 
loaded)
> 
FAILED: Build did NOT complete successfully (0 packages 
loaded)
> 
> ERROR: Could not build Bazel
> make[1]: *** [debian/rules:67: override_dh_auto_build] Error 1
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> make: *** [debian/rules:63: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
> 2
> 
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage 
> --sanitize-env -us -uc -rfakeroot -b' failed to run.


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.

Reply via email to