Remote parts don't seem to work in snapcraft 3.0
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed without resolution. The report details a build failure with 'desktop-launch' when using remote parts in snapcraft 3.0, but received zero comments and no fix.
Suggested action: —
No scores available.
Issue body
I've got a yaml which has after: [desktop-gtk2], and an apps stanza which has "desktop-launch foo". When building snapcraft errors with.
Failed to generate snap metadata: The specified command 'desktop-launch' defined in the app 'snes9x-gtk' does not exist or is not executable.
Ensure that 'desktop-launch' is relative to the prime directory.
I'm doing this inside multipass if that matters, and it's a core18 based snap.
name: snes9x
version: '1.56.2' # just for humans, typically '1.2+git' or '1.3.2'
summary: Super NES Emulator
description: |
Snes9x is a portable, freeware Super Nintendo Entertainment System (SNES)
emulator. It basically allows you to play most games designed for the SNES
and Super Famicom Nintendo game systems on your PC or Workstation; they
include some real gems that were only ever released in Japan.
base: core18
grade: stable
confinement: strict
apps:
snes9x-gtk:
environment:
"LD_LIBRARY_PATH": "$LD_LIBRARY_PATH:$SNAP/usr/lib/$SNAPCRAFT_ARCH_TRIPLET/pulseaudio"
command: desktop-launch $SNAP/bin/snes9x-gtk
plugs:
- x11
- network
- network-bind
- joystick
- home
- pulseaudio
- removable-media
parts:
snes9x:
after: [desktop-gtk2]
source: https://github.com/snes9xgit/snes9x.git
plugin: autotools
source-tag: '1.56.2'
build-packages:
- libsdl1.2-dev
- libboost-thread-dev
- libboost-system-dev
- libsdl-ttf2.0-dev
- libasound2-dev
- zlib1g-dev
- libpng-dev
- xorg-dev
- libpulse-dev
- libx11-dev
- libxml2-dev
- portaudio19-dev
- intltool
- libgtk-3-dev
- libminizip-dev
- libsdl2-dev
stage-packages:
- pulseaudio-utils
- libpulse0
override-build: |
cd gtk
autoreconf --install
intltoolize --force
./configure
make
cp -a snes9x-gtk $SNAPCRAFT_PART_INSTALL/bin
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The report details a build failure with 'desktop-launch' when using remote parts in snapcraft 3.0, but received zero comments and no fix. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Lacking follow-up, the report was likely abandoned. The user encountered a missing desktop-launch command error when using remote parts in snapcraft 3.0 on core18. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed and likely abandoned due to inactivity. No comments or resolution were provided. The reported snapcraft 3.0 remote parts and desktop-launch error remains unfixed. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1750866 Remote parts can't depend on other remote parts | snapcraft (launchpad) | closed | Closed as abandoned due to inactivity. Snapcraft does not automatically pull in dependent remote parts, requiring manual specification in the snap.yaml. | |
| #1804067 Remote part always considered 'pull step changed' after modifying files in local tree | snapcraft (launchpad) | closed | Closed without resolution, likely abandoned due to inactivity. The report described a snapcraft bug where local file modifications incorrectly triggered a ccache remote part rebuild, causing unnecessary dependent part cleanups. | |
| #1876123 remote-build failed | snapcraft (launchpad) | closed | A snapcraft remote-build crash causing a NoneType error was closed without resolution or further discussion, indicating abandonment. No fix or merge details were provided. | |
| #1719951 SNAPCRAFT_PARTS_URI doesn't work with cleanbuild | snapcraft (launchpad) | closed | Abandoned and closed without resolution due to inactivity. The report details a snapcraft cleanbuild failure where SNAPCRAFT_PARTS_URI fails to resolve remote parts, triggering a subprocess error. No fix was implemented. |