Upgrade to bazel 9

[Databean]

Bug: b/477396584

[dwhea]

Could you share a workaround while this support isn't yet merged? Build and install is failing with error after the install script earlier fetched bazel 9.0.0.

Building packages
dpkg-buildpackage -us -uc -ui -i -b
dpkg-buildpackage: info: source package cuttlefish-common
dpkg-buildpackage: info: source version 1.38.0
dpkg-buildpackage: info: source distribution stable
dpkg-buildpackage: info: source changed by Sergio Rodriguez <sorama@google.com>
dpkg-source -i --before-build .
dpkg-buildpackage: info: host architecture amd64
dpkg-source: warning: unknown information field 'Build-Depends' in input data in package's section of control info file
debian/rules clean
cat: bazel-bin/build/compilation_mode.txt: No such file or directory
debian/rules:18: *** Bazel install is broken. Stop.
dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -i -b failed

[dwhea]

Could you share a workaround while this support isn't yet merged? Build and install is failing with error after the install script earlier fetched bazel 9.0.0.

Building packages dpkg-buildpackage -us -uc -ui -i -b dpkg-buildpackage: info: source package cuttlefish-common dpkg-buildpackage: info: source version 1.38.0 dpkg-buildpackage: info: source distribution stable dpkg-buildpackage: info: source changed by Sergio Rodriguez <sorama@google.com> dpkg-source -i --before-build . dpkg-buildpackage: info: host architecture amd64 dpkg-source: warning: unknown information field 'Build-Depends' in input data in package's section of control info file debian/rules clean cat: bazel-bin/build/compilation_mode.txt: No such file or directory debian/rules:18: *** Bazel install is broken. Stop. dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2 debuild: fatal error at line 1182: dpkg-buildpackage -us -uc -ui -i -b failed

OK, having bazel (8.x) installed already on the system is good enough to avoid this problem.

[Databean]

The workaround we used for this was to pin to bazel 8 and start slowly migrating targets to be ready for bazel 9, with presubmit enforcement.