-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Update rules_pkg to 0.2.5 and use real rules_python #11191
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I think I added the stub repo because it seemed less intimidating than a real dependency. But now it seems I choose the more complicated option.
# XXXX This is a mock version of bazelbuild/rules_python that contains only | ||
# @rules_python//python:defs.bzl. It is used by protobuf. | ||
# TODO(#9029): We could potentially replace this with the real @rules_python. | ||
#new_local_repository( | ||
# name = "rules_python", | ||
# build_file = "//third_party/rules_python:BUILD", | ||
# path = "./third_party/rules_python", | ||
# workspace_file = "//third_party/rules_python:rules_python.WORKSPACE", | ||
#) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you intended to delete these lines?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. I just have not yet because I keep flipping back and forth to figure out the build error.
#new_local_repository( | ||
# name = "rules_python", | ||
# build_file = "//third_party/rules_python:BUILD", | ||
# path = "./third_party/rules_python", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems we can submit a follow-up to remove this stub repo from //third_party
. I'll draft the PR. (Can't be in this PR since we can't do third_party changes atomically with ordinary changes.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was my intent, but the failures are not transient. They reproduce locally. All of the protobufs go wonky.
No idea what the test failures are about... transient issue with unpacking third_party? |
What's the status of this PR? |
It is still a WIP blocked on #9046. That, in turn, is a WIP which turned into an overly complex project because the workspace tests should not depend on pkg_tar. |
Abandoning this line of reasoning. The tests should be rewritten to not depend on rules_pkg, and thus, transitively, rules_python. |
No description provided.