Local file changes are not detected
Metadata
Current evaluation
Triaged enhancement to mark dump-plugin pull steps dirty when local sources change, including permission-only edits; a maintainer confirmed in 2026 that it remains unimplemented.
Suggested action: keep open
Reason: The issue is explicitly labeled "Status: Triaged" and "Type: Enhancement," and a 2026 maintainer reply states there has been "no progress." Current LocalSource.check_if_outdated() compares only st_mtime, leaving permission-only changes uncovered, while the requested dirty-pull behavior is not implemented; source metadata and lifecycle semantics require moderate development.
Evaluated by: mr-cal-bot
Impact:
58
Quick Win:
17
Complexity:
61
Confidence:
92
Actionability:
74
Issue body
### What needs to get done
Detect if the `source` of the `dump` plugin has been modified (including file permissions).
If it has been modified, the `pull` step for that part should be marked as dirty.
### Why it needs to get done
When files are changed locally, the `dump` plugin does not detect changes or re-run the `pull` step.
source: https://github.com/canonical/snapcraft/issues/4984
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
58
Quick Win:
17
Complexity:
61
Confidence:
92
Actionability:
74
|
keep open | Triaged enhancement to mark dump-plugin pull steps dirty when local sources change, including permission-only edits; a maintainer confirmed in 2026 that it remains unimplemented. | |
| qwen/qwen3.6-35b-a3b |
Impact:
65
Quick Win:
27
Complexity:
45
Confidence:
75
Actionability:
75
|
keep open | Enhancement to detect local source file changes in the dump plugin and mark the pull step as dirty when modifications occur. | |
| qwen/qwen3.8-27b |
Impact:
55
Quick Win:
25
Staleness:
60
Complexity:
55
Confidence:
75
Support Request:
10
|
keep open | Enhancement to detect local file changes (incl. permissions) for the dump plugin and mark the pull step dirty. Triaged, tracked as CRAFT-3268; maintainer confirmed no progress as of 2026-02-18. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
70
Complexity:
40
Confidence:
90
Support Request:
5
|
keep open | Enhancement to detect local file modifications in the dump plugin and mark the pull step as dirty. Currently triaged but inactive for over 5 months with no progress despite maintainer acknowledgment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
55
Complexity:
40
Confidence:
85
Support Request:
10
|
keep open | Enhancement to detect local file changes in the dump plugin's source and mark the pull step as dirty. Triaged but inactive for over 4 months with no progress despite maintainer acknowledgment. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#4984
(confidence 98%)
Explicitly cited in the issue body as the originating Snapcraft report.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1364 File source handler ignores changes to the file | craft-parts | open | Confirmed triaged bug: source-type: file lacks pull-step change detection, so touched or edited files are not recopied; dump and Python plugin cases are affected. | |
| #1647877 The pull step is not marked as dirty when the source of the dump plugin is changed | snapcraft (launchpad) | closed | Local-source dirty tracking was added in canonical/snapcraft#2167, commit 39c4c39f1, resolving missed rebuilds after files changed under `.`. |