Hello Łukasz, or anyone else affected, Accepted ubuntu-image into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- image/1.1+17.04ubuntu3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Description changed: [Impact] With the current ubuntu-image 1.1, it is impossible for the package to migrate to the release pocket as the autopkgtests for armhf, ppc64el and - am64 will be failing (the snap.sh test). This test does not make sense - to be ran as part of .deb migration as it's testing snap buildability - - it's a bad idea to mix those two worlds. + arm64 will fail (the snap.sh test). This test does not make sense to be + run as part of .deb migration as it's testing snap buildability - it's a + bad idea to mix those two worlds. [Test Case] Make sure that all the autopkgtests pass for all architectures (with the snap.sh test skipped). [Regression Potential] None. This is only a test change. Skipping the test on package migration introduces no real possibility of regressions. Snap buildability is checked during the github source CI for each pull-request. Besides, snap buildability is a feature of the source that is not used by the .deb parts and is completely irrelevant to users. [Original Description] We have an autopkgtest called snap.sh that checks if we're able to properly build an ubuntu-image snap from the current source and that the resulting tool is usable. This test started failing with ubuntu-image 1.1 for armhf, ppc64el and s390x. By checking the test logs, this test was never really working for archs other than amd64 and i386. The snap never really got properly built and installed, and the test only passed because, for some reason, ubuntu- image was available as a deb (you can see it in the old logs by examining the ubuntu-image --version output, stating a non-snap version number). Starting with changes from 1.1, we now have some tests that make sure the deb is not installed. In theory building the ubuntu-image snap should be possible on all arches. In practice, on all the fancy archs basically the core snap is *always* failing to install with: error: cannot communicate with server: Post http://localhost/v2/snaps/core: dial unix /run/snapd.socket: connect: connection refused This doesn't seem to be a transient error. This causes ubuntu-image to not migrate. ** Changed in: ubuntu-image (Ubuntu Zesty) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-zesty ** Changed in: ubuntu-image (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1704979 Title: The snap.sh autopkgtest suite failes on non amd64/i386 arches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-image/+bug/1704979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
