Closed davexroth closed 3 days ago
cc @Wyverald @tpudlik
This is WAI -- the overrides you have in WORKSPACE don't affect the Bzlmod part of the build. You'll need to add local_path_override
clauses to your MODULE.bazel file, similar to what you have in your WORKSPACE file.
So local_path_override(module_name="platforms", path="external/platforms")
etc.
This is a little un-intuitive for users upgrading from bazel 6 to 7, as by default in version 7 both enable_workspace
and enable_bzlmod
are true, which causes a working WORKSPACE to start failing on upgrade. It's also not obvious to a user why these WORKSPACE overrides are ignored while other parts of the WORKSPACE are honored in this configuration.
Description of the bug:
I have a workspace where all bazel dependencies are specified through
local_repositories
. If I run bazel with--experimental_repository_disable_download --enable_bzlmod=false
everything works. However, if I enable bzlmod, the bazel fails with the following error message:Please see the included minimal reproduction with full details.
Which category does this issue belong to?
External Dependency
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
https://github.com/davexroth/bazel_no_download_repro
Which operating system are you running Bazel on?
linux
What is the output of
bazel info release
?release 7.4.1
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD
?No response
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response