bazelbuild / bazelbuild/rules_pkg

Unable to find package for @rules_python_internal//:rules_python_config.bzl: The repository '@rules_python_internal' could not be resolved: Repository '@rules_python_internal' is not defined.

Open
#872 7 comments 0 reactions 0 assignees View on GitHub
p4 question
Dominant language
Starlark
Stars
253
Forks
221
Avg merge
10h 33m
Merged PRs (30d)
1

Description

WORKSPACE:
```
http_archive(
name = "rules_pkg",
sha256 = "d250924a2ecc5176808fc4c25d5cf5e9e79e6346d79d5ab1c493e289e722d1d0",
urls = [
"https://github.com/bazelbuild/rules_pkg/releases/download/0.10.1/rules_pkg-0.10.1.tar.gz",
],
)

load("@rules_pkg//:deps.bzl", "rules_pkg_dependencies")
rules_pkg_dependencies()
```

//src/bootstrap/cloud/BUILD:
```
...

pkg_tar(
name = "files",
srcs = [
"//:config.sh.tmpl",
"//src/bootstrap/cloud/terraform",
],
mode = "644",
strip_prefix = "/",
)
```

Error:
```
bazel test //...
Starting local Bazel server and connecting to it...
INFO: Streaming build results to:
ERROR: Analysis of target '//src/bootstrap/cloud:files' 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: at /usr/local/google/home/ensonic/.cache/bazel/_bazel_ensonic/88cafc24ebbba21bc2294727bc8fc64d/external/rules_python/python/py_runtime_info.bzl:17:6: Unable to find package for @rules_python_internal//:rules_python_config.bzl: The repository '@rules_python_internal' could not be resolved: Repository '@rules_python_internal' is not defined.
```

We're not using any rules_python in the repo. This issue is blocking https://github.com/googlecloudrobotics/core/pull/373

Contributor guide

Open the contributing guide

Research direction

Start with the WORKSPACE declaration and rules_pkg_dependencies(), then inspect src/bootstrap/cloud/BUILD and reproduce the failure with bazel test //.... Trace why loading rules_pkg's dependencies requests @rules_python_internal even though the repository does not use rules_python; done means the target analyzes and the full test command proceeds without that unresolved repository error.

Written by the indexing model from the issue text.

Assessment

Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.