← Back to issue list

`primed-stage-packages` isn't in manifest.yaml when using override-prime

View original Github issue

Metadata

Project
snapcraft
Number
#5552
Type
issue
State
open
Author
mr-cal
Labels
Status: Triaged Type: Bug
Created
Updated
Closed
—

Current evaluation

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.

Suggested action: keep open

Reason: The issue is triaged (labeled Status: Triaged, Type: Bug) and explicitly blocked by upstream craft-parts issue #1122 which is still open. The current snapcraft code (parts.py:278) still delegates to craft-parts' get_primed_stage_packages, and no fix commits were found in either repo. The problem remains reproducible and relevant to core22+ users.

Impact: 35 Quick Win: 19.25 Staleness: 60 Complexity: 45 Confidence: 75 Support Request: 5

Issue body

### Bug Description When using `override-prime`, the `primed-stage-packages` entry in the `manifest.yaml` is never populated. This is due to an upstream issue in craft-parts (https://github.com/canonical/craft-parts/issues/1122). We've worked around this problem before by warning when `override-prime` is used (https://github.com/canonical/snapcraft/issues/4547). ### To Reproduce Build the snap below with `SNAPCRAFT_BUILD_INFO=y snapcraft` and inspect the manifest with and without the `override-prime` keyword. ### Environment Snapcraft 8.9.0 This affects core22+ since this is a craft-parts issue. ### snapcraft.yaml ```yaml name: my-snap-test version: '0.1' summary: A test snap to demonstrate primed-stage-packages description: | This is a simple snap to show how stage-packages are primed. grade: stable confinement: strict base: core22 parts: my-part: plugin: nil stage-packages: - curl override-prime: | craftctl default ``` ### Relevant log output ```shell n/a ``` ### Additional context _No response_

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 35
Quick Win: 19.25
Staleness: 60
Complexity: 45
Confidence: 75
Support Request: 5
keep 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.
qwen/qwen3.6-35b-a3b
Staleness: 65
Complexity: 40
Confidence: 85
Support Request: 10
keep open Bug: `primed-stage-packages` not populated in manifest.yaml when using `override-prime`. Caused by upstream craft-parts issue. Has workaround. Triaged, linked to internal ticket.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 25
Confidence: 75
Support Request: 10
keep open primed-stage-packages missing from manifest.yaml when using override-prime due to upstream craft-parts issue. Triaged bug, inactive for over a year, awaiting upstream resolution.
qwen3.6-35b-a3b-mtp-q6
Staleness: 75
Complexity: 30
Confidence: 85
Support Request: 5
keep open primed-stage-packages entry omitted from manifest.yaml when override-prime is used. Root cause is an upstream craft-parts bug. Status: triaged. Internal Jira ticket filed. Awaiting upstream resolution or a permanent workaround.

Update history

No update history recorded yet.

Related work

  • Blocked By: canonical/craft-parts#1122 (confidence 90%)

    Issue body explicitly states 'This is due to an upstream issue in craft-parts' and links to this issue, which is still open

  • Related To: canonical/snapcraft#4547 (confidence 80%)

    Referenced in the issue body as a previous workaround that warned when override-prime was used

  • Duplicate Of: snapcraft (launchpad)#2097440 (confidence 70%)

    Same bug reported on Launchpad: 'override-prime disables primed-stage-packages', also still open

Related issues

Issue Project State Summary Similarity
#2097440 override-prime disables primed-stage-packages snapcraft (launchpad) open 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.
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.
76%
#5998 `primed-stage-packages` in `manifest.yaml` loses architecture information snapcraft open primed-stage-packages in manifest.yaml drops foreign-arch qualifiers (e.g. :i386) while stage-packages keeps them. Root cause is in craft-parts origin tracking; a craft-parts PR (#1558) has since fixed it.
76%