snapcraft doesn't create binary-identical reproducible builds
Metadata
Current evaluation
Feature request for byte-identical reproducible snap builds (deterministic plugin order, identical output across machines). Open ~10 years with zero comments, no labels, and no maintainer interaction.
Suggested action: needs triage
Reason: The issue has no labels, no assignee, and zero comments or maintainer responses in ~10 years (last activity 3563 days ago), showing no sign of ever being categorised or prioritised. I could not confirm via repo inspection (pinned SHA unavailable) that reproducible builds have since been implemented, so close_stale is not justified on irrelevance grounds; a maintainer needs to decide whether to pursue, scope, or decline this long-standing feature request.
Impact:
35
Quick Win:
8.75
Staleness:
95
Complexity:
75
Confidence:
65
Support Request:
15
Issue body
It would be nice if plugins were run in a deterministic order and two very different machines with identical snapcraft.yaml files would make a byte-for-byte identical snap package.
Reproducible builds would be a great selling-point.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
8.75
Staleness:
95
Complexity:
75
Confidence:
65
Support Request:
15
|
needs triage | Feature request for byte-identical reproducible snap builds (deterministic plugin order, identical output across machines). Open ~10 years with zero comments, no labels, and no maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
99
Complexity:
80
Confidence:
95
Support Request:
5
|
close stale | Feature request for deterministic, byte-for-byte reproducible snap builds. Unaddressed for over nine years with zero maintainer interaction or labels. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
45
Confidence:
85
Support Request:
10
|
close stale | Feature request for deterministic plugin execution to achieve byte-for-byte reproducible snap builds. Unaddressed for over 9 years with zero comments, labels, or maintainer interaction. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
75
Confidence:
90
Support Request:
10
|
close stale | Feature request for deterministic plugin execution and byte-for-byte reproducible snap builds. Unlabelled, zero maintainer interaction, inactive for over a decade. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
75
Confidence:
75
Support Request:
10
|
close stale | Requests deterministic plugin execution and byte-for-byte identical snap builds from identical snapcraft.yaml files. Open, unlabelled, and inactive for nearly ten years with zero comments. Needs triage or implementation to enable reproducible builds. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1793471 snapcraft trggers unnecessary pulls from unrelated file modifications | snapcraft (launchpad) | open | Feature request to add .snapignore support so IDE and .git changes stop marking snapcraft stages stale and triggering unnecessary re-pulls/rebuilds. Open since 2018 with label 18.10-build-caching, zero comments, no maintainer engagement for ~8 years. |