daily-canary manifest does not include snaps

hmmm, would have to take a look at the way we generate the manifests. Possibly when we moved the seeded snaps from the main standard layer to the classic overlay layer, I assume we're still only generating the manifest for the standard one.

It's an interesting question now: what should we be printing out now? How to ensure we keep model and seeded snap deps in sync?

Should we move to generating separate .manifest files for each of the squashfs in the image? That would probably be the most helpful thing for forensics.

@Steve agreed, sounds like the best option here.

We do already generate manifests for each squashfs? But the issue is that snap-seed-parse.py cannot parse uc20 style seeds.

On the cdimage side we download and publish a single manifest, which is of dubious value now

This bug was fixed in the package livecd-rootfs - 23.10.26

---------------
livecd-rootfs (23.10.26) mantic; urgency=medium

  [ Łukasz 'sil2100' Zemczak ]
  * Update the enhanced-sb layer model to not preinstall the printing snaps,
    per changes to seeds. Live layer model not changed as it will go away
    soon per our staged changes.

  [ Michael Hudson-Doyle ]
  * Use a traditional seed.yaml style seed for the canary installer's live

 -- Łukasz 'sil2100' Zemczak <email address hidden> Mon, 28 Aug 2023 12:13:38 +0200