Python parts can't be automatically rebuilt if dirty
Metadata
Current evaluation
Closed without comments or documented resolution. The snapcraft build caching bug preventing dirty Python parts from rebuilding due to missing python3 paths was abandoned.
Suggested action: —
No scores available.
Issue body
If the snapcraft CLI determines that a part is dirty (perhaps a dependency changed, or YAML properties changed) it will attempt to clean the dirty steps and re-run them. However, if the build or pull steps of a python part are considered dirty, rebuilding them always errors with "Unable to find python3, searched: stage:parts/python-part/install"
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without comments or documented resolution. The snapcraft build caching bug preventing dirty Python parts from rebuilding due to missing python3 paths was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | A bug report detailing failed automatic rebuilds of dirty Python parts due to a missing python3 path error was closed without resolution. The ticket appears abandoned due to prolonged inactivity, with no fix or workaround implemented. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.