Modifying snapcraft.yaml with parts using local sources get dirty
Metadata
Current evaluation
Closed without resolution or comments. Appears abandoned, with no fix or workaround implemented.
Suggested action: —
No scores available.
Issue body
Modifying the snap directory should not trigger a rebuild for a part (as that would be the mostly desired outcome).
e.g.; Modifying the apps entry should not trigger a rebuild when using "source: ."
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments. Appears abandoned, with no fix or workaround implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned and closed without resolution. The report indicated that modifying snapcraft.yaml with local sources incorrectly triggered unnecessary rebuilds. No fix was implemented. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1746784 Failing while fetching parts.snapcraft.io should be handled better | snapcraft (launchpad) | closed | Closed without comments or resolution. No fix or merge details provided; likely abandoned or marked stale. | |
| #1448 snapcraft build using manifest.yaml | snapcraft | closed | Closed without discussion or comments. The issue appears abandoned or superseded by newer snapcraft build workflows. No resolution or merge details were recorded. | |
| #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. | |
| #1650686 Some symlinks not properly fixed up | snapcraft (launchpad) | closed | Abandoned. Closed without comments or resolution. The snapcraft build failure caused by unpatched absolute symlinks remains unresolved, with no fix implemented. | |
| #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. | |
| #1660885 confusing behaviour using the root of the repo as source | snapcraft (launchpad) | closed | Closed without resolution. The discussion on confusing relative path behavior for snapcraft.yaml source directories was abandoned. No code changes were implemented. | |
| #1650943 Wrong source-type in yaml is ignored | snapcraft (launchpad) | closed | Closed without a documented fix or PR. Invalid source-type values in snapcraft.yaml remain silently ignored, suggesting the bug was abandoned or resolved upstream without tracking. | |
| #1597484 The parser needs to support hidden .snapcraft.yaml files | snapcraft (launchpad) | closed | Closed without resolution. Support for hidden .snapcraft.yaml files was abandoned due to inactivity. No fix or implementation details were recorded. | |
| #1816 snapcraft update won't fetch from `SNAPCRAFT_PARTS_URI` | snapcraft | closed | Closed without resolution or comments. Likely superseded by the linked Launchpad bug report. No fixes or code changes were applied. | |
| #1528873 snapcraft produces supposely bad caps formatting in package.yaml | snapcraft (launchpad) | closed | Closed without resolution. References an external Launchpad bug regarding snapcraft caps formatting in package.yaml. No fix or merge occurred, indicating the report was abandoned. |