Hello Dimitri, or anyone else affected, Accepted ubuntu-meta into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.361.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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! ** Changed in: ubuntu-meta (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial ** Changed in: ubuntu-meta (Ubuntu Zesty) Status: In Progress => Fix Committed ** Tags added: verification-needed-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1730647 Title: on s390x one should alway be able to manipulate z devices Status in ubuntu-meta package in Ubuntu: Fix Committed Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-meta source package in Zesty: Fix Committed Status in ubuntu-meta source package in Artful: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Committed Bug description: [Impact] * Currently s390-tools is not installed as part of the server seed, which leads to inconsistencies between manually installed systems with d-i and systems originating from cloud images - containers, cloud images, maas. d-i installs s390-tools, whilst the rest do not. However, s390-tools ship tooling to inspect, list, operate on z specific devices and should always be available across all of ubuntu, including containers, maas, etc. Hence seeding it to server seed. [Test Case] * s390x containers have s390-tools package installed * s390x cloud images have s390-tools package installed * s390x maas images have s390-tools package installed [Regression Potential] * This is calling ubuntu-meta update script only * The only other changes are those that have been introduced in other srus. * s390-tools is in main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1730647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
