← Back to issue list

Add a how-to for controlling package versions

View original Github issue

Metadata

Project
snapcraft
Number
#5918
Type
issue
State
open
Author
bepri
Labels
Type: Documentation
Created
Updated
Closed

Current evaluation

Doc request to add how-to for controlling package versions in snaps (PPAs, deadsnakes, compiling own libs). Target file package-provisioning.rst does not exist. Maintainer commented with user dialogue as source material ~9 months ago; no PR or further activity since.

Suggested action: keep open

Reason: The issue is labelled Type: Documentation, filed by maintainer bepri, and acknowledged by medubelko with captured user dialogue as source material. The target file docs/how-to/package-provisioning.rst does not exist in the repo, and while manage-dependencies.rst and reference/package-repositories.rst partially cover the topic, neither provides the dedicated how-to for controlling versions (PPAs, deadsnakes, compiling own dev libraries) that this issue requests. The documentation gap is still present, so the issue remains relevant despite ~9 months of inactivity.

Impact: 35 Quick Win: 24.5 Staleness: 62 Complexity: 30 Confidence: 72 Support Request: 20

Issue body

### Check existing issues - [x] I've verified that this request isn't described by any existing issues. ### Request Currently, it is a bit opaque which package versions one will get when packing a snap. It can only ever be inferred that for a core24 snap, Noble apt repositories are used for example. In addition, some examples such as "compile your own dev version of a library" and "use `package-repositories` to get `deadsnakes`" would be very helpful. ### Document location how-to/package-provisioning.rst

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 35
Quick Win: 24.5
Staleness: 62
Complexity: 30
Confidence: 72
Support Request: 20
keep open Doc request to add how-to for controlling package versions in snaps (PPAs, deadsnakes, compiling own libs). Target file package-provisioning.rst does not exist. Maintainer commented with user dialogue as source material ~9 months ago; no PR or further activity since.
qwen/qwen3.6-35b-a3b
Staleness: 65
Complexity: 15
Confidence: 80
Support Request: 10
keep open Request to add documentation on controlling snap package versions, including examples for dev builds and deadsnakes. Currently awaiting implementation after a maintainer comment captured relevant user dialogue.
qwen3.6-35b-a3b-mtp-q6
Staleness: 75
Complexity: 20
Confidence: 80
Support Request: 10
needs triage Request to add documentation on controlling snap package versions, pointing to how-to/package-provisioning.rst. Inactive for 209 days with no maintainer triage or assignment.
qwen3.6-35b-a3b-mtp-q6
Staleness: 60
Complexity: 10
Confidence: 85
Support Request: 0
needs triage Request to document how to control package versions during snap builds using PPAs, package-repositories, or source compilation. Currently open and awaiting documentation updates. A recent comment provides technical guidance to inform the new how-to.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft/snapcraft#5452 (confidence 75%)

    PR that created docs/how-to/crafting/manage-dependencies.rst, which partially covers dependency identification and overriding core dependencies but does not address version control via PPAs or compiling own libraries.

  • Related To: snapcraft/snapcraft#3221 (confidence 55%)

    Commit 'repo: install requested build-package versions' relates to the underlying mechanism for pinning build-package versions, relevant context for the documentation.

Related issues

No related issues found above the similarity threshold.