-
Notifications
You must be signed in to change notification settings - Fork 42
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-cli==0.23.0
gives pulpcore.cli.deb.context is not a package
#874
Comments
Can you confirm that this is an incompatibility between pulp-cli-deb and pulp-cli~=0.23? Is pulp-cli alone fine? |
Running |
Thanks for checking. I'm currently sorting out this exact issue with pulp-cli-gem. |
In 0.23 a regression was introduced that forced the use of `get_translation(__package__)` instead of `get_translation(__name__`). This change adds a fallback to allow the old style alongside. It may however be removed in the future. Fixes pulp#874
In 0.23 a regression was introduced that forced the use of `get_translation(__package__)` instead of `get_translation(__name__`). This change adds a fallback to allow the old style alongside. It may however be removed in the future. Fixes pulp#874
In 0.23 a regression was introduced that forced the use of `get_translation(__package__)` instead of `get_translation(__name__`). This change adds a fallback to allow the old style alongside. It may however be removed in the future. Fixes #874
Would you be so kind confirming that this is actually fixed with 0.23.2? |
Is this the same error? I'm getting this on |
No, sorry. There's nothing i can do for you. This is just bad design of pip. It recklessly breaks installed packages for the sake of satisfying your last request to *) Curiously enough, I have seen pip printing an error message about incompatible installed packages that will be broken, and still continue without asking. |
Summary
Since the release yesterday of
pulp-cli
version 0.23.0 can no longer installpulp-cli
.Steps to reproduce
In a Debian container running:
Fails with the following stacktrace:
Changing to 0.22.0 fixes this:
This can be reproduced with the following Containerfile:
The text was updated successfully, but these errors were encountered: