← Back to issue list

stage-packages behaviour inconsistent

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1885074
Type
issue
State
open
Author
~ondrak
Labels
Created
Updated
Closed

Current evaluation

Snapcraft 4.0.7: stage-packages with :arm64 suffix cross-compile fine but native arm64 build yields an empty snap. Reported ~6 years ago, no maintainer response, no labels, zero comments.

Suggested action: close stale

Reason: The issue targets snapcraft 4.0.7 (a 2019-era release) and has had zero maintainer interaction for ~6 years (2258 days, 0 comments, no labels). The affected version is long since superseded by snapcraft 8.x, whose parts/stage-packages handling was substantially reworked, so the original problem is no longer applicable to a supported version. Related cross-compile stage-package arch-suffix reports (e.g. canonical/snapcraft#5335) were closed as expected behavior with documentation, reinforcing that this class of arch-suffix handling is understood and no longer an open defect.

Impact: 30 Quick Win: 18.0 Staleness: 95 Complexity: 40 Confidence: 55 Support Request: 15

Issue body

snapcraft: 4.0.7 snapcraft.yaml: name: test-snap base: core18 version: '0.1' summary: test bug description: | Test snapcraft-bug grade: stable confinement: strict architectures: [ arm64 ] parts: initrd: plugin: nil stage-packages: - e2fsprogs:arm64 - libgcrypt20:arm64 - libgpg-error0:arm64 - libuuid1:arm64 - dmsetup:arm64 This snap will cross compile with expected result, however native build with result in empty snap

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 30
Quick Win: 18.0
Staleness: 95
Complexity: 40
Confidence: 55
Support Request: 15
close stale Snapcraft 4.0.7: stage-packages with :arm64 suffix cross-compile fine but native arm64 build yields an empty snap. Reported ~6 years ago, no maintainer response, no labels, zero comments.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 25
Confidence: 90
Support Request: 10
close stale Reports inconsistent stage-packages behavior in Snapcraft 4.0.7 where architecture-specific packages fail on native builds. Unattended for ~6 years with no maintainer response.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 45
Confidence: 90
Support Request: 25
close stale Inconsistent stage-packages behavior in snapcraft 4.0.7 causing empty native builds. Issue is over six years old with no activity or maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 40
Confidence: 90
Support Request: 10
close stale Reports inconsistent stage-packages behavior in snapcraft 4.0.7 where architecture-specific pins fail during native builds. Issue is 6 years old, unlabelled, and based on a long-unsupported version.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 40
Confidence: 90
Support Request: 10
close stale Reports inconsistent stage-packages behavior between cross-compile and native builds in snapcraft v4.0.7 with core18. No activity for 6 years, outdated versions, and no maintainer response.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/snapcraft#5335 (confidence 50%)

    Same class of stage-packages arch-suffix handling around native vs cross builds; closed as expected behavior with docs, indicating the area was addressed.

Related issues

Issue Project State Summary Similarity
#2012503 wrong arch of stage packages snapcraft (launchpad) open Snapcraft 7.3 picks host architecture for stage packages when cross-building (build-on amd64, build-for arm64). No maintainer response in 3.4 years. Nearly identical issue #5335 was closed as expected behavior requiring explicit :$CRAFT_ARCH_BUILD_FOR suffix on stage packages.
75%
#1921418 wrong architecture of stage-snaps when cross building snapcraft (launchpad) open Cross-building with stage-snaps downloads the wrong architecture snap (tested on snapcraft 4.6). No comments, no activity for ~5 years, tracked under Jira label craft-415.
73%
#1835638 inconsistent to arch behaviour snapcraft (launchpad) open Snapcraft 3.6 stage-packages with 'on <arch>'/'to <arch>' conditionals behave inconsistently: cross-compiling works but native builds fail to pull required packages, and adding 'else' under 'on amd64' mixes arch packages. No maintainer response in 7+ years.
72%
#4386 stage-packages pull, fails for arm64 target architecture snapcraft closed Closed as abandoned after the author changed their build process and could not confirm if the arm64 stage-packages pull failure persists. No fix was implemented.
72%
#1983009 Snapcraft 7.1.0 fails to find stage package when cross-compiling snapcraft (launchpad) closed Closed. Snapcraft 7.1.0 fails to find stage packages like bluez when cross-compiling from amd64 to arm64/armhf, breaking builds. Issue closed without a provided resolution or fix.
71%
#1569280 Snapcraft fails to strip go binaries on arm snapcraft (launchpad) closed Closed without resolution. Snapcraft failed to strip Go binaries on ARM during Launchpad builds, causing failures despite amd64 success. No fix or comments were provided.
70%