A core24 snap creation fails on compression (RISCV64)
Metadata
Current evaluation
core24 riscv64 snap builds failed at `snap pack` (exit 20). Maintainers traced it to older snapd on RISCV lacking core24 support, not snapcraft; fixed once newer snapd shipped. Reporter confirmed 'Fixed now' on 2024-10-26.
Resolution: closed not a bug
Reason: ~the-meulengracht identified the failure as a known upstream snapd issue on RISCV (stable snapd too old for core24 riscv), not a snapcraft defect, and the reporter confirmed 'Fixed now' on 2024-10-26 after snapd updated, with core22 as an interim workaround. No snapcraft code change was made.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | core24 riscv64 snap builds failed at `snap pack` (exit 20). Maintainers traced it to older snapd on RISCV lacking core24 support, not snapcraft; fixed once newer snapd shipped. Reporter confirmed 'Fixed now' on 2024-10-26. | |
| stealth/space-bunny-alpha | — | closed resolved | Resolved by updating snapd: after snapd 2.65 reached RISCV64 stable, the reporter confirmed on 2024-10-26 that core24 snap pack failures were fixed. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a fix or maintainer explanation; the reported core24 RISCV64 failure during xz compression remains unresolved. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed and abandoned without resolution or comments. The snapcraft xz compression failure on RISCV64 architecture remains unresolved. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
92
Complexity:
45
Confidence:
75
Support Request:
15
|
needs triage | Snapcraft core24 build fails during xz compression on RISC-V 64 architecture. Works on other archs. Unresolved, no maintainer response since September 2024. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
45
Confidence:
90
Support Request:
10
|
needs triage | Snapcraft core24 snap build fails during xz compression on riscv64. Reported over 1.5 years ago with no maintainer response, labels, or assignee. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
92
Complexity:
45
Confidence:
75
Support Request:
15
|
needs triage | Snap creation fails during xz compression on riscv64 architecture. Reported over a year ago with build logs, but remains unlabelled and has received no maintainer response or triage. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Blocked By:
canonical/snapcraft#4499
(confidence 90%)
snap pack failures not surfaced to stdout, hiding the real snapd error; cited by ~mr-cal, later fixed by PR #5188 (commit a9fc44093)
-
Blocked By:
snapd#2070926
(confidence 75%)
Upstream snapd work to produce printable error messages that snapcraft#4499 depends on
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1984227 Snapcraft 7.1.1 does not build with core22 on riscv64 | snapcraft (launchpad) | closed | Fixed in Snapcraft 7.1.2, which added the missing riscv64 support needed to build core22 snaps. | |
| #4980 Fix Snapcraft 7 builds on riscv64 | snapcraft | closed | Closed as obsolete without a riscv64 fix: Snapcraft 7 now serves core18-only builds, which do not support RISC-V. | |
| #772 build(snap): drop 'riscv64' for now | rockcraft | merged | Merged as f0e8fe0d: removed riscv64 from the snap build (1-line change) because core24+riscv64 was unsupported by the store, which had left 'edge' diverged from 'main'. Risсv64 was later restored in #1024. | |
| #2064639 snapcraft remote-build core20 armhf openssl error | snapcraft (launchpad) | closed | armhf/riscv64/ppc64el/s390x remote-build failed on core20 after cryptography 42.0.5 broke the OpenSSL legacy provider. Fixed by merged PR canonical/snapcraft#4784 (commit 7aeffed19), setting CRYPTOGRAPHY_OPENSSL_NO_LEGACY=1 in the snap manifest; LP#2064639 closed as fixed. | |
| #1866300 snapcraft fails to build core20 snap | snapcraft (launchpad) | closed | Closed without a documented fix after core20 Multipass/LXD failures; core20 build-base support was unavailable and the workaround was destructive mode. |