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

issue with dependency installation in install.sh #216

Closed
00h-i-r-a00 opened this issue Aug 6, 2018 · 3 comments
Closed

issue with dependency installation in install.sh #216

00h-i-r-a00 opened this issue Aug 6, 2018 · 3 comments

Comments

@00h-i-r-a00
Copy link

Hello,

I just tried to set up OpenWPM by running the install.sh script, but get this error:

Cannot uninstall 'psutil'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.

The end result of which is that all the packages listed inside requirements.txtdo not get installed. and I have to do them all manually. It seems like this is a known issue in pip post version 10 (See this and this)

I am not sure if there is a better way to get around this, but removing the -U flag from line 57 in install.sh (sudo pip install -U -r requirements.txt) seems to fix the issue. That way pip doesn't have to uninstall the older version (which it seems to have a problem with) and updating it with the newer version (thats my guess though I am not entirely sure why pip doesn't try to remove the older versions when not using the update flag).

This is technically not an issue but I thought you guys might want to know about this bug.

@00h-i-r-a00
Copy link
Author

Actually removing the -U flag seems to skip installing the psutil package altogether, and despite OpenWPM running, it may cause problems in the future, so still figuring it out.

@englehardt
Copy link
Collaborator

Does b8f23c9 fix the issue? I've switched to installing a pip package locally in the current user's home directory (~/.local/bin/), rather than use the system pip. All of the dependencies are also installed there.

That should use pip v18, which doesn't appear to have this issue.

@englehardt
Copy link
Collaborator

Closing due to inactivity. Feel free to file a new issue if you still have the same problem.

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

No branches or pull requests

2 participants