prime error: unable to set version: it was already set in the 'build' step
Metadata
Current evaluation
snapcraft prime fails with 'Unable to set version: it was already set in the build step' when a custom patch sets the version during build. 7 years old, 0 comments, no maintainer interaction. The error string no longer exists in current code.
Suggested action: close stale
Reason: The issue is 2650 days old with zero comments and no maintainer interaction. The exact error string 'it was already set in the' no longer appears anywhere in the current codebase (grep returns no matches), and the version-setting logic has been substantially rewritten (snapcraftctl set-version #2063, craft-application adoption #4560, update_metadata.py now guards with 'if metadata.version and not project.version'). The reporter was using a custom patch to trigger 'new' snapcraft, so the report is tied to a transitional/legacy code path that no longer exists. The reporter never provided the paste content inline or responded to any follow-up, so there is no actionable, reproducible bug remaining in the current codebase.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
14.0
Staleness:
95
Complexity:
30
Confidence:
60
Support Request:
55
|
close stale | snapcraft prime fails with 'Unable to set version: it was already set in the build step' when a custom patch sets the version during build. 7 years old, 0 comments, no maintainer interaction. The error string no longer exists in current code. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
25
Confidence:
85
Support Request:
65
|
close stale | User reports a snapcraft version conflict error during the prime step after applying a custom patch. Issue is 7 years old with no maintainer interaction or comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
25
Confidence:
90
Support Request:
10
|
close stale | Snapcraft prime fails with version conflict during build. No maintainer response or labels after 7 years. Likely obsolete due to snapcraft evolution. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
20
|
close stale | Reports snapcraft prime failure when version is already set in build step. Issue remains untriaged after 7 years with no maintainer comments or activity. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
85
Support Request:
25
|
close stale | snapcraft prime fails with a version already set error during Multipass builds using the new snapcraft. The report remains open with no comments or updates in over three years. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
snapcraft#2063
(confidence 45%)
many: add snapcraftctl set-version (#2063) introduced the modern version-setting path; the old 'already set in the build step' error path was removed in the rewrite. Inferred from code archaeology, not an explicit cross-reference.
-
Related To:
snapcraft#4560
(confidence 40%)
feat(craft-application): initial support (#4560) rewrote metadata update logic; update_metadata.py now only sets version when not already set, eliminating the reported conflict. Inferred from code archaeology.
Related issues
No related issues found above the similarity threshold.