File conflicts between parts should include files with identical contents
Metadata
Current evaluation
Snapcraft still allows identical same-path files from different parts without warning; changing this collision behavior remains unresolved in craft-parts.
Suggested action: needs triage
Reason: Current craft-parts collision code still suppresses conflicts when filecmp reports identical contents, confirming the reported behavior remains. The request is understandable, but choosing a warning versus error and defining behavior for directories, symlinks, permissions, and pkg-config files requires maintainer triage; the issue has no labels, comments, or maintainer response.
Evaluated by: mr-cal-bot
Impact:
42
Quick Win:
12
Complexity:
58
Confidence:
94
Actionability:
67
Issue body
Currently, when two parts in the same snapcraft.yaml file attempt to stage the same file at the same location, it's an error only if the files have different contents. I think this is dangerous -- at the very least, even if two conflicting files have the same contents, this should generate a warning, if not an outright error. It's unwise to depend on the unpredictability of the contents of two files, which might be identical for months, only to suddenly differ and start throwing build errors.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
12
Complexity:
58
Confidence:
94
Actionability:
67
|
needs triage | Snapcraft still allows identical same-path files from different parts without warning; changing this collision behavior remains unresolved in craft-parts. | |
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
18
Complexity:
30
Confidence:
88
Actionability:
75
|
keep open | Snapcraft currently allows parts to stage identical files without warning; the request is to warn or fail on all same-path conflicts. The behavior remains implemented and tested in craft-parts. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
20
Quick Win:
14
Staleness:
85
Complexity:
30
Confidence:
60
Support Request:
40
|
needs triage | Feature request to warn on identical file conflicts during staging. Untriaged, 4 years old, no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
80
Support Request:
5
|
close stale | Snapcraft only errors on file conflicts if contents differ. Author requests warnings or errors for identical files to prevent future build failures. No maintainer response in ~4 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Request to warn or error on file conflicts between snapcraft parts even when contents match, to prevent future build failures. Issue is completely inactive with no maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
35
Confidence:
70
Support Request:
10
|
close stale | Feature request to warn or error on identical file conflicts between snapcraft parts to prevent future build failures. Unaddressed for ~3.8 years with zero maintainer interaction. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1660696 Snapcraft is testing file collisions on unbuilt parts | snapcraft (launchpad) | closed | Collision detection ran on not-yet-built parts, causing file-not-found failures (dump plugin with custom build). Fixed by PR #1405 (commit dbdc4b5a6), merged into snapcraft; bug was acknowledged by maintainers. |