Skip to content

chore: remove pkginfo from bzlmod file #778

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

Merged
merged 1 commit into from
Aug 4, 2022
Merged

chore: remove pkginfo from bzlmod file #778

merged 1 commit into from
Aug 4, 2022

Conversation

alexeagle
Copy link
Contributor

Under bazel 5 this unused entry is okay, but with Bazel 6 you get an error

ERROR: Analysis of target '//:bzlmod' failed; build aborted: module extension "pip_install" from "@@rules_python~override//python:extensions.bzl" does not generate repository "pypi__pkginfo", yet it is imported as "pypi__pkginfo" in the usage at rules_python@_/MODULE.bazel:7:28

This was detected on BCR which runs against latest bazel, so I had to
make this change there already:
bazelbuild/bazel-central-registry@6e1bf0e#diff-d133485c86e1650c9910643274be2051f2c714042c59de22b4c3fd6e546bd93c

Under bazel 5 this unused entry is okay, but with Bazel 6 you get an error

ERROR: Analysis of target '//:bzlmod' failed; build aborted: module extension "pip_install" from "@@rules_python~override//python:extensions.bzl" does not generate repository "pypi__pkginfo", yet it is imported as "pypi__pkginfo" in the usage at rules_python@_/MODULE.bazel:7:28

This was detected on BCR which runs against latest bazel, so I had to
make this change there already:
bazelbuild/bazel-central-registry@6e1bf0e#diff-d133485c86e1650c9910643274be2051f2c714042c59de22b4c3fd6e546bd93c
Copy link
Collaborator

@groodt groodt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@groodt groodt merged commit 8048ff7 into main Aug 4, 2022
@groodt groodt deleted the unused branch August 4, 2022 06:36
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