Skip to content
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

Add py_repositories() call #35

Closed
wants to merge 1 commit into from
Closed

Conversation

brenting
Copy link
Contributor

I tried compiling a dmlab2d wheel for a CentOS 7-based compute cluster and encountered an error:
ERROR: Skipping '//dmlab2d:dmlab2d_wheel': error loading package 'dmlab2d': at /root/.cache/bazel/_bazel_root/567cbe29eda1d897f010a5019ec89c95/external/rules_python/python/packaging.bzl:17:6: at /root/.cache/bazel/_bazel_root/567cbe29eda1d897f010a5019ec89c95/external/rules_python/python/py_binary.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.

This error is specifically mentioned in the unreleased Python rules CHANGELOG:
https://github.com/bazelbuild/rules_python/blob/main/CHANGELOG.md

Building dmlab2d uses the Python rules repository in its current state. I added a call to the py_repositories() as mentioned in the change log, which fixed the error.

Details:
CentOS 7
Bazel 6.3.2 (and 5.4.1)

Added a call to the py_repositories() as mentioned in the unreleased Python rules repository CHANGELOG:
https://github.com/bazelbuild/rules_python/blob/main/CHANGELOG.md
@tkoeppe
Copy link
Collaborator

tkoeppe commented Oct 4, 2023

Thanks!

@tkoeppe
Copy link
Collaborator

tkoeppe commented Oct 4, 2023

(I'll handle the other problems.)

@tkoeppe
Copy link
Collaborator

tkoeppe commented Oct 5, 2023

Merged as de0d047!

@tkoeppe tkoeppe closed this Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants