← Back to issue list

Pull stage of an unspecified part is unexpectedly cleaned by snapcraft

View original Launchpad issue

Metadata

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

Current evaluation

⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.

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.

Suggested action:

No scores available.

Issue body

snapcraft.yaml: http://paste.ubuntu.com/p/Zpg8gghHNK/ == Reproduce Instructions 1. Build once 2. Run `snapcraft clean desktop-gtk3 -s pull` == Expected Behavior Several priming/staging stage are cleaned but only desktop-gtk3's pull stage is cleaned == Current Behavior Another, `poedit` part's pull stage is also cleaned, which is unnecessary at all. ``` Requested clean of 'desktop-gtk3' which requires also cleaning the part 'poedit' Cleaning priming area for poedit Cleaning staging area for poedit Cleaning build for poedit Cleaning pulled source for poedit Cleaning priming area for desktop-gtk3 Cleaning staging area for desktop-gtk3 Cleaning build for desktop-gtk3 Cleaning pulled source for desktop-gtk3 ```

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b 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.
qwen/qwen3.6-35b-a3b Closed without resolution. The snapcraft clean command unexpectedly removed another part's pull stage, which was not addressed.
qwen3.6-35b-a3b-mtp-q6 Closed without resolution. The bug report described snapcraft clean unexpectedly removing an unrelated part's pull stage. No fix or merge was implemented.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#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.
77%
#1824473 Changed stage-snaps property does not make pull step dirty snapcraft (launchpad) open 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.
73%
#1957915 Cleaning later steps and re-pulling with snapcraft 6.0.1 snapcraft (launchpad) closed Abandoned. The report described repeated part pulls during snapcraft 6.0.1 builds, but received no comments or patches to address the issue.
73%
#1804067 Remote part always considered 'pull step changed' after modifying files in local tree snapcraft (launchpad) closed Closed without resolution, likely abandoned due to inactivity. The report described a snapcraft bug where local file modifications incorrectly triggered a ccache remote part rebuild, causing unnecessary dependent part cleanups.
71%
#1605164 Errors due to "missing" files using "stage:" snapcraft (launchpad) closed Abandoned. Reported a snapcraft staging error when excluding directories with missing files. Closed without comments or a fix, indicating the issue was stale.
71%
#1799925 snapcraft gives conflicting advice for cleaning parts snapcraft (launchpad) closed Closed without a fix. Snapcraft incorrectly advised running snapcraft clean with part and step flags, which were unsupported. The author worked around it with a full clean. The report appears abandoned or superseded by later updates.
71%
#4 snapcraft.yaml needs to make all stages dirty (was: the can't add file without recreating entire package) snapcraft closed Closed without a direct fix. The maintainer noted snapcraft failed to invalidate stages when snapcraft.yaml changed, requiring an internal --force. Tracking was moved back to Launchpad, superseding this GitHub issue.
70%