← Back to issue list

snaps with type: os should allow publishing of .manifest files

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1608432
Type
issue
State
open
Author
~ogra
Labels
lp-snappy qa-ok
Created
Updated
Closed
—

Current evaluation

Launchpad support for publishing .manifest files alongside snaps was reported fixed in stable revision 18187; the issue remains open administratively.

Suggested action: close resolved

Reason: The final comment explicitly reports “Fixed in stable r18187,” directly addressing the identified Launchpad-side restriction on uploading .manifest files. The author had also confirmed the expected top-level build location, so the requested publishing workflow was implemented.

Evaluated by: mr-cal-bot

Impact: 48 Quick Win: 25 Complexity: 43 Confidence: 96 Actionability: 90

Issue body

when we build an os snap using live-build (our standard method), then live-build produces a .manifest file that contains the list of packages (and their versions) used to assemble the rootfs. with cdimage builds we published these so people could verify what is contained in their install. snapcraft should have an option to release this file along with the .snap as well. http://cdimage.ubuntu.com/ubuntu-core/vivid/daily-preinstalled/current/vivid-preinstalled-core-amd64.manifest is an example of such a file

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 48
Quick Win: 25
Complexity: 43
Confidence: 96
Actionability: 90
close resolved Launchpad support for publishing .manifest files alongside snaps was reported fixed in stable revision 18187; the issue remains open administratively.
stealth/space-bunny-alpha
Impact: 35
Quick Win: 23
Complexity: 24
Confidence: 91
Actionability: 88
close resolved The concrete Ubuntu Core workflow was resolved by placing live-build’s package manifest beside the snap and accepting it in Launchpad r18187; no general Snapcraft .manifest option remains.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 11
Complexity: 40
Confidence: 60
Actionability: 60
keep open Feature request to allow publishing .manifest files (from live-build) alongside .snap for type:os snaps. Open 10 years with no comments or maintainer engagement.
qwen/qwen3.8-27b
Impact: 15
Quick Win: 9
Staleness: 95
Complexity: 40
Confidence: 70
Support Request: 10
close stale 2015 feature request to publish live-build .manifest files alongside type: os snaps so users can verify rootfs package contents. Zero comments or maintainer activity in ~10 years; the type: os snap type no longer exists in modern snapcraft.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 30
Confidence: 85
Support Request: 10
close stale Feature request to publish .manifest files alongside OS snaps. Issue has been inactive for over nine years with no maintainer response or priority labels.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 15
Confidence: 90
Support Request: 5
close stale Feature request to allow publishing .manifest files alongside type: os snaps. Unaddressed for ~10 years with no maintainer interaction or implementation.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 25
Confidence: 90
Support Request: 10
close stale Feature request to allow publishing .manifest files alongside OS snaps. Unaddressed for nearly 10 years with no maintainer interaction.

Update history

Date Change
created

Related work

  • Related To: snapcraft#4611 (confidence 86%)

    Later Snapcraft functionality generated a snap manifest, though it is a newer in-snap format rather than the original external .manifest upload.

Related issues

No related issues found above the similarity threshold.