-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rules_* modules broken with Bazel 8.0.0rc8 #3260
Comments
Upgrade to https://github.com/fmeum/with_cfg.bzl/releases/tag/v0.6.0 to fix `Error: 'struct' value has no field or method 'AppleDebugOutputs'` and work towards bazelbuild/bazel-central-registry#3260
Addressing bazelbuild/bazel-central-registry#3260
FYI: |
Upgrade `with_cfg.bzl` to https://github.com/fmeum/with_cfg.bzl/releases/tag/v0.6.0 to fix `Error: 'struct' value has no field or method 'AppleDebugOutputs'` in https://buildkite.com/bazel/bcr-bazel-compatibility-test/builds/72#019367bc-a37c-4ae9-acf2-4a0ccdfdf8c9 and work towards bazelbuild/bazel-central-registry#3260
This should unblock bazelbuild/bazel-central-registry#3260
This should unblock bazelbuild/bazel-central-registry#3260
This should unblock bazelbuild/bazel-central-registry#3260
|
Filed bazelbuild/bazel#24499 to discuss a better solution, but was able to just duplicate some data as a workaround. The breaking change stems from bazelbuild/bazel@27487cf which causes the patch tool for |
rules_jni@0.10.3 contains a fix. @ouillie Can you use |
It looks like all of these breakages are caused by Once these build failures are addressed on the |
@EdSchouten Yes, jsonnet is also identified in #3056 |
rules_sh, rules_nixpkgs and rules_haskell all fail with the same error:
We were relying on this macro, but apparently it has been removed and the one in rules_cc is private. We are going to vendor a copy of this macro into our rules to solve this, but maybe others are also having this issue and copying this code around seems not very maintainable. WDYT? |
Copybara Import from #283 BEGIN_PUBLIC Expose get_cpu_value in toolchain_config_utils.bzl (#283) Addressing bazelbuild/bazel-central-registry#3260 (comment) Closes #283 END_PUBLIC COPYBARA_INTEGRATE_REVIEW=#283 from bazelbuild:meteorcloudy-patch-5 8d7f986 PiperOrigin-RevId: 700977422 Change-Id: I979446d5d79d8da465ec538632326d6d2c6932f7
rules_flex fix: #3285 |
rules_Synology will take a few days to fix: I butchered the bcr template and I’m afk 3 days. I can’t reproduce the failure but have a fix for a guess of the cause into v0.0.3 |
After some templating issues, #3330 brings in v0.1.1 (via chickenandpork/rules_synology#176) which might have a fix for update 2025-02-21
|
@meteorcloudy can we pass |
…f bazel version is overridden (#2140) Address: bazelbuild/bazel-central-registry#3260 (comment)
@keith |
@meteorcloudy what would be a procedure to remove rules_poetry@0.3.6 from this check? I don't plan to add support for Bazel >=8 to the package |
@oxidase You can simplify ignore this notification for now? Those kind of issues won't be filed too frequently. |
These issues for rules_android should be fixed now with the v0.6.0 release. |
rules_elm should be fixed starting from v1.1.0 |
The following modules are broken with Bazel@8.0.0rc8 (Updated Dec 9):
BCR Bazel Compatibility Test: https://buildkite.com/bazel/bcr-bazel-compatibility-test/builds/103
rules_android@0.5.1
Maintainers: @ted-xie, @ahumesky
rules_android_ndk@0.1.2
Maintainers: @bazelbuild/bcr-maintainers
rules_appimage@1.16.2
Maintainers: @lalten
rules_apple_linker@0.5.1
Maintainers: @keith
rules_buf@0.3.0
Maintainers: @srikrsna-buf
rules_directory@0.0.2
Maintainers: @matts1
rules_elm@1.0.1
Maintainers: @kczulko
rules_erlang@3.16.0
Maintainers: @pjk25
rules_graalvm@0.11.1
Maintainers: @sgammon
rules_haskell@1.0
Maintainers: @avdv, @aherrmann
rules_ios@5.3.0
Maintainers: @luispadron
rules_jsonnet@0.6.0
Maintainers: @EdSchouten
rules_kotlin@2.0.0
Maintainers: @Bencodes, @restingbull, @nkoroste
rules_nixpkgs_core@0.12.0
Maintainers: @benradf, @aherrmann
rules_oci@2.0.1
Maintainers: @alexeagle, @thesayyn
rules_pact@1.1.9
Maintainers: @opicaud
rules_poetry@0.3.6
Maintainers: @oxidase
rules_proto_grpc_c@5.0.1
Maintainers: @aaliddell
rules_pycross@0.6.1
Maintainers: @jvolkman
rules_sh@0.5.0
Maintainers: @avdv, @aherrmann
rules_shtk@1.7.0
Maintainers: @jmmv
rules_swift_package_manager@0.41.0
Maintainers: @cgrindel
rules_synology@0.1.1
Maintainers: @chickenandpork
rules_zig@0.6.0
Maintainers: @aherrmann
The text was updated successfully, but these errors were encountered: