Doesn't tell you about conflicting files in staging before exiting the debug shell
Metadata
Current evaluation
Debug shell shows only the brief staging-conflict message, not which parts/files conflict; details only in log. Reported May 2024, one bot comment, no maintainer triage.
Suggested action: needs triage
Reason: No maintainer has responded, labelled, or assigned this; the only comment is the auto-generated Jira sync (CRAFT-2906). The report is a valid UX/bug complaint with a clear repro, but it has sat untriaged for ~18 months, so it needs a maintainer to assess whether the detailed conflict info should be surfaced before the debug shell.
Impact:
40
Quick Win:
26.0
Staleness:
70
Complexity:
35
Confidence:
55
Support Request:
10
Issue body
### Bug Description
Trying to debug an issue with the gnome-46-2404-sdk build locally
installed: 8.2.5 (11627) 74MB classic
```
$ SNAPCRAFT_ENABLE_EXPERIMENTAL_EXTENSIONS=1 snapcraft --debug --verbosity=verbose
...
Staging libtool (required to build 'libffi')
Failed to stage: parts list the same file with different contents or permissions.
Launching shell on build environment...
snapcraft-gnome-46-2404-sdk-on-amd64-for-amd64-9167204 ../project#
exit
Failed to stage: parts list the same file with different contents or permissions.
Failed to execute snapcraft in instance.
Full execution log: '/home/seb128/.local/state/snapcraft/log/snapcraft-20240509-165322.300995.log'
```
which makes me believe the issue is in the libtool part since that's what is printed just before getting me the shell but in fact checking the log tells me
`Parts 'at-spi2-core' and 'atk' list the following files, but with different contents or permissions:`
Shame that this information wasn't shared before I wasted half an hour in the shell poking at the wrong part...
### To Reproduce
$ git clone https://github.com/ubuntu/gnome-sdk
$ cd gnome-sdk
$ git checkout f44a9363
$ SNAPCRAFT_ENABLE_EXPERIMENTAL_EXTENSIONS=1 snapcraft --debug --verbosity=verbose
(the experimental env is needed until the a new snapcraft lands which make the core24/gnome46 support stable)
### Environment
Ubuntu Noble
### snapcraft.yaml
```shell
https://github.com/ubuntu/gnome-sdk/blob/f394b7985
```
### Relevant log output
```shell
shared in description
```
### Additional context
_No response_
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
26.0
Staleness:
70
Complexity:
35
Confidence:
55
Support Request:
10
|
needs triage | Debug shell shows only the brief staging-conflict message, not which parts/files conflict; details only in log. Reported May 2024, one bot comment, no maintainer triage. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
90
Complexity:
15
Confidence:
85
Support Request:
0
|
needs triage | Bug report indicating snapcraft prints staging conflict errors after exiting the debug shell instead of before, complicating debugging. Unlabelled with no maintainer response in over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
30
Confidence:
65
Support Request:
10
|
needs triage | snapcraft --debug exits the debug shell before displaying the actual staging conflict error, forcing users to check logs manually. Untriaged and inactive for over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
70
Support Request:
0
|
close stale | Snapcraft's debug shell omits staging conflict details until after exiting, requiring manual log inspection. The report remains open and inactive for over a year, with a Jira ticket created but no triage or assignment. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4802 No debug information about conflicting files in staging error in the launchpad build log | snapcraft | open | Launchpad snapcraft builds only print the brief staging-conflict error, not the list of conflicting files; reporter expects details in the build log. Unlabelled, no maintainer response since the 2024-05-09 Jira sync bot comment. |