[ubuntu/eoan-proposed] livecd-rootfs 2.607 (Accepted)

[Iain Lane]

livecd-rootfs (2.607) eoan; urgency=medium

  * snap seeding: Defer validation for regular image builds. When getting the
    list of snaps to include on an image via germinate, we process the snaps
    in alphabetical order. Currently we seed several packages `gnome-foo` and
    also `gtk-common-themes`, the default provider of `gtk-3-themes`. Since
    `gtk-common-themes` is alphabetically after `gnome-foo`, the `seed.yaml`
    we generate is invalid when we are part way through generating. What we
    really care about, though, is not that the `seed.yaml` is always valid at
    every step, but it is that it is valid at the *end* of seeding.  So for
    the germinate case, let's defer validation to happen once at the end.
    Other callsites of `snap_preseed`, where callers are careful to seed snaps
    in the right order, are unaffected by this.

Date: Mon, 02 Sep 2019 14:22:49 +0100
Changed-By: Iain Lane <iain.lane at canonical.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/livecd-rootfs/2.607
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 02 Sep 2019 14:22:49 +0100
Source: livecd-rootfs
Architecture: source
Version: 2.607
Distribution: eoan
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Iain Lane <iain.lane at canonical.com>
Changes:
 livecd-rootfs (2.607) eoan; urgency=medium
 .
   * snap seeding: Defer validation for regular image builds. When getting the
     list of snaps to include on an image via germinate, we process the snaps
     in alphabetical order. Currently we seed several packages `gnome-foo` and
     also `gtk-common-themes`, the default provider of `gtk-3-themes`. Since
     `gtk-common-themes` is alphabetically after `gnome-foo`, the `seed.yaml`
     we generate is invalid when we are part way through generating. What we
     really care about, though, is not that the `seed.yaml` is always valid at
     every step, but it is that it is valid at the *end* of seeding.  So for
     the germinate case, let's defer validation to happen once at the end.
     Other callsites of `snap_preseed`, where callers are careful to seed snaps
     in the right order, are unaffected by this.
Checksums-Sha1:
 7a3fc07f133050edd037011131fb6ad490f0f5dd 1571 livecd-rootfs_2.607.dsc
 d74d99723ae5615ca48311fdfa926221cbab39bd 129396 livecd-rootfs_2.607.tar.xz
 3667bc67cb7a1802945170f0d7ff1fbe97a17ecb 8156 livecd-rootfs_2.607_source.buildinfo
Checksums-Sha256:
 96a155c3a6f7912c841e58d819248c816b6b6b33b7f6a2e674fe3a8344468ea5 1571 livecd-rootfs_2.607.dsc
 c9e01038f33f5ba7e0307daebd7daf22fd8ff83ccdaf4eca604ee4775456096d 129396 livecd-rootfs_2.607.tar.xz
 2c1399ed6130720192c166c3e40f362fc97838709f0436af20256b7787b7a316 8156 livecd-rootfs_2.607_source.buildinfo
Files:
 ad9b49a64195327594b772bed72af5a9 1571 devel optional livecd-rootfs_2.607.dsc
 aac4e3e5d9c6e55aceb15088ceb0dfc5 129396 devel optional livecd-rootfs_2.607.tar.xz
 04718765867852b04d84532faef2cf7b 8156 devel optional livecd-rootfs_2.607_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEPQ77lee1I38W6CJY41LVxRxQQdQFAl1tKz4ACgkQ41LVxRxQ
QdSdVA//SyV7bLL2OJA1e1xEuWPscJnXql/tjC4Zs3J2K2+nKvLoL9N2Z2hIXkN8
LXsmj8P1zZDyUs4NcCT3BY0nKuD+n6B8bMxNILyllnZ7tV73m2P9B7fwiqPdyqOM
f//aJWSYd0f5t+TFzf03nUt107ZcJJiWy1Rd93+b3LRXhQISkRsf6RueZvHBYRgv
U9vTc3/MipMil01fRViRzsaUUEOlHFQEKn2OzMhNKbIlQM3l5sR9kZofDybh/iPx
x8I2Mvi4y/0ftrOQ7YPK1fP4gLgXM9/S1+1qn9XnB+4I6LjcuIf8EJoTzgc+nDl3
+EdstMX7xGG6NJ2OaYDzSSbi3kJsGVOAlIpum8Dj69jsEMu5nXFB0mhVgcv6WfNy
x+z82yK+1oUt1+U8JkH8WaH8kLWKAiOQwEnBkacmRqeZZwh+lQw7a7e2FjHcsW1A
a/SKwzYy2R9IdK9E6v1m1b2D8vCEOVH9aOxjiSMvG/9G7yOahCQOF2AsP/xjD9FG
qAhK/Un8kfHBYzY/S8de+1zN0ylXaZoHWTzBhwfe99dnDigC8dPc7Sn1DsaQWt2G
hNTEBqvuSZHbbGnx3g+WTFAqUlano+4kQLbKKVcjMDVoJdKApppPfo6k+nUkCQnI
pfRyk9grlbOE6T0umK+BjtxjDsMwV69uDeDWVx+p6iY7uQMIF5I=
=dS3m
-----END PGP SIGNATURE-----