-
Notifications
You must be signed in to change notification settings - Fork 821
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
Fix pip-managed ansible on pip < 23.0.1 #4403
Conversation
b635abb
to
85fe9cf
Compare
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.
Hey @holmanb what o you think about an alternative approach to only append --break-system-packages if that EXTERNALLY-MANAGED marker file is present? This would work on all flavors of Ubuntu back to focal as we'd avoid adding the param unless the distro itself implements the PEP668 marker.
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.
Ran through jammy, focal and mantic with the suggested changeset.
Co-authored-by: Chad Smith <chad.smith@canonical.com>
Thanks for the review @blackboxsw. Fixed according to your comment. |
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.
LGTM!
Commit b417b21 broke pip-managed ansible with pip < 23.0.1 and fixed pip-managed ansible with pip >= 23.0.1. Gate the change by a filesystem artifact only found on newer pip versions.
Additional Context
https://jenkins.canonical.com/server-team/view/cloud-init/job/cloud-init-integration-focal-lxd_vm/303/testReport/junit/tests.integration_tests.modules/test_ansible/test_ansible_controller/