You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now you need to build with --noenable_bzlmod.
But, IIRC, the name of the repo is different under bzlmod, so you have to fix the build files.
Such is life.
The text was updated successfully, but these errors were encountered:
aiuto
added
the
P2
An issue that should be worked on when time is available
label
Jan 10, 2024
aiuto
changed the title
Update startdoc in MODULE.bazel so we can build with bazel 7.x in default mode
Update stardoc in MODULE.bazel so we can build with bazel 7.x in default mode
Mar 15, 2024
aiuto
added
the
P1
An issue that must be resolved. Must have an assignee
label
Apr 16, 2024
Update: April 2024. Bazel at is pretty much breaking --noenable_bzlmod. You tend to get an error like
(02:55:28) ERROR: Error computing the main repository mapping: Label '@@platforms//host:extension.bzl' is invalid because 'host' is not a package; perhaps you meant to put the colon here: '@@platforms//:host/extension.bzl'?
(02:55:28) Computing main repo mapping:
Force the integration test (stardoc and packaging) to run with bazel
7.0.0.
Bazel at head seems to have broken --noenable_bzlmod in some cases. See
#808.
This also bumps platforms to the latest, but that was a red herring from
the error message in the underlying problem
aiuto
added a commit
to aiuto/rules_pkg
that referenced
this issue
Apr 16, 2024
* Update to new stardoc so we can work with bzlmod.
* Requires update to merge.py to account for stardoc changes.
* put integration test back on bazel at head.
Fixes#808
Right now you need to build with
--noenable_bzlmod
.But, IIRC, the name of the repo is different under bzlmod, so you have to fix the build files.
Such is life.
The text was updated successfully, but these errors were encountered: