← Back to issue list

Building snaps directly from GitHub fails

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1790052
Type
issue
State
closed
Author
~kenokenobingo
Labels
Created
Updated
Closed

Current evaluation

⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.

A snapcraft build failure triggered by a deb-systemd-invoke error was abandoned and closed without resolution. No comments or follow-up actions were recorded.

Suggested action:

No scores available.

Issue body

When directly building my code from GitHub on build.snapcraft.io, an error message appears, which seems to be a snapcraft fault. `deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code 101 and 104!` Complete log is attached.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b A snapcraft build failure triggered by a deb-systemd-invoke error was abandoned and closed without resolution. No comments or follow-up actions were recorded.
qwen/qwen3.6-35b-a3b Abandoned and closed without resolution. The deb-systemd-invoke policy-rc.d return code error during snap builds was never addressed or fixed.
qwen3.6-35b-a3b-mtp-q6 Closed without resolution. The reported build failure on build.snapcraft.io involving a deb-systemd-invoke error received no comments or follow-up, indicating the report was abandoned or closed due to inactivity.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1731478 Snap of snapcraft fails to run on Solus and openSUSE snapcraft (launchpad) closed Closed without resolution. Hard dependency on Debian apt_pkg caused runtime failures on non-Debian distros. The report was abandoned after seven days with zero comments or patches.
74%
#1566363 snapcraft deb touches snap-package systemd files snapcraft (launchpad) closed Closed without resolution. The report described unexpected systemd file modifications during snapcraft package removal, but no fix or follow-up was documented.
73%
#1647139 CalledProcessError: Command '['/usr/bin/sudo', '/usr/sbin/chroot', '/home/buildd/build-SNAPBUILD-12520/chroot-autobuild', 'linux64', '/bin/sh', '-c', 'cd /build/qucs-spice && env LANG=C.UTF-8 https_proxy=http://snap-proxy.launchpad.net:3128 http_proxy=http://snap-proxy.launchpad.net:3128 SNAPCRAFT_LOCAL_SOURCES=1 snapcraft pull']' returned non-zero exit status 1 snapcraft (launchpad) closed A snapcraft build failure during the pull stage was closed without resolution. The report was abandoned due to prolonged inactivity, with no comments or fixes provided.
72%
#1675516 can't cleanbuild snapcraft itself snapcraft (launchpad) closed Closed without resolution or comments, the report of a failed snapcraft cleanbuild due to missing build-packages was abandoned.
71%