Laurenz
Laurenz
@mvukov should we land #443 #444 #445 and #446?
https://github.com/bazel-contrib/rules_jvm_external?tab=readme-ov-file#prerequisites claims compatibility with Bazel 6 which can't be true given https://github.com/bazel-contrib/rules_jvm_external/blob/a1d4e4f4267c1797b686719aa385e707b732c541/MODULE.bazel#L105 so that's probably their bug
looks like this isn't the first time people stumble over that: https://github.com/bazel-contrib/rules_jvm_external/issues/1055 :)
But actually the bazel_compatibility is set to `[">=7.0.0"]` in rules_jvm_external 6.3: https://github.com/bazel-contrib/rules_jvm_external/blob/2deeda518cf1ccb847c6e188bb3bf7d3f6fb7496/MODULE.bazel#L1-L5 so I'm not sure how Bazel picked up this dependency in the first place 🤔
Fixed in https://github.com/bazelbuild/bazel/pull/22257
In my case I'm calling zsyncmake2 from a Bazel run target. Path setups are kind of important in the Bazel world. Currently, every invocation of running zsyncmake2 will clutter up...
That would be not ideal (because I still need to write logic around the call to calculate what the output filename will be so it can be used elsewhere afterwards)...
@bazel-io skip_check unstable_url
@wep21 please have a look :)
It seems to be related to https://github.com/indygreg/python-build-standalone/pull/326. rules_appimage uses Python 3.13 by default.