Use pip version 18.1 #3866
Open
Use pip version 18.1 #3866
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR reverts the pip version from 19.0.x to 18.1 for the source installation of Agent v5.32, in hopes of fixing a Backend Unavailable error that is present on some machines.
Motivation
In trying to install the source agent on a Raspberry Pi Zero W I ran into a pep517 error: "Backend Unavailable." This error led me to this pip github issue stating that this issue is not present in version 18.1 of pip: pypa/pip#6164
I puled down the dd-agent repo and changed the pip version in setup_agent.sh locally, which allowed the completion of the download, though the agent is still non-functional on the Pi Zero W.
My hope is that using pip 18.1 will allow the source installation to complete on a wider range of machines.
Additional Notes
This PR is untested at this time, and should not be merged until we're able to test this. I'm not sure of how we might go about testing this PR out, and would be happy to sit with someone who can guide me on how to best test this PR to make sure it doesn't break installations on supported machines.