← 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

Open documentation request to explain base-specific APT versions and how to select or override them using PPAs such as Deadsnakes; current docs only mention package sources briefly.

Suggested action: keep open

Reason: The maintainer-authored, documentation-labeled request has a specific gap: the current dependency guide and package-repositories reference mention Ubuntu and PPAs but do not provide the requested version-selection workflow or examples. The proposed path was reorganized, but the comment supplies concrete guidance, so the documentation work remains valid and ready for implementation.

Evaluated by: mr-cal-bot

Impact: 42 Quick Win: 20 Complexity: 43 Confidence: 94 Actionability: 82

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
stealth/space-bunny-alpha
Impact: 42
Quick Win: 20
Complexity: 43
Confidence: 94
Actionability: 82
keep open Open documentation request to explain base-specific APT versions and how to select or override them using PPAs such as Deadsnakes; current docs only mention package sources briefly.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 17
Complexity: 20
Confidence: 70
Actionability: 70
keep open Documentation request to create a how-to guide on controlling package versions, including PPA usage and deadsnakes examples. File docs/how-to/package-provisioning.rst does not yet exist.
qwen/qwen3.8-27b
Impact: 35
Quick Win: 24
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.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft#5440 (confidence 96%)

    Documentation reorganization explains why the requested package-provisioning.rst path no longer exists.

  • Related To: snapcraft#5452 (confidence 96%)

    Build and staging dependency documentation was migrated into the current manage-dependencies guide, which partially discusses build environments but not version control.

Related issues

No related issues found above the similarity threshold.