← 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

No response or triage is present. Current craft-parts still omits stage-snaps from PullState.properties_of_interest, matching the reported stale-step and build crash.

Suggested action: needs triage

Reason: The report provides a public PoC, exact rerun steps, and the resulting crash, but has no labels, comments, assignee, or maintainer assessment. PullState.properties_of_interest includes stage-packages and stage-slices but not stage-snaps, while _run_pull fetches stage-snaps into the pull state, confirming the reported dirtiness gap.

Evaluated by: mr-cal-bot

Impact: 62 Quick Win: 35 Complexity: 28 Confidence: 91 Actionability: 78

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
stealth/space-bunny-alpha
Impact: 62
Quick Win: 35
Complexity: 28
Confidence: 91
Actionability: 78
needs triage No response or triage is present. Current craft-parts still omits stage-snaps from PullState.properties_of_interest, matching the reported stale-step and build crash.
stealth/space-bunny-alpha
Impact: 45
Quick Win: 26
Complexity: 32
Confidence: 89
Actionability: 86
needs triage Changing a part's stage-snaps skips pull on incremental builds and fails staging; a precise POC exists, but the longstanding report remains untriaged.
qwen/qwen3.8-27b
Impact: 40
Quick Win: 18
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.

Update history

Date Change
created

Related issues

No related issues found above the similarity threshold.