> core20 snap builds started to fail now, as it installs a
> few more packages on top of base, and expects to maintain stable gids
In principle, the snap build should follow the changes in behavior in livecd-rootfs, rather than blocking us from making any changes; it's a sanity check against accidental drift. As Oliver says:
> adding a new entry to one of the readonly password
> db files is fine but requires changes in livecd-rootfs
> and an update of the expected md5sum ...
So it needs a separate confirmation for the snap builds to work, but I don't see any reason we should special case a revert for the ubuntu-base build.
> core20 snap builds started to fail now, as it installs a
> few more packages on top of base, and expects to maintain stable gids
In principle, the snap build should follow the changes in behavior in livecd-rootfs, rather than blocking us from making any changes; it's a sanity check against accidental drift. As Oliver says:
> adding a new entry to one of the readonly password
> db files is fine but requires changes in livecd-rootfs
> and an update of the expected md5sum ...
So it needs a separate confirmation for the snap builds to work, but I don't see any reason we should special case a revert for the ubuntu-base build.