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

pulp file python package reporting wrongly #4724

Closed
mdellweg opened this issue Nov 15, 2023 · 0 comments · Fixed by #4723
Closed

pulp file python package reporting wrongly #4724

mdellweg opened this issue Nov 15, 2023 · 0 comments · Fixed by #4723

Comments

@mdellweg
Copy link
Member

Starting with pulpcore 3.40 the pulp_file plugins python package started reporting as pulp_file instead of pulp-file.

mdellweg added a commit to mdellweg/pulpcore that referenced this issue Nov 15, 2023
Status report of the pulp_file python_package must be pulp-file.
Technically this is still wrong, because it should be pulpcore, but we
will need another field to present the python module in order to be able
to generate the bindings.

fixes pulp#4724
@mdellweg mdellweg linked a pull request Nov 16, 2023 that will close this issue
mdellweg added a commit to mdellweg/pulpcore that referenced this issue Nov 16, 2023
Status report of the pulp_file python_package must be pulp-file.
Technically this is still wrong, because it should be pulpcore, but we
will need another field to present the python module in order to be able
to generate the bindings.

fixes pulp#4724

(cherry picked from commit 822e2be)
dralley pushed a commit that referenced this issue Nov 17, 2023
Status report of the pulp_file python_package must be pulp-file.
Technically this is still wrong, because it should be pulpcore, but we
will need another field to present the python module in order to be able
to generate the bindings.

fixes #4724

(cherry picked from commit 822e2be)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant