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

It seems this would be better handled by launchpad and having the manifest inside the snap in some predefined location like `meta/<name>.manifest`

i could surely do that, but that would mean that launchpad would have to unpack the .snap ... also snapcraft knows the proper package name and version, i.e.
https://code.launchpad.net/~snappy-dev/+snap/ubuntu-core/+build/2574

currently has ubuntu-core_16.04.1_s390x.snap,
former launchpad rootfs builds would have put ubuntu-core_16.04.1_s390x.manifest next to it.

(i would point to https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/xenial/ubuntu-core-system-image/+build/70717 but sadly LP removes the snaps after a few days, so only the manifests are left in these older builds)

This manifest file would be interesting for more than just the core snap-- it would be useful for app snaps and really anything that uses stage-packages since the manifest could then be examined for out-of-dateness of staged packages. This seems like it would be useful for more than just Launchpad builds and seems like snapcraft should handle it itself (AIUI, the Launchpad buildds use snapcraft to build snaps). Am I missing something?

El 09/08/16 a las 12:40, Jamie Strandboge escribió:
> This manifest file would be interesting for more than just the core
> snap-- it would be useful for app snaps and really anything that uses
> stage-packages since the manifest could then be examined for out-of-
> dateness of staged packages. This seems like it would be useful for more
> than just Launchpad builds and seems like snapcraft should handle it
> itself (AIUI, the Launchpad buildds use snapcraft to build snaps). Am I
> missing something?
>
Yes, we already have a bug for that ;-)

This is the manifest produced by live-build wrapped inside a part which is totally disconnected from snapcraft itself.

no, you are right, LP uses snapcraft ... but there is also code in launchpad-buildd missing to publish them currently ... for my usecase i agreed with colin to actually just make my build spit out a .manifest in the toplevel build dir next to the snap ... but that indeed only works when using a tool that creates these files so yes, i think it would make sense if snapcraft itself could also create them.

colin pointed to http://paste.ubuntu.com/22806674/ ... i'm currently preparing the ubuntu-core builds for putting the file into the right place, then this should just work...

the ubuntu-core build now puts the manifest into /build/ubuntu-core/
from a build log:
...
ls -l /build/ubuntu-core
total 36
-rw-r--r-- 2 root root 1010 Aug 29 10:50 Makefile
-rw-r--r-- 2 root root 432 Aug 29 10:50 README
drwxr-xr-x 2 root root 4096 Aug 29 10:50 cron-scripts
drwxr-xr-x 3 root root 4096 Aug 29 10:50 parts
drwxr-xr-x 2 root root 4096 Aug 29 10:50 prime
-rw-r--r-- 1 root root 245 Aug 29 10:50 snapcraft.yaml
drwxr-xr-x 2 root root 4096 Aug 29 10:50 stage
-rw-r--r-- 2 root root 7431 Aug 29 10:52 ubuntu-core_16.04.1_ppc64el.manifest
Staging livebuild
Priming livebuild
...

@colin: is this the location you need ? (or does it need to be one level up)

Yes, that's the right location.

I've just realised that we need a slight tweak to the Launchpad side as well to allow us to upload .manifest files without losing the check that at least one .snap file was uploaded.

Fixed in stable r18187 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18187>.