Stefan Sauer

So what rules_python version do you need to pkg_tar, just add it to you readme and I am happy to apply that workaround

I see the python deps from the query: https://github.com/search?q=repo%3Abazelbuild%2Frules_pkg%20rules_python&type=code

I am a bit stuck here: ``` bazel test //... INFO: Streaming build results to: https://source.cloud.google.com/results/invocations/0c41da21-59d8-4378-aa8f-cfbd06e79bbb ERROR: Analysis of target '//src/bootstrap/cloud:crc-binary' failed; build aborted: error loading package '@rules_pkg//pkg/private': at /usr/local/google/home/ensonic/.cache/bazel/_bazel_ensonic/88cafc24ebbba21bc2294727bc8fc64d/external/rules_python/python/defs.bzl:21:6:...

Looks like we need to pin python despite not using it. Some hints: https://github.com/search?q=repo%3Abazelbuild%2Frules_pkg%20rules_python&type=code

Fixed as part of the bzlmod porting in #422

We're getting `Error: could not launch profiler: Error: No python processes found in process ... or any of its subprocesses`. Sorry for not including the error in the first post....

Good to know that the error is coming from py-spy. I'll poke at it.

``` > git grep ctx.actions.run bazel/app_chart.bzl: ctx.actions.run_shell( bazel/build_rules/helm_chart.bzl: ctx.actions.run_shell( ``` @sgowroji what did you do to determine that we need a migration? I've build with `--incompatible_auto_exec_groups` and I think contrary...

@sgowroji as much as we'd like to fix it, I believe the common bazel rules need to make the first move.

> I see a commit after this - Is the migration done or do you still have some questions? I've changed it for this repo but it is hard to...