← Back to issue list

rust-revision is not respected

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1654718
Type
issue
State
closed
Author
~sabdfl
Labels
Created
Updated
Closed

Current evaluation

The rust-revision parameter remained unaddressed after being reported as ignored. The report was closed without a fix or workaround.

Suggested action:

No scores available.

Issue body

snapcraft help rust suggests that I can get a particular revision of rust with the 'rust-revision' keyword. However, a snapcraft.yaml like this: rust-channel: 'nightly' rust-revision: 'nightly-2016-12-16' results in this: Downloading 'rustup.sh'[=================================================================================================================================================================================================================================] 100% /home/mark/software/snaps/alacritty-snap/parts/alacritty/rust/rustup.sh --prefix=/home/mark/software/snaps/alacritty-snap/parts/alacritty/rust --disable-sudo --save rustup: gpg available. signatures will be verified rustup: downloading manifest for 'stable'

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b The rust-revision parameter remained unaddressed after being reported as ignored. The report was closed without a fix or workaround.
qwen/qwen3.6-35b-a3b Closed without resolution or comments. The rust-revision parameter was ignored, causing snapcraft to default to the stable channel instead of the specified nightly build.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1803466 rust test errors in legacy snapcraft (launchpad) closed Closed without a documented fix. The report of two Rust test failures in the legacy branch received no comments or follow-up, indicating the issue was abandoned or resolved externally.
71%
#1655203 rust test with revision is skipped in armhf snapcraft (launchpad) closed Closed without resolution. The rust integration test remains skipped on armhf due to revision 1.13 incompatibility, requiring an armhf-compatible revision update.
70%