Doesn't tell you about conflicting files in staging before exiting the debug shell
Metadata
Current evaluation
Staging conflict diagnostics are omitted before --debug opens a shell, forcing users to find the conflicting parts and files in the log; the exact-reproducer report remains open and untriaged.
Suggested action: needs triage
Reason: The report provides a precise gnome-sdk commit and command sequence, and identifies that the terminal shows only the generic staging failure while the log names at-spi2-core and atk. There are no labels, assignee, maintainer response, or resolving Snapcraft change—only an automated CRAFT-2906 sync—and current behavior should be rechecked because lifecycle.py now prints the caught error before launch_shell.
Evaluated by: mr-cal-bot
Impact:
31
Quick Win:
16
Complexity:
34
Confidence:
87
Actionability:
76
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
31
Quick Win:
16
Complexity:
34
Confidence:
87
Actionability:
76
|
needs triage | Staging conflict diagnostics are omitted before --debug opens a shell, forcing users to find the conflicting parts and files in the log; the exact-reproducer report remains open and untriaged. | |
| stealth/space-bunny-alpha |
Impact:
28
Quick Win:
18
Complexity:
25
Confidence:
90
Actionability:
84
|
needs triage | Staging file-conflict errors show only a generic failure before --debug opens the shell; conflicting parts and files remain hidden in the log. Reproducer is clear but the issue is not yet maintainer-triaged. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
14
Complexity:
40
Confidence:
70
Actionability:
80
|
keep open | Snapcraft doesn't show conflicting file details in staging before entering debug shell, forcing users to check logs | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
26
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. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft#4802
(confidence 98%)
Reports the same omission of detailed staging-conflict information in Launchpad build logs.
Related issues
No related issues found above the similarity threshold.