-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Fresh install has hash errors for python-logstash on Arm based os #1191
Comments
@jmurrayufo would you mind posting the lockfile that your system is generating? |
Pipfile.lock from my 'real world' case
And the limited case (just targeting smbus2 and python-logstash)
Fixing the hash in the lockfile does result in correct behavior, so it seems there is a problem generating this hash? |
Ok, I didn't catch this before. You're using a wheel distributed by a 3rd party packaging server. I don't know if we have support for that right now because we only have a way to retrieve hashes from PyPI. Is there something specific about the 3rd party wheel you need for the Raspberry Pi, or would the standard distribution work? |
Forgive my ignorance here, but I am just using what gets defaultly setup? At no point have I attempted to point anything my toolchain anywhere different. Is there a way to ask pipenv to install from the default packaging servers? |
No problem, there's a lot of machinery working in the background of both pip and pipenv. If you look at the original log you provided, you'll see the line: This isn't one of the official pypi servers, so perhaps Raspberry Pi is adding this with their python build? Either way, there's a few ways to get around this. The first is to try clearing the cache with If the above doesn't work, you can either use |
Trying the suggestions now.
Using For my own purposes, I'm happy with just using this to deploy to my set of Pis. I would love to have a similar flag for Thank you so much for the support in getting me running again! |
The raspbian distribution adds a '/etc/pip.conf' file with an extra source, piwheels: piwheels/piwheels#47 |
Installing python-logstash and smbus2 from pipenv on a Raspberry Pi results in errors that seem to be related to Pipenv's hashing?
Describe your environment
Expected result
Virtualenv install of python-logstash and smbus2
Actual result
Sample run of actual development Pipfile
Of note, only these two packages seem to have this error. I am unsure as to why this is (not really knowing enough about the pip system in general to see how they might be different).
Reducing the Pipfile to just smbus2 and python-logstash as follows:
Test Pipfile
Resulting Error
Results seem the same if using
pipenv install
on a fresh OS, and git checkout, or when usingpipenv update
otherwise. Doing a pip3 install of the packages succeeds, but sort of removes the utility of pipenv.Steps to replicate
pipenv --python 3.6
pipenv install python-logstash smbus2
(This will succeed, and simulates the creation of the git downloaded Pipfile. Note: I am not using git to push the Pipfile.lock at this time.)pipenv update
(This will fail with the following)The text was updated successfully, but these errors were encountered: