-
Notifications
You must be signed in to change notification settings - Fork 75
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
Closed Issue: revert to using pip for ansible on 32bit RasPiOS [& ongoing issues w/ wheels, cryptography, rust] #3459
Conversation
ASIDE: RasPiOS will probably fix its 32-bit problems in coming months if not in coming weeks. Background here: |
Screenshot just for the record: Recap: This PR uses |
FWIW / FYI
Tangentially related: |
The latest colorful chart at https://www.piwheels.org/project/cryptography/ suggests IIAB should probably... transition from |
Just remove the pinned versioning now that the upstream rust tool chain is corrected. |
Definitely. Or perhaps eliminate it entirely — e.g. if the PR below was tested on 32-bit RasPiOS to not need |
About 6 months later, Raspberry Pi OS and Debian issues with {cryptography, rust, piwheels} appear to now all be thankfully resolved:
|
2 bits of bad news just for the record:
|
Debian-10 is unsupported so why mention it and just pin the version if need be, I showed you how to do that. Not the fault of this project that the wheel is unavailable could install the rust toolchain and build the package from scratch but would add greatly to the install time.
Told you the switch to the arm64 kernel is going to hurt a pile of workflows |
Just FYI 2 new piwheels releases (41.0.0 and 41.0.1) failed ~10 days ago: |
Fixes bug:
Stops polluting /etc/apt/sources.list.d/ and /usr/share/keyrings/ with files that are never used to install ansible while using "pip3 install". ie Ubuntu and RasPiOS-64bit
Description of changes proposed in this pull request:
Restores "pip3 install" for RasPiOS-32-bit
Smoke-tested on which OS or OS's:
Ref: Slimmed down version of #3456