remote-build `version: git` resolved too late
Metadata
Current evaluation
Remote-build preserves clean Git history, but auto-commits dirty trees before resolving version: git, yielding a different SHA-dirty version; warning versus pre-resolution remains undecided.
Suggested action: keep open
Reason: The reporter confirmed on 2024-01-25 that the new remote builder preserves clean history but auto-commits dirty trees, producing a version different from a local build. The maintainer listed warning, error, and no-auto-commit options, and said the best path still needed to be determined; no matching fixing commit was found.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
50
Quick Win:
15
Complexity:
55
Confidence:
84
Actionability:
68
|
keep open | Remote-build preserves clean Git history, but auto-commits dirty trees before resolving version: git, yielding a different SHA-dirty version; warning versus pre-resolution remains undecided. | |
| stealth/space-bunny-alpha |
Impact:
46
Quick Win:
14
Complexity:
52
Confidence:
91
Actionability:
62
|
keep open | Remote-build preserves clean Git history, but auto-commits dirty trees before `version: git` resolves, yielding `<SHA>-dirty`; the desired warning or pre-resolution behavior remains undecided. | |
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
11
Complexity:
48
Confidence:
92
Actionability:
55
|
needs triage | Remote builds resolve version: git after source mangling, so Launchpad records the temporary repository's SHA instead of the original project's; the report remains untriaged. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
55
Quick Win:
30
Staleness:
85
Complexity:
45
Confidence:
65
Support Request:
25
|
needs triage | Remote-build with version: git resolves SHA from mangled source instead of original. Untriaged, 955 days old, no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
60
Confidence:
80
Support Request:
5
|
close stale | remote-build with version: git resolves the commit SHA after source mangling instead of the original. Untriaged, zero comments, inactive for ~2.5 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
50
Confidence:
75
Support Request:
10
|
needs triage | remote-build with version: git resolves the commit SHA after source mangling, causing incorrect versioning. The issue has remained unlabelled and without maintainer interaction for over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
50
Confidence:
75
Support Request:
10
|
needs triage | remote-build with version: git resolves the SHA after source mangling, causing incorrect version strings. Untriaged, no maintainer comments, inactive for ~2.5 years. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1973199
(confidence 100%)
Explicitly cited by this issue; the older missing-tags problem was fixed in Snapcraft 8.0.0, but the dirty-tree auto-commit behavior remains distinct.
Related issues
No related issues found above the similarity threshold.