← Back to issue list

Snapcraft should consider dump part's file permission change as part changed

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1822709
Type
issue
State
open
Author
~brlin
Labels
craft-216
Created
Updated
Closed
—

Current evaluation

Snapcraft's dump part doesn't mark a part dirty when a source file's UNIX permissions change (e.g. chmod +x), forcing manual clean. Reported 7+ years ago, no comments, no maintainer activity, and the underlying dirty-check logic has since moved to craft-parts.

Suggested action: needs triage

Reason: The issue is a legitimate bug report (dump part not detecting permission-only changes) but has zero comments, no labels beyond a tracking tag, and no maintainer response in ~2 years of inactivity. The dirty-check logic now lives in craft-parts (state_manager.py), so a maintainer needs to assess whether this is still reproducible there and whether permission changes should be part of the dirty check. No evidence it was fixed or closed elsewhere.

Impact: 30 Quick Win: 18.0 Staleness: 85 Complexity: 40 Confidence: 60 Support Request: 5

Issue body

Currently, Snapcraft won't consider a part dirty if a file in the part's source has its UNIX file permission changed (e.g. `chmod +x`), it should do so so that one doesn't need to clean the part manually.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 30
Quick Win: 18.0
Staleness: 85
Complexity: 40
Confidence: 60
Support Request: 5
needs triage Snapcraft's dump part doesn't mark a part dirty when a source file's UNIX permissions change (e.g. chmod +x), forcing manual clean. Reported 7+ years ago, no comments, no maintainer activity, and the underlying dirty-check logic has since moved to craft-parts.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 20
Confidence: 90
Support Request: 10
close stale Requests Snapcraft to track UNIX file permission changes in dump parts as dirty state changes to avoid manual cleanups. Unaddressed for over 7 years with zero maintainer interaction.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 20
Confidence: 90
Support Request: 10
close stale Snapcraft ignores UNIX permission changes in dump part sources when determining if a part is dirty, requiring manual cleaning. The issue remains open with no maintainer response or comments after over 7 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 20
Confidence: 80
Support Request: 10
close stale Snapcraft ignores UNIX permission changes in dump part sources when determining if a part is dirty, requiring manual cleanup. Unassessed for over 7 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 30
Confidence: 80
Support Request: 10
close stale Snapcraft ignores UNIX permission changes in dump part sources, treating them as unchanged and requiring manual cleaning. The open issue has zero comments and no recent activity, awaiting triage and implementation.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1889081 snapcraft does not detect need to re-clean part after permission bits change on file snapcraft (launchpad) open Snapcraft fails to detect permission-bit-only changes in dump part source files, requiring manual clean before re-priming. Untriaged, no maintainer activity in ~5.5 years; related Launchpad bug still open.
82%