Tests

These are the tests that must pass before landing this new release in the -updates pockets of xenial, yakkety and zesty:

Plugins: Run the kernel manual tests documented in manual-tests.md. Build a snap with that uses meson.

Sources: Build a snap with a 7zip source.

Store: Run the release, close and status commands in snaps with channels.

Exploratory:

Build snaps with SNAPCRAFT_BUILD_INFO=1
Check that a snap can be build with the resulting snap/prime/snapcraft.yaml. Run all the snapcraft commands in different scenarios including failure conditions. Cleanbuild snaps with local and remote containers.

Is support for snapcraft build across architectures when classically confined also in consideration for this release? This is something that’s blocking adoption of kubernetes snaps upstream. lp:1674828

Yes, set DEB_ARCH to the architecture you are dumping. It is not like theArchitectureentry indebian/control`, which hints on where it is supposed to build, the snapcraft one actually sets the resulting architecture of the package to what is set in that field, given the confusion that general distro packagers have is the reason we don’t promote this feature, but it is exactly what you want; that is: