This repository was archived by the owner on Sep 8, 2024. It is now read-only.
Fixing dev_setup.sh for Arch Linux #2403
Merged
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.
Description
When you have
virtualenv
installed troughpip
in Arch Linux, the./dev_setup.sh
script does not works. The installation ofpython-virtualenvwrapper
breaks because the files already exists. The ideal solution is to fixpython-virtualenvwrapper
installation for Arch.For now, the Mycroft setup script can check if the lib is already installed and skip it.Update:
Actually, we do not need virtualenv anymore for Mycroft, the ideal solution is to remove this dependency.
This is related to "Error installing dependencies using pacman on Arch linux" #1967
How to test
Simulating the error
Create a
Dockerfile
with the following code:Try to build the Dockerfile with
docker build .
. You should see something like:Simulating the solutionCreate aDockerfile
with the following code:Try to build the Dockerfile withdocker build .
. You should see something like:The16.7.8
message shows that thevirtualenv
is instaled in the version 16.7.8.Real testing
Using an Arch Linux installation, install the
virtualenv
withpip
runningpip install virtualenv
. Try to run the./dev_setup.sh
after that. The setup should finish with success, and you should be able to start Mycroft. I have tested the solution on my machine (Manjaro Linux) and works ok.