When building the arch-independent snap, don't pip install binaries #182
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
Adjust snapcraft.yaml to avoid installing binaries with pip for the arch-independent snap.
Resolved issues
Snap publication was previously failing in the new github action due to this error:
Basically we were pulling binaries for some things like cpython. However we don't really need those binaries for it to run correctly. We can prevent this through some extra pip options, which are now set in the build-environment section of the snapcraft yaml.
Documentation
n/a
Tests
I forced the action to run against this branch and the snap built and published - https://canonical.greenhouse.io/scorecards/75984869