← Back to issue list

override-prime disables primed-stage-packages

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#2097440
Type
issue
State
open
Author
~valentin.david
Labels
—
Created
Updated
Closed
—

Current evaluation

Bug report: using override-prime in a part causes primed-stage-packages to be empty in the manifest, even when stage-packages are specified. Untriaged, 576 days old.

Suggested action: needs triage

Reason: The issue has zero maintainer comments, no labels, and no assignee, indicating it has not yet been triaged. The bug report is clear with a minimal reproduction case showing that override-prime causes primed-stage-packages to be empty in the manifest. Code analysis in craft-parts/part_handler.py confirms the logic: _get_primed_stage_packages is called with contents.partitions_contents which tracks files from the override-prime step, but files from stage-packages installed during the stage step may not be included in that tracking.

Impact: 50 Quick Win: 22.5 Staleness: 85 Complexity: 55 Confidence: 65 Support Request: 15

Issue body

Consider the following `snapcraft.yaml` ``` name: something version: '0.1' summary: something description: something base: core24 confinement: strict parts: something: plugin: nil stage-packages: - libbrotli1 override-prime: | craftctl default ``` `SNAPCRAFT_BUILD_INFO=1 snapcraft` will generate a manifest with an empty `primed-stage-packages`. But if I remove `override-prime`, then it will work correctly.

Evaluation history

Date Model Scores Action Summary
qwen3.6-35b-a3b-mtp-q6
Impact: 50
Quick Win: 22.5
Staleness: 85
Complexity: 55
Confidence: 65
Support Request: 15
needs triage Bug report: using override-prime in a part causes primed-stage-packages to be empty in the manifest, even when stage-packages are specified. Untriaged, 576 days old.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 40
Confidence: 80
Support Request: 10
close stale Using override-prime in a snapcraft.yaml part causes primed-stage-packages to be empty in the manifest. Unlabelled, zero comments, inactive for over 14 months.
qwen/qwen3.6-35b-a3b
Staleness: 92
Complexity: 45
Confidence: 85
Support Request: 10
needs triage Using override-prime in snapcraft.yaml causes primed-stage-packages to be empty in the manifest. The issue is unlabelled, has zero comments, and has been inactive for approximately 17 months.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 40
Confidence: 90
Support Request: 10
needs triage Using override-prime in a snapcraft part causes primed-stage-packages to be empty in the manifest, while removing it works correctly. Untriaged with no maintainer comments.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 55
Confidence: 80
Support Request: 15
needs triage Using override-prime in snapcraft.yaml causes primed-stage-packages to be empty in the manifest. Issue is unlabelled, has no maintainer comments, and has been inactive for over 16 months.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#5552 `primed-stage-packages` isn't in manifest.yaml when using override-prime snapcraft open primed-stage-packages missing from manifest.yaml when override-prime is used; triaged bug blocked by upstream craft-parts issue #1122 which remains open. No fix implemented in ~15 months.
83%
#1122 craft-parts doesn't track primed files when using `override-prime` craft-parts open craft-parts writes an empty fileset to prime state when a part uses override-prime, since the scriptlet path in _run_step returns no tracked contents. Bug confirmed still present in current code; unlabelled, no comments; downstream snapcraft issue still open.
73%