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

fix(charm_builder): force-install pip #1892

Merged
merged 1 commit into from
Sep 12, 2024
Merged

Conversation

lengau
Copy link
Collaborator

@lengau lengau commented Sep 11, 2024

The previous version wasn't installing pip if it was already in the venv.

This is the hotfix for 3.x, while #1891 is the hotfix for 2.x.

Fixes #1456
CRAFT-2538

The previous version wasn't installing pip if it was already in the venv

Fixes #1456
CRAFT-2538
@lengau lengau requested review from mr-cal and mattculler September 11, 2024 15:19
@lengau lengau marked this pull request as ready for review September 11, 2024 15:19
Copy link
Contributor

@mattculler mattculler left a comment

Choose a reason for hiding this comment

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

Why do we always need to reinstall pip?

@lengau
Copy link
Collaborator Author

lengau commented Sep 12, 2024

@mattculler we only need to do so if the version of pip that's added in the venv is older than the minimum version that supports our needed feature set (as is the case on focal, for example). But we're checking the pip version before running that command.

@lengau lengau merged commit 358657b into hotfix/3.2 Sep 12, 2024
20 checks passed
@lengau lengau deleted the work/1456/install-pip branch September 12, 2024 16:52
lengau added a commit that referenced this pull request Sep 12, 2024
The previous version wasn't installing pip if it was already in the
venv.

This is the hotfix for 2.x, while
#1892 is the hotfix for 3.x

Fixes #1456
CRAFT-2538
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.

3 participants