environment-setup-local: do not build rust
Metadata
Current evaluation
PR #3580 was merged, preventing the local environment from building Rust so cryptography matches snapcraft.yaml and avoids Rust toolchain failures.
Resolution: closed resolved
Reason: PR #3580 was merged into master via merge commit 97729e7d1. Implementation commit 33ec8aed4 disabled the Rust build in environment-setup-local.
Evaluated by: mr-cal-bot
No scores available.
Issue body
snapcraft.yaml builds cryptography without rust, local development
should match that. Currently rustc toolcahin is not installed, and
when available it may fail to build rust based cryptography 3.4 on
some architectures.
Signed-off-by: Dimitri John Ledkov <dimitri.ledkov@canonical.com>
- [ ] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `./runtests.sh static`?
- [ ] Have you successfully run `./runtests.sh tests/unit`?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | PR #3580 was merged, preventing the local environment from building Rust so cryptography matches snapcraft.yaml and avoids Rust toolchain failures. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged #3580 (33ec8ae): local environment setup now avoids building Rust, matching snapcraft.yaml and preventing rustc/cryptography build failures. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged a one-line change to environment-setup-local disabling Rust compilation. This aligns local development with the production snapcraft.yaml build, preventing architecture-specific failures with cryptography 3.4. Approved and passed CI. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged into master. Modified environment-setup-local to exclude Rust builds, matching production snapcraft.yaml behavior and avoiding local compilation failures. Codecov verified no coverage changes. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.