New git commits don't mark pull step dirty
Metadata
Current evaluation
Snapcraft skips the pull step for git-source parts after new commits, using stale source. Reported 9 years ago with clear repro; no labels, comments, or maintainer interaction since.
Suggested action: needs triage
Reason: The issue has zero labels, zero comments, and no maintainer interaction in 3336 days, showing no sign of ever being triaged. The related Launchpad bug #1704103 remains open, so the underlying problem may still be relevant to the current craft-parts-based codebase, but no one has assessed whether it persists or was fixed during the architectural transition.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
55
Quick Win:
30.25
Staleness:
95
Complexity:
45
Confidence:
55
Support Request:
10
|
needs triage | Snapcraft skips the pull step for git-source parts after new commits, using stale source. Reported 9 years ago with clear repro; no labels, comments, or maintainer interaction since. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
10
|
close stale | Snapcraft incorrectly skips the pull step after new git commits are made, failing to invalidate the build cache. The issue has been inactive for nearly 9 years with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
25
Confidence:
85
Support Request:
5
|
close stale | Snapcraft git source dirty state detection fails to trigger pull step after new commits. Issue is 9 years old with no maintainer response or comments. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
45
Confidence:
85
Support Request:
5
|
close stale | Bug report stating snapcraft skips the pull step after new git commits. Issue is 9 years old, has no comments or labels, and is likely irrelevant due to major snapcraft build system rewrites. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
40
Confidence:
90
Support Request:
5
|
close stale | Snapcraft incorrectly skips the pull step after new git commits, failing to mark it dirty. Issue remains open, unassigned, and inactive with zero comments. Requires triage and a fix to properly detect repository changes. |
Update history
No update history recorded yet.
Related work
-
Duplicate Of:
snapcraft (launchpad)#1704103
(confidence 80%)
Identical title and description; the Launchpad bug is still open with no resolution, suggesting the same underlying issue.
Related issues
No related issues found above the similarity threshold.