docs/snapcraft-syntax.md should explicitly name the conditions under which a file is expected to end up in stage/ and snap/
Metadata
Current evaluation
Closed as stale by the Stale bot on 2017-05-19 after 60 days without activity; no fixing PR or commit was identified.
Resolution: closed stale
Reason: The Launchpad record states that the Stale bot closed it after 60 days of inactivity. Although a later test showed both files reaching prime, no documentation change was linked.
Evaluated by: mr-cal-bot
No scores available.
Issue body
https://github.com/ubuntu-core/snapcraft/blob/master/docs/snapcraft-syntax.md currently says:
- stage-packages (list of strings) A list of Ubuntu packages to use that would support the part creation.
This is vague and leaves unclear, under which conditions files from these packages (or their dependencies) can be expected into end in the final snap (that they _can_ end up in snap somehow is implied by the different description of build-packages explicitly denying that for those).
E.g. having
stage-packages:
- libxml2-dev
snap:
- usr/lib/x86_64-linux-gnu/*
- usr/include/libxml2/*
results in neither of:
usr/include/libxml2/libxml/parser.h
usr/lib/x86_64-linux-gnu/libxml2.so
to end up in the snap, while only the second ends up in the stage/ dir. (on snapcraft 2.2.2/xenial)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed as stale by the Stale bot on 2017-05-19 after 60 days without activity; no fixing PR or commit was identified. | |
| stealth/space-bunny-alpha | — | closed stale | Closed by the Stale bot on 2017-05-19 after 60 days without activity; no linked fixing PR or commit was identified. | |
| stealth/space-bunny-alpha | — | closed stale | Closed with no comments or documented resolution; no PR or commit is linked to clarify stage-packages file placement in stage/ and snap/. | |
| qwen/qwen3.6-35b-a3b | — | — | Requested documentation clarification on stage-packages file placement in stage/ and snap/. Closed without comments or resolution, indicating the request was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without action due to inactivity. The documentation request to clarify stage-packages and snap directive behavior was abandoned. No updates or fixes were implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The documentation request clarifying stage-packages file placement was abandoned due to prolonged inactivity, with no updates provided to the snapcraft-syntax.md file. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Documentation request clarifying stage-packages behavior was closed without changes, likely abandoned due to inactivity and superseded by updated Snapcraft guides. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1686484 snapcraft fails when two parts have the same file in the stage keyword | snapcraft (launchpad) | closed | Closed as stale in August 2026 after nearly nine years without a fix; the discussion provided no confirmed workaround. | |
| #1557018 Access from the build system to $SNAPCRAFT_STAGE directory when after: keyword is used in parts | snapcraft (launchpad) | closed | Closed as stale on 2016-05-29 after 60 days without activity; no resolving PR or commit was recorded. SNAPCRAFT_STAGE was later exported globally in #757. | |
| #1607249 docs/snapcraft-syntax.md should refer to source related syntax | snapcraft (launchpad) | closed | Closed as outdated; no documentation change, resolving PR, or commit was recorded. |