Re: Do you have ubiquity slideshow changes for Disco?
Thanks for the reminder Mathieu - two merge requests have been made. One to fix the broken test slideshow in disco The second is UB specific - wording changes and picture changes TIA. On Wed, 6 Feb 2019 at 17:04, Mathieu Trudel-Lapierre wrote: > > Hi, > > Just an advance reminder if you want to make ubiquity slideshow > changes for the Disco release: make them as soon as possible, to give > time for translators to translate them. > > Kind regards, > > Mathieu Trudel-Lapierre > Freenode: cyphermox, Jabber: mathieu...@gmail.com > 4096R/65B58DA1 818A D123 0992 275B 23C2 CF89 C67B B4D6 65B5 8DA1 > > -- > ubuntu-devel mailing list > ubuntu-devel@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
authbind in platform/supported-sysadmin-common
Hello, On 12/02/2019 1:10 pm, Andreas Hasenack wrote: > Hi, > > while investigating removing authbind from the server-ship seed[1], we > noticed it's still included via platform/supported-sysadmin-common. I > tracked this back to 2008 when the file was created already with that > content, so no particular reasoning was logged in the commit. I would say you should check with IS if they are still using that package and need it supported. Cheers, Nafallo -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
beignet (and possibly other arch-specific packages) trapped in -proposed
britney tries to run autopkgtests on all architectures, including ones where the package under test does not exist: https://bugs.launchpad.net/britney/+bug/1815131 For most arch-specific packages this is likely to produce a harmless (other than wasted resources) "Always failed". However, beignet's tests are all skippable, and were added before Ubuntu autopkgtest had the skippable Restriction or the "all tests skipped" neutral state. Hence, autopkgtest thinks they used to pass on non-beignet architectures, when they never actually did: http://autopkgtest.ubuntu.com/packages/beignet As they currently fail as uninstallable, this is considered to be a regression trapping the package in -proposed: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#beignet As it thinks they used to *pass*, marking the tests skip-not-installable probably wouldn't be enough on its own. I could do that and also add a "pass if beignet doesn't exist here, skip if it does" test (Test-Command: true, Depends: @, Conflicts: @, Restrictions: skip-not-installable ? though I haven't actually tried that), but that feels silly, and would also make beignet skip rather than fail if it became uninstallable on an architecture where it does exist. Please let beignet out of -proposed: https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1815014 and consider checking whether any other packages are in a similar state. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
