[Merge] ~philroche/ubuntu-seeds/+git/ubuntu:bugfix/mantic-cloud-minimal-time-daemon into ~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu:mantic

[Steve Langasek]

Because the metapackage is defined to include only packages from main, neither openntpd nor ntpsec is considered, only systemd-timesyncd and chrony.  And yes, it's probably evaluating them alphabetically.

I don't think it would actually fix the current behavior, but I would suggest that the seed should also blacklist chrony (using the syntax '* !chrony' in the cloud-minimal seed) to ensure it doesn't get picked up.  That may result in build failures, but is better than having a misbuild pull chrony into the minimal images.

Regardless, if the ./update script is resolving a virtual package to a real package and encoding that, that's also not what we want, so a real package is warranted.

> The new package will require an MIR too won't it. Even if it is a trivial package?

Let's not let process get in the way of designing this properly.  No, this would be a trivial package and would not require an MIR, an archive admin (hello) can just promote it.

> @Steve, what do you think? Can we make do with livecd-rootfs changes?

That's a step backwards from the goal of moving the image definition out of livecd-rootfs and into seeds.  -1.  It also conflicts with the goal of moving away from livecd-rootfs altogether in favor of ubuntu-image/imagecraft.  Let's just get this done right.  A time-daemon metapackage is trivial, you just need to coordinate it with systemd to get systemd-timesyncd to drop its Provides: (since time-daemon will Conflict: time-daemon and thus systemd-timesyncd will need to not provide it).
-- 
https://code.launchpad.net/~philroche/ubuntu-seeds/+git/ubuntu/+merge/449589
Your team Ubuntu Core Development Team is subscribed to branch ~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu:mantic.