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
64-bit install failing #5
Comments
Good snooping. I'll spin up a 64bit image tomorrow and see if I can track this back to a sensible resolution. I'm open to just detecting the OS version and working from that if we can't figure out what's going on. |
I mean it might just make sense to add some arch if statements to add the necessary files for running the 32-bit compiled version on a 64-bit OS. Also, is the Pipfile generated automatically or manually? I searched through the repo and the only reference I found to cairo is in the comments of the crypto plugin, but it doesn't seem to actually be used anywhere. I haven't done an exhaustive search, but if it's not required, and causing issues, the simple solution might be to remove the dependency |
It's a hidden dependency of pygal in the crypto plugin. Took me forever to figure that out. The requirements.txt are generated programmatically. The eventual goal is to have a plugin installer that uses the requirements. Then plugins can be installed on demand and live in their own repos rather than being baked in to paper pi. |
I wondered if it wasn't something like that. That makes sense. A plugin installer would be slick. I'll keep an eye out for similar solutions. |
I'm trying out the "milestones" feature in Github to to try to add some order to the project. I have a lot of ideas about what I'd like this version to be able to do and I really need to document it out in some sensible way. |
Might also be a good chance to start using the projects tab on GitHub. I'm pretty sure it auto-imports issues and PRs and can be organized into goals (maybe even using the existing milestones) in a task tracking manner |
I looked at that this morning, but wasn't quite sure the purpose. I'll look again. Thanks for the tip. |
I think it could be used to track progress on an issue or PR. Like needs investigating, being worked on, waiting on something, etc. Here's an example of it being used in full (probably overkill for this repo), but good to see how it could be used. |
@aaronr8684
I was distracted and missed the error messages. I added the Crypto plugin and started it up and everything started as expected. This may solve one problem while presenting us with another in its place.
|
Yea I was playing around with that as well and it seems that But to your bigger point, we should handle errors somehow. I don't know the best way to do this. If the script will work anyway, we don't want to fail the whole install for a non-critical failure (especially for a single plugin). |
Good point. My shell-scripting-FU is pretty weak when it comes to this sort of thing. We might just want to see if we can detect errors and then alert the user that "some plugins might not work..." or something like that. I've verified that removing pycairo solves this. |
Ok, I'll test a reinstall on my 64-bit as well. |
64-bit test was successful. Also, for future reference, I did a
|
Same as the issue #48. 32-bit (Bullseye) works fine, but in the 64-bit version, something in the PyCairo dependency is causing the script to fail.
I think the quick and dirty fix would be to check if the OS is 64-bit and the PyCairo dependency is listed in the Pipfile. If it is, just do a quick
sudo apt install pycairo2-dev
Alternatively, we could try to track down what is failing or why and see if their is a cleaner fix. There seems to be hint at PATH variables and obsolete installation methods, but a quick search doesn't turn up much.
pipenv install pycairo
ouput:The text was updated successfully, but these errors were encountered: