prime error: unable to set version: it was already set in the 'build' step
Metadata
Current evaluation
A reproducible core22 lifecycle-ordering failure could set the snap version twice; it is covered by a regression test and addressed by the craft-parts 1.19.7 update.
Suggested action: close resolved
Reason: The March 2023 comment provides an exact core22 reproducer involving dirty-part reordering. Commit 24e430d05 (#4305) updates craft-parts to 1.19.7, while tests/spread/core22/set-version-twice explicitly cites this bug and verifies that version is not set twice.
Evaluated by: mr-cal-bot
Impact:
45
Quick Win:
22
Complexity:
48
Confidence:
93
Actionability:
95
Issue body
Trying to build Multipass with the following patch: http://paste.ubuntu.com/p/PzMKxvpw2m/ to trigger "new" snapcraft.
Having built, trying to `snapcraft prime` I end up with:
Unable to set version: it was already set in the 'build' step.
Failed to run 'override-build': Exit code was 2.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
22
Complexity:
48
Confidence:
93
Actionability:
95
|
close resolved | A reproducible core22 lifecycle-ordering failure could set the snap version twice; it is covered by a regression test and addressed by the craft-parts 1.19.7 update. | |
| stealth/space-bunny-alpha |
Impact:
48
Quick Win:
13
Complexity:
67
Confidence:
84
Actionability:
82
|
close resolved | The core22/core24 version-setting failure is covered by regression tests after craft-parts 1.19.7; the original core20 report remains unreproduced on a now-unsupported base. | |
| qwen/qwen3.6-35b-a3b |
Impact:
10
Quick Win:
8
Complexity:
10
Confidence:
90
Actionability:
90
|
close resolved | snapcraft prime fails with 'Unable to set version: it was already set in the build step' when version is set during build. The error string no longer exists in the codebase; the bug was fixed in craft-parts. | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
14
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. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcraft#4305
(confidence 95%)
The craft-parts 1.19.7 update is associated with regression coverage for the exact core22 lifecycle-ordering reproducer.
Related issues
No related issues found above the similarity threshold.