snaps with type: os should allow publishing of .manifest files
Bug #1608432 reported by
Oliver Grawert
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
Colin Watson | ||
Snapcraft |
Incomplete
|
Undecided
|
Unassigned | ||
launchpad-buildd |
Fix Released
|
Low
|
Colin Watson |
Bug Description
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://
Related branches
lp:~cjwatson/launchpad/snap-upload-check-filename
- William Grant (community): Approve (code)
-
Diff: 86 lines (+31/-10)2 files modifiedlib/lp/archiveuploader/snapupload.py (+13/-9)
lib/lp/archiveuploader/tests/test_snapupload.py (+18/-1)
lp:~cjwatson/launchpad-buildd/snap-upload-manifest
- William Grant (community): Approve (code)
-
Diff: 88 lines (+50/-3)3 files modifieddebian/changelog (+1/-0)
lpbuildd/snap.py (+4/-2)
lpbuildd/tests/test_snap.py (+45/-1)
Changed in snapcraft: | |
status: | New → Incomplete |
Changed in launchpad: | |
status: | Triaged → In Progress |
assignee: | nobody → Colin Watson (cjwatson) |
Changed in launchpad-buildd: | |
status: | Triaged → In Progress |
assignee: | nobody → Colin Watson (cjwatson) |
Changed in launchpad-buildd: | |
status: | In Progress → Fix Committed |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad-buildd: | |
status: | Fix Committed → Fix Released |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It seems this would be better handled by launchpad and having the manifest inside the snap in some predefined location like `meta/< name>.manifest`