← Back to issue list

No debug information about conflicting files in staging error in the launchpad build log

View original Github issue

Metadata

Project
snapcraft
Number
#4802
Type
issue
State
open
Author
seb128
Labels
—
Created
Updated
Closed
—

Current evaluation

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.

Suggested action: needs triage

Reason: No labels, no assignee, and the only comment is the autogenerated Jira-sync bot (CRAFT-2907), so no maintainer has assessed it. The bug is real and reproducible: the Launchpad log shows only 'Failed to stage: parts list the same file with different contents or permissions.' plus a 'Full execution log:' path, while the local build shows the detailed 'Parts ... list the following files' message, indicating snapcraft's error handling drops the details field. The fix likely lives in snapcraft's error display (PartsLifecycleError path in snapcraft/parts/parts.py) or craft-application's error rendering, so it needs triage to confirm the right component.

Impact: 40 Quick Win: 22.0 Staleness: 75 Complexity: 45 Confidence: 60 Support Request: 5

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
qwen/qwen3.8-27b
Impact: 40
Quick Win: 22.0
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 25
Confidence: 75
Support Request: 10
needs triage Launchpad snapcraft build logs omit detailed error messages for staging file conflicts. An internal tracking ticket was created, but the issue remains inactive and unresolved.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/snapcraft#4801 (confidence 80%)

    Explicitly referenced in the issue body as the analogous local-build problem ('Similar to ... but on launchpad'); that issue is also open and unlabelled.

Related issues

No related issues found above the similarity threshold.