A lot of Bazel bugs were just left to rot, even though they are invalid.
There are work from users to get Bazel to a reasonable state, see:
https://bugs.gentoo.org/918703 (plus comment #1)

> # Unmasking this requires a sign-off from QA and treecleaners, since
> # these packages require a ton of mental bandwidth to keep up to date

I would urge to reconsider leaving Bazel out of this; I do not think 
that one is lost for now. Since I sometimes use Bazel myself, I will 
work on adding a bazel-bin + virtual.

I will NOT however use/support Bazel for Gentoo packages nor eclasses.

On 18.01.2024 13:53, David Seifert wrote:
> # David Seifert <soap@gentoo.org> (2024-01-18)
> # Unmaintained set of packages. Overall, TensorFlow is ill-suited for
> # distro packaging, since it's entangled with tons of googleware and
> # continually breaks on minor dependency updates coupled with a
> # byzantine build system. These 5 packages together have a total of
> # 54 bugs reported against them, with zero activity from the maintainer.
> #
> # Unmasking this requires a sign-off from QA and treecleaners, since
> # these packages require a ton of mental bandwidth to keep up to date
> # and Google's general unwillingness to take community input quickly
> # leads to maintainer burnout.
> # Use sci-libs/pytorch as a modern alternative with better packaging.
> # Removal on 2024-02-17. Bug #922374
> dev-build/bazel
> sci-libs/keras
> sci-libs/tensorflow
> sci-libs/tensorflow-estimator
> sci-visualization/tensorboard
> 

-- 
Have a great day!

~ Maciej XGQT Barć

xgqt@gentoo.org
Gentoo Linux developer
(dotnet, emacs, math, ml, nim, scheme, sci)
https://wiki.gentoo.org/wiki/User:Xgqt
9B0A 4C5D 02A3 B43C 9D6F D6B1 14D7 4A1F 43A6 AC3C