← Back to issue list

Changed stage-snaps property does not make pull step dirty

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1824473
Type
issue
State
open
Author
~brlin
Labels
Created
Updated
Closed

Current evaluation

Snapcraft bug: changing a part's stage-snaps property does not mark the pull step dirty, so re-running stage skips pull and crashes. Reported ~7.4 years ago with a POC repo; no maintainer response, no labels, zero comments.

Suggested action: needs triage

Reason: The issue has no labels, no assignee, and zero comments — no sign a maintainer has assessed it. It is a genuine bug report with a reproduction POC (not a support request), but it is ~7.4 years old and the underlying parts logic has since moved to craft-parts, so it needs a maintainer to confirm whether it still reproduces on a current base before any close/keep decision.

Impact: 40 Quick Win: 18.0 Staleness: 95 Complexity: 55 Confidence: 55 Support Request: 5

Issue body

Bug reproduction instructions:   1. `git clone --branch=bug-stage-snaps-dirtiness https://github.com/Lin-Buo-Ren/snapcraft-bug-poc.git && cd snapcraft-bug-poc`   2. Run `snapcraft stage ccache`   3. Uncomment the commented lines in snap/snapcraft.yaml   4. Run `snapcraft stage ccache` again   Expected behavior:       Snapcraft considers ccache part's `pull` step changed and redo the pull step   Current behavior:       Snapcraft only considered ccache part's `stage` step changed, then crashed due to the stage snap isn't pull and build yet.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 40
Quick Win: 18.0
Staleness: 95
Complexity: 55
Confidence: 55
Support Request: 5
needs triage Snapcraft bug: changing a part's stage-snaps property does not mark the pull step dirty, so re-running stage skips pull and crashes. Reported ~7.4 years ago with a POC repo; no maintainer response, no labels, zero comments.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 35
Confidence: 90
Support Request: 5
close stale Bug report for Snapcraft where changing the stage-snaps property fails to mark the pull step as dirty, causing a crash. The issue has been completely inactive for over 7 years with no maintainer response.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 65
Confidence: 90
Support Request: 5
close stale Bug report for snapcraft where modifying the stage-snaps property fails to invalidate the pull step, causing a crash when the staged snap has not been pulled or built. Untriaged and inactive for over 7 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 65
Confidence: 90
Support Request: 15
close stale Modifying stage-snaps fails to mark the pull step as dirty, causing a crash. The report is over seven years old with zero maintainer interaction or labels.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 45
Confidence: 80
Support Request: 10
close stale Bug report claiming that changing stage-snaps does not invalidate the pull step, causing a crash. Issue is 7 years old, unlabelled, and has zero maintainer interaction.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1772027 Pull stage of an unspecified part is unexpectedly cleaned by snapcraft snapcraft (launchpad) closed Abandoned due to inactivity. Snapcraft incorrectly cleaned an unrelated part's pull stage during partial clean operations. No comments or resolution were provided before closure.
73%
#1663623 Changing stage-packages requires cleaning the pull stage snapcraft (launchpad) closed Closed without resolution. Snapcraft incorrectly requiring a pull stage clean after stage-packages changes was abandoned or superseded by later versions.
73%
#1921418 wrong architecture of stage-snaps when cross building snapcraft (launchpad) open Cross-building with stage-snaps downloads the wrong architecture snap (tested on snapcraft 4.6). No comments, no activity for ~5 years, tracked under Jira label craft-415.
70%