snapcraft.yaml needs to make all stages dirty (was: the can't add file without recreating entire package)
Metadata
Current evaluation
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.
Suggested action: —
No scores available.
Issue body
I am running snapcraft assemble (qml plugin) on ted's branch lp:~ted/+junk/digitalsign
while iterating over the package, I added 1 new file in ./pic.jpg and edited snapcraft.yaml accordingly:
parts:
qml:
plugin: qml
digitalsign:
plugin: copy
mkdirs:
- bin
files:
digitalsign: bin/digitalsign
digitalsign.qml: digitalsign.qml
pic.jpg: pic.jpg
snappy-metadata: meta
rerunning snapcraft assemble will not pull in the new file, as it's skipping the build stage:
olli@joe-XPS-12-9Q33:~/code/snappy/digitalsign$ ../../qml/bin/snapcraft assemble
Skipping pull digitalsign (already ran)
Skipping build digitalsign (already ran)
Skipping stage digitalsign (already ran)
Snapping digitalsign
...
upon deleting ./snap/ ./parts/ ./stage/ the file is being pulled in:
...
Building digitalsign
cp --preserve=all -R digitalsign /home/olli/code/snappy/digitalsign/parts/digitalsign/install/bin/digitalsign
cp --preserve=all -R digitalsign.qml /home/olli/code/snappy/digitalsign/parts/digitalsign/install/digitalsign.qml
cp --preserve=all -R pic.jpg /home/olli/code/snappy/digitalsign/parts/digitalsign/install/pic.jpg
...
while not critical (workaround: delete files, start over) it's imho a bad experience as it can be expected that developers will iterate over the package quite frequently, rebuilding is taking longer time and thus not desirable
Launchpad Details: [#LP1477904](https://bugs.launchpad.net/bugs/1477904) Olli Ries - 2015-07-24 06:15:58 -0300
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | 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. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned and migrated back to Launchpad. The maintainer noted snapcraft should dirty all stages when snapcraft.yaml changes, but no fix was implemented and tracking reverted to Launchpad. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a documented fix. Maintainer acknowledged snapcraft fails to rebuild when snapcraft.yaml changes and should invalidate all stages upon modification. Tracking moved back to Launchpad. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Superseded by Launchpad tracking. Modifying snapcraft.yaml fails to trigger stage rebuilds, requiring an internal dirty flag. Closed without resolution. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed and migrated to Launchpad. Maintainers noted snapcraft must dirty all stages when snapcraft.yaml changes, but no code fix or merge was implemented on GitHub. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.