← 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 reportedly creates an empty core18 arm64 snap when stage-packages use :arm64 suffixes natively, while cross-compilation succeeds; no triage or resolution is recorded.

Suggested action: needs triage

Reason: The report provides a complete snapcraft.yaml and a clear native-versus-cross-compilation discrepancy, but it lacks the native host architecture, exact command, logs, and confirmation against a current Snapcraft release. The issue has no labels, maintainer comments, or other evidence of assessment, so it needs triage rather than closure based on its age.

Evaluated by: mr-cal-bot

Impact: 58 Quick Win: 18 Complexity: 52 Confidence: 79 Actionability: 64

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
stealth/space-bunny-alpha
Impact: 58
Quick Win: 18
Complexity: 52
Confidence: 79
Actionability: 64
needs triage Snapcraft 4.0.7 reportedly creates an empty core18 arm64 snap when stage-packages use :arm64 suffixes natively, while cross-compilation succeeds; no triage or resolution is recorded.
stealth/space-bunny-alpha
Impact: 45
Quick Win: 9
Complexity: 58
Confidence: 89
Actionability: 50
needs triage Snapcraft 4.0.7 reportedly builds a core18 arm64 snap when cross-compiling but produces an empty snap natively with :arm64 stage-packages; no triage or resolution is recorded.
qwen/qwen3.8-27b
Impact: 30
Quick Win: 18
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.

Update history

Date Change
created

Related issues

Issue Project State Summary Similarity
#1835638 inconsistent to arch behaviour snapcraft (launchpad) open Snapcraft 3.6 advanced grammar can omit stage-packages on native builds and mix host/target packages in nested on/to cases; the old report remains open and untriaged.
73%
#1849707 stage-snap causes issues when mixing cores snapcraft (launchpad) open Staging a core16 snap into core18 reportedly overwrote build tools and caused file collisions; the proposed mismatch warning is untriaged, and core18 support has since been removed.
72%
#1983009 Snapcraft 7.1.0 fails to find stage package when cross-compiling snapcraft (launchpad) closed Fixed by canonical/snapcraft#3416 (commit 8f418e3d9), restoring core20 behavior so stage packages come from build-on repositories during cross-compilation.
71%