No debug information about conflicting files in staging error in the launchpad build log
Metadata
Current evaluation
Launchpad shows only the brief staging-conflict failure while the conflicting parts and files remain in the execution log; this valid diagnostic gap awaits maintainer triage.
Suggested action: needs triage
Reason: The report supplies a snapcraft.yaml revision and a concrete Launchpad log showing the generic staging failure and directing users to a separate execution log containing the missing part and file details. However, it has no labels or maintainer response; the sole comment is an autogenerated CRAFT-2907 ticket notice.
Evaluated by: mr-cal-bot
Impact:
40
Quick Win:
17
Complexity:
48
Confidence:
88
Actionability:
82
Issue body
### Bug Description
Similar to https://github.com/canonical/snapcraft/issues/4801 but on launchpad
### To Reproduce
Try to build a snap with conflicting files staged by different parts
Check the build log
-> I would expect to see what the error is but the log doesn't include it
### Environment
Launchpad
### snapcraft.yaml
```shell
https://github.com/ubuntu/gnome-sdk/blob/d13758aeb4aec727e026b783931a7940de84af5f/snapcraft.yaml
```
### Relevant log output
```shell
https://launchpadlibrarian.net/728919235/buildlog_snap_ubuntu_noble_amd64_gnome-46-2404-sdk_BUILDING.txt.gz
Staging libtool (required to build 'libffi')
Failed to stage: parts list the same file with different contents or permissions.
Full execution log: '/root/.local/state/snapcraft/log/snapcraft-20240509-132418.799795.log'
Build failed
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/lpbuildd/target/build_snap.py", line 308, in run
self.build()
File "/usr/lib/python3/dist-packages/lpbuildd/target/build_snap.py", line 292, in build
self.run_build_command(["snapcraft"], cwd=output_path, env=env)
File "/usr/lib/python3/dist-packages/lpbuildd/target/operation.py", line 62, in run_build_command
return self.backend.run(args, cwd=cwd, env=full_env, **kwargs)
File "/usr/lib/python3/dist-packages/lpbuildd/target/lxd.py", line 718, in run
subprocess.check_call(cmd, **kwargs)
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['lxc', 'exec', 'lp-noble-amd64', '--env', 'LANG=C.UTF-8', '--env', 'SHELL=/bin/sh', '--env', 'http_proxy=http://10.10.10.1:8222/', '--env', 'https_proxy=http://10.10.10.1:8222/', '--env', 'GIT_PROXY_COMMAND=/usr/local/bin/lpbuildd-git-proxy', '--env', 'SNAPPY_STORE_NO_CDN=1', '--env', 'SNAPCRAFT_BUILD_INFO=1', '--env', 'SNAPCRAFT_IMAGE_INFO={"build-request-id": "lp-88872230", "build-request-timestamp": "2024-05-09T13:15:09Z", "build_url": "https://launchpad.net/~desktop-snappers/+snap/gnome-46-2404-sdk/+build/2478630"}', '--env', 'SNAPCRAFT_BUILD_ENVIRONMENT=host', '--env', 'SNAPCRAFT_BUILD_FOR=amd64', '--', '/bin/sh', '-c', 'cd /build/gnome-46-2404-sdk && linux64 snapcraft']' returned non-zero exit status 1.
Revoking proxy token...
RUN: /usr/share/launchpad-buildd/bin/in-target scan-for-processes --backend=lxd --series=noble --arch=amd64 SNAPBUILD-2478630
Scanning for processes to kill in build SNAPBUILD-2478630
```
On a local build checking the log the actual error is
'at-spi2-core' and 'atk' list the following files, but with different contents or permissions:
...```
```
### Additional context
_No response_
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
17
Complexity:
48
Confidence:
88
Actionability:
82
|
needs triage | Launchpad shows only the brief staging-conflict failure while the conflicting parts and files remain in the execution log; this valid diagnostic gap awaits maintainer triage. | |
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
18
Complexity:
48
Confidence:
90
Actionability:
84
|
needs triage | Launchpad logs show only the generic staging-conflict message while conflicting parts and files remain in an inaccessible execution log; the valid diagnostics bug is awaiting triage. | |
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
21
Complexity:
38
Confidence:
92
Actionability:
82
|
needs triage | Launchpad logs show only the generic staging-conflict failure and omit the conflicting parts and files found in the execution log; the issue remains open without maintainer triage. | |
| stealth/space-bunny-alpha |
Impact:
43
Quick Win:
22
Complexity:
42
Confidence:
91
Actionability:
88
|
needs triage | Launchpad omits conflicting-file details from staging failures, leaving only a generic error and an inaccessible execution-log path. The issue remains open and untriaged with a concrete reproducer. | |
| stealth/space-bunny-alpha |
Impact:
32
Quick Win:
12
Complexity:
42
Confidence:
58
Actionability:
62
|
keep open | Staging conflict error on Launchpad shows only the short message; the detail naming conflicting parts/files goes to the execution log only. Duplicate report of #4801 for Launchpad builds, open since May 2024. | |
| qwen/qwen3.6-35b-a3b |
Impact:
60
Quick Win:
25
Complexity:
40
Confidence:
70
Actionability:
70
|
needs triage | Launchpad build logs omit detailed error messages for staging file conflicts, showing only the brief message without listing which files conflict | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
22
Staleness:
75
Complexity:
45
Confidence:
60
Support Request:
5
|
needs triage | 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. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
90
Complexity:
35
Confidence:
85
Support Request:
10
|
close stale | Launchpad build logs omit detailed debug info for staging conflicts, unlike local builds. Currently untriaged with no maintainer response since May 2024. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
80
Complexity:
35
Confidence:
75
Support Request:
10
|
needs triage | Launchpad build logs omit specific conflicting file and part details during staging errors, unlike local builds. The report remains open with no maintainer response since May 2024, only referencing an internal Jira ticket. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#4801
(confidence 98%)
The report explicitly identifies #4801 as the same staging-conflict diagnostics problem for local debug-shell builds.
Related issues
No related issues found above the similarity threshold.