User1: Hello infinity, how can we add the upgrade test cases to the tracker? http://iso.qa.ubuntu.com/qatracker/milestones/358/builds I don't think I have access to that kind of stuff ..
User2: User1 Erm, honestly not sure.  I seem to always have someone else do it.
User2: User3 ^
User3: User2 they are manually added through the web UI
User3: I can do it if you'd like
User3: Admin -> Builds, tick as appropriate, put current timestamp as version and select milestone
User3: added
User1: stgraber, many thanks :D thanks too infinity :D
User2: ^-- Best package name ever.
User4: User2 it's a paulwiseism
User5: +1 infinity :D
User5: !info check-all-the-things xenial-proposed
User6: Package check-all-the-things does not exist in xenial-proposed
User5: !info check-all-the-things
User6: Package check-all-the-things does not exist in wily
User5: huh, new package XD
User2: User4 Not surprising.
User7: it's an interesting package, for sure
User8: User9 actually i'm wrong - mokutil 0.3 fixes this.  it uses efivar to create the variables which understands how to work with immutable variables
User8: that's the right way to fix it
User8: uploaded it and sitting in unapproved
User9: User8 ok
User9: User8 I can't approve stuff, I'm not old enough ;)
User8: heh
User9: (and also I'm busy cursing vistaprint and trying to finish wedding invites
User2: User4 You own mokutil in Debian, want to review that upload in the queue and confirm that it's the same orig you'll use so merges aren't a mess, etc?
User2: The actual code delta is fairly reasonable, once you filter out all the crap. :P
User8: there wasn't a watch file otherwise i would have used uscan to fetch it, so I just grabbed and renamed orig from https://github.com/lcp/mokutil/releases
User2: User8 Yeahp, I'm sure that's fine, but since the Debian maintainer happens to be a member of the Ubuntu release team, I figured I'd let him do the honors. :)
User9: User8 can we copypasta the mokutil magic so that fwupdate is happy too?
User8: User9 i made fwupdate happy with some changes to it's install script
User9: oh, awesome, thanks
User8: sure
User2: tyhicks: Seriously?  *sigh*
User10: User2 Patch for innobase and innodb_memcached
User10: http://paste.ubuntu.com/15477836/
User2: User10 Lovely.  I'll use this to stress-test a PPC machine I just set up.
User11: oh f...
User11: could someone drop freeipa from the queue?
User11: was meant for a ppa :P
User2: User11 It's kinda already accepted and built.
User11: but in new?
User11: and proposed
User2: Yeah, I can delete it from proposed.
User11: cool
User11: thx
User2: User10 You win.
User2: User10 If you want a log to pass back to folks, http://lucifer.0c3.net/~adconrad/mysql-powerpc.log
User2: User10 I'll upload all of this to the archive shortly.
User10: Whooo
User2: User10 Thanks for the quick turnaround.
User10: No problem. I'll pass it on :)
User10: I know we have some tests failing on platforms we don't normally test as well, but not entirely sure if those tests are in the main suite, so will wait for the results of it.
User2: User10 Whatever testsuite is run at build time succeeded on all 7 arches.
User10: Hm, for some of the tests I know it's because some floating point calculations return slightly different results, so maybe those tests won't be run.
User2: User10 ibm-long-double arches (ppc* and s390*) definitely give slightly different fastfp results from the rest of the world.
User2: User10 But both passed here, so you must not be testing that at build time. :P
User2: User10 http://launchpadlibrarian.net/249671602/mysql-5.7_5.7.11-0ubuntu1_5.7.11-0ubuntu2.diff.gz
User10: I don't think dep8 will run any more tests than what's run at build time. Though I have some input on making the test runs faster, in which case we could make it run more tests :)
User2: User10 There's the final packaging diff, if you wanted to import that into your git tree.
User10: Thanks
User2: User10 IMO, the ideal situation is for the build-time tests to be as complete as possible, and the dep-8 tests to just touch enough important bits to know it didn't explode (ie: try each backend driver, try the client tools, dump/load a DB, call it good)
User2: User10 Since dep-8 is about making sure other deps don't break you at runtime, it's a) not really where deep unit testing belongs and b) run frequently, so 4h test runs suck.
User10: Yeah, true
User10: We tend to see failures there we don't see at build time, but in those cases it's usually a problem with the test, and not the package itself :)
User10: e.g. tests trying to write files in weird places
User10: Seems dep8 runs the same suite as build time
User2: Yeah, that's common, but not necessarily ideal. :)
User10: But that suite is fairly limited right now. I think it was cut back some time ago to reduce build time
User10: But if we can make it faster we could expand testing during builds
User2: I don't mind long builds, really.
User2: Not when there's a good reason, anyway.
User2: User12 Oops, I triggered a world rebuild right before I noticed you'd just done GNOME.  You'll get another one shortly. :P
User12: infinity, ha ok, guess it will be the same atleast!
User12: infinity, my respin (that you just trumped) is winning btw, so hopefully everything is good now, although of course something else will pop up
User13: cjwatson, I noticed something very strage with the archive.
User13: cjwatson, Yesterday I had some packages synced, one of them was mate-tweak 3.5.8.
User13: cjwatson, I saw is sitting in universe proposed.
User13: cjwatson, This morning mate-tweak 3.5.8 is no longer listed for proposed and only 3.5.7 is listed for xenial.
User13: I see the same behaviour with mate-dock-applet and mate-settings-daemon.
User14: User13 How curious, seems to have lost the copies.  I'll dig.
User13: ty
User14: NotOneError in BinaryPackageBuildSet.getBySourceAndLocation, how, er, exciting :-/
User14: Which is indeed borne out by https://launchpad.net/ubuntu/+source/mate-tweak/3.5.8-1
User14: And those are the three packages where I noticed duplicate announcements to xenial-changes yesterday
User14: I reckon these were each synced by you and by barry, and perhaps accepted simultaneously or something
User13: cjwatson, I have no repository super powers.
User15: I accepted those
User15: using queue accept
User15: which probably would have accepted both queue entries
User14: User13 syncing doesn't require superpowers, only upload permissions
User14: User13 anyway I'm not saying it was your fault, I'm just trying to work out the exact history
User13: cjwatson, I don't have any of those either.
User14: User13 Ah, Mirv sponsored it for you
User13: Yeah, I know you're not point the finger at me :-(
User13: Opps :-)
User13: I'm just explaining I didn't upload anything :-)
User16: gcc-defaults-ports (1.149ubuntu2 to 1.150ubuntu1)
User16: Maintainer: Debian GCC Maintainers
User16: Section: universe/misc
User16: 0 days old
User16: Impossible dependency: gcc-defaults-ports -> gcc-5-cross-ports/amd64
User16: Impossible dependency: gcc-defaults-ports -> gcc-5-cross-ports/i386
User16: Depends: gcc-defaults-ports gcc-5-cross-ports
User16: Valid candidate
User16: this looks odd. it references gcc-5-cross-ports, but that is not part in update_excuses
User14: User13 https://bugs.launchpad.net/launchpad/+bug/1560889 - I'm uploading rebuilds to work around this now, since that's by far the simplest option
User6: Launchpad bug 1560889 in Launchpad itself "Accepting multiple identical syncs from unapproved creates SPR with duplicate BPBs" [Critical,Triaged]
User13: cjwatson, Thanks.
User13: cjwatson, I have an RC issue as well :-(
User13: cjwatson, Could you sponsor an upload for me please?
User14: User13 no, sorry, need to go back to LP work
User13: cjwatson, OK.
User14: should be somebody else around who can
User14: (I mean, all the above is LP work, but YKWIM)
User13: Laney, I have an RC issue with Beta 2 image for Ubuntu MATE. Could sponsor and upload for me please?
User13: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-welcome/+bug/1560517
User6: Launchpad bug 1560517 in ubuntu-mate-welcome (Ubuntu) "ubuntu-mate-welcome 16.04.6 released critical fix [dsc attached]" [Undecided,New]
User14: User15 ^- penance for you
User15: k. ta
User17: User13 I managed to get your packages to explore corner cases of LP!
User13: Mirv, hah!
User13: cjwatson, Thanks for your help.
User18: good morning! would it be possible to release the above to the archive? fixes a FTBFS and gets our documentation to a final beta release ready state
User18: (xubuntu-docs)
User13: Ubuntu MATE needs some help please. We have complete uninstallable images.
User13: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-welcome/+bug/1560517
User6: Launchpad bug 1560517 in ubuntu-mate-welcome (Ubuntu) "ubuntu-mate-welcome 16.04.6 released critical fix [dsc attached]" [Undecided,New]
User13: I'm testing upgrades right now.
User13: Laney, thanks for the help!
User19: mapreri, ^^^
User20: User19 cool
User19: not sure why the syncs goes in unapproved, but well, somebody is accepting fast :D
User20: User19 that was indeed weird, since the package is not seeded anywhere
User14: User19 unapproved> because xenial is frozen
User14: that just lands everything in unapproved; the "not seeded" etc. logic is implemented by the auto-accept bot
User14: so that's also why you see "somebody" (a robot) accepting things quickly
User14: at least in some cases
User19: thanks
User19: :)
User13: cjwatson, Roughly how long will is take for accepted packages to transition from proposed to universe?
User14: User13 category error.  proposed and universe are different axes
User20: is this a good day to poke for a couple of RM?
User20: #1556226 & #1556229
User14: User13 if you mean proposed to release, I can't answer that, too many variables.  if nothing at all blocks them then probably an hour or two end to end, but it depends on lots of stuff
User13: cjwatson, Good enough for me. Thanks :-)
User13: Just working out when I maybe able to rebuild.
User21: cyphermox, willcooke: so there might be issues with oem mode not completing enduser setup and the slide show for the enduser setup will look at it on hardware after to confirm though E:JUGGLINGTOOMANYBALLSTODAY
User21: User9 two for you https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1560940 and http://launchpad.net/bugs/1546317
User6: Launchpad bug 1560940 in ubiquity (Ubuntu) "None matching mokutils passwords" [Undecided,New]
User6: Launchpad bug 1546317 in ubuntu-mate "Accessibility indicator is missing from ubiquity-dm at the "Try Ubuntu" dialog" [High,Confirmed]
User8: User21 bug 1569040 may actually be resolved with the fix for bug 1560764
User6: Error: Launchpad bug 1569040 could not be found
User6: bug 1560764 in linux (Ubuntu) ""fails to request state" when trying to perform actions in mokutil" [Undecided,Confirmed] https://launchpad.net/bugs/1560764
User8: We discovered some kernel behavior change on immutable variables that make mokutil unable to write variables properly
User21: User8 could be then we'll see when things are fixed there if it fixes this too then
User8: Not sure which point the variable is written in Python though, so that might be a second issue :)
User22: superm1, reading that bug you seem to be changing the way mokutils works to cope with the change; so there is nothing to do there /
User22: superm1, kernel side ?  correct ?
User8: User22 yes shouldn't have to do anything kernel side unless mokutil 0.3 isn't accepted for xenial
User22: superm1, heh well changing the kernel takes 2 days, so we'll not be doing that in time i suspect
User22: superm1, anyhow, who is making the decision on that
User8: User22  (per discussion with infinity last night) waiting on slangasek as he's Debian maintainer for mokutil
User22: superm1, ack thanks, just in case we do have to do something
User8: Yeah that's why left a Linux task on so you are in the loop
User21: User4 damn it I was close
User4: User8 could do with updating the text of the openssl exception in debian/copyright now that it's published upstream, but otherwise, looks good.  infinity accepting mokutil now
User23: infinity, are you aware of the new juju2 package trying to land in xenial?
User23: I wanted to make you aware and see if you had any questions / concerns
User4: User2 fyi, working through bug #1556241 now with mvo and cyphermox; this may only be affecting netboot installs today (because the seeded package is not yet in main therefore possibly only installed when doing a netboot install) and not require image respins, but I know that the ubuntu-snappy MIR is supposed to be getting finished this week...
User6: bug 1556241 in ubuntu-snappy (Ubuntu) "installer sets "iface encf5f0 inet dhcp" although a static IP address was preseeded" [Critical,Triaged] https://launchpad.net/bugs/1556241
User24: hello, can a release team member review the python-oslo.* and python-*client openstack dependency packages in the xenial review queue?
User24: infinity, ^
User25: User9 hey Mathieu, how are you?
User25: are there some beta critical things you need a hand with? I'll have about another hour today (not feeling too well), so if you have something reasonably small
User9: User25 hey, I'm alright
User9: you?
User9: there's nothing that small
User9: the most critical thing that needs help is upgrades, I think
User25: User9 ok, got some fever/infection since yesterday, going a bit slow; but I hope I'll be fully back tmw
User9: User25 no worries, get well soon!
User25: User9 any particular upgrade bugs to look into? these usually can still be looked into after the actual release
User9: User25 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1555237
User6: Launchpad bug 1555237 in ubuntu-release-upgrader (Ubuntu) "Upgrade from 14.04.4â 16.04 dies midway taking out the session." [Critical,In progress]
User13: Laney, cjwatson ubuntu-mate-welcome (and others) haven't been promoted to release yet. Am I being impatient or is their a problem with the package?
User13: *there
User14: needs manual unfreezing by a member of the release team
User14: you can see this on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ubuntu-mate-welcome
User14: (I did say the timing depended on a lot of things ...)
User13: Laney, please can yu unfreeze ubuntu-mate-welcome, mate-tweak, mate-dock-applet, eom and pluma please.
User13: cjwatson, Yes, you did. I've used my time to do some testing for Ubuntu proper :-)
User13: Laney, and mate-settings-daemon
User14: (you don't want mate-settings-daemon too?)
User14: aha
User15: User13 can you give me it in this format: unblock package1/version1 package2/version2 ... please?
 * Laney has a crisis and can't remember if that works with multiple packages per hint
User13: Laney, Wilco. One sec.
User13: Laney, unblock ubuntu-mate-welcome/16.04.6
User13: Laney, unblock mate-tweak/3.5.8-1build1
User13: Laney, unblock mate-dock-applet/0.70-1build1
User13: Laney, unblock mate-settings-daemon/1.12.1-2build1
User13: Laney, unblock  eom/1.12.2-2
User13: Laney, unblock pluma/1.12.2-2
User13: Laney, and thanks for helping.
User15: thx
User15: next time maybe pastebin would be easier for me to put in place :-)
User13: Laney, will do.
User15: pushed
User13: cjwatson, So are any packages automatically unfrozen right now?
User13: Laney, ty
User15: the block is for packages that are participating in this beta
User15: Things that get through it should be more or less the same as the ones that get auto accepted
User14: multiple packages per hint should work fine
User15: I didn't do it, out of fear of crashing britney :)
User15: there's only single-package hints in place currently
User4: hmm, boost binary rejects?
User16: slangasek, was me. mpi not building mpi
User9: jgrimm: rharper: User4 User2 release team: I'm sponsoring rharper's multipath-tools merge; it may be nice to land in beta if the server images are otherwise respun.
User2: User4 Eek.  It was snappy writing that interfaces snippet?  Whee.
User26: Could somebody approve mir 0.20.3+16.04.20160322-0ubuntu1 ?
User4: that is a question
User4: User2 ^^ fwiw I was just discussing this with kgunn.  It sounds like we do want to continue landing mir into xenial post-beta, but of course the lib is in all the images.  How do you want to play this?
User2: User4 I'd prefer to wait until after the beta so we don't keep respinning, unless there's a legitimately urgent reason it can't be tested from -proposed.
User2: User4 We can accept it, though, it should be blocked from migration.
User27: thanks guys
User4: User2 I think the main issue is that the train treats a silo as not "landed" until it's in xenial (not xenial-proposed), which blocks further development.  A one day delay seems ok here, but is there a reason not to let it into xenial if we aren't explicitly respinning for it?
User4: i.e. let it in xenial, let it get picked up or not with any subsequent respins
User2: User4 Well, it would make the source ISOs not match, but that's probably not the end of the world.
User23: infinity, can we talk about accepting juju2?
User28: User2 plan is to upload some postfix love "sometime this week"... guessing you'd prefer that be "after beta ships", true?
User2: User28 You can upload whenever, it just might stick in the queue for a day.
User2: User23 We can talk about it.
User28: User2 kewl
User29: Laney, hi
User21: User2 just remember the answer is no, you give in to balloons once and he'll never stop ;)
User30: ooh did the d-i/ubiquity issues get fixed?
User31: User30 you mean with the keyboard selection?  or a different issue?
User31: (there's several I'm aware of now)
User30: User31 well, any of the above :)
User2: User30 The not starting one was fixed.
User31: E: Ambiguous
User2: User31 What's the keyboard one?
User30: yay
User31: User2 cyphermox was going to look at it
User2: Kay.
User31: let me grab the bugs again
User2: User31 d-i, ubiquity, or both?
User31: User2 different bugs on each, but similar issue on both
User31: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1559507
User6: Launchpad bug 1559507 in debian-installer (Ubuntu) "Keyboard selection is missed" [High,Confirmed]
User31: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1549529
User6: Launchpad bug 1549529 in ubiquity (Ubuntu) "The keyboard is still installed as US-English even if another language is selected during the installation" [Undecided,Confirmed]
User31: d-i one was discovered by phillw on the lubuntu alt images, confirmed by me on server, and forwarded to matsubara for the d-i stuff bevcause we can't complete test cases for server
User9: yeah, I'm going to look at console-setup; first try to reproduce this in d-i
User31: (steps require us to manually selevct keyboard layout)
User2: User31 I just did a French ubiquity install, and got a horrible azerty keyboard out of it, so the second one seems to be fixed.
User13: Laney, cjwatson Thanks for you help today. The new Ubuntu MATE image appears to be working :-)
User2: User9 This might have been fallout from locales merge stuff, since we leverage locales to guess keyboards.  The ubiquity bug certainly seems unreproducible here.
User9: right, but it still should be checked
User31: User2 egads, ouch.  I can't attest to the ubiquity GUI one; i can only attest to what i've confirmed - which is the server/lubuntu-alternate d-i stuff
User30: so there's a possibility that the keyboard issues affecting both d-i and ubiquity are related?
User2: Oh, but this bug was reported long before I changed the world.  Hrm.
User31: User2 at least since the 19th it's been an issue, and i saw it on the ISOs on the 21st, for the d-i item
User2: Right, okay, so not my issue, though my issue may have compounded it briefly.
User9: User2 I agree ubiquity does what it should, testing d-i now
User2: User9 Note that the ubiquity bug seems deeply concerned specifically with Swedish keyboards, maybe that's extra broken somehow.
User9: (well, anyway, various French keyboards work, and so does the hebrew one
User2: (or maybe it relates to which langpacks are and aren't preinstalled)
User15: Blame Gunnar
User9: dah
User9: Swedish was always a bit of an issue
User2: Agreed, but they make good meatballs.
User9: admittedly, I didn't try that one
User9: the keyboard, not the meatballs
User9: good thing I'm so good at languages I can't read
User9: oh
User9: is Svenska Swedish?
User2: Thankfully, driving ubiquity doesn't really require reading.
User2: Svenska is Swedish, yes.
User9: it's some sort of casper issue I think
User9: at least for ubiquity
User9: If i pick Svenska at gfxboot, I will be able to continue with the install with no issues
User2: User9 If you pick it at gfxboot, casper creates the locale in the target before booting.
User9: yes
User9: and if you boot EFI, that won't happen
User2: User9 If you don't, then I assume something else is meant to be responsible later.
User9: right
User2: That "something else" would be d-i/ubiquity, no?
User9: the key is in a message that pops up in Swedish, about XKBLAYOUT or something
User9: yeah
User9: console-setup isn't quite doing what it should
User9: still, I reassigned the ubiquity bug to casper, and will try on d-i now, and if both behave the same I'll make it all console-setup
User31: User9 note the observed d-i issue is if you skip auto detection, you end up with no ability to select anything - it just skips and goes onto the next step
User31: fine if you are US/English format, poor if you're not.
User31: and matsubara confirmed the issue exists, so it tends to be something of a very evil thing, in my (tiny) opinion
User2: No disagreement on the evil.  Might be post-beta evil, though, if the fix isn't immediately obvious.
User31: User2 indeed.  though, if not fixed in beta, it should definitely be fixed before final
User31: otherwise we're going to have some very large complaints
User2: Quite.
User9: User31 I'm not worried about this kind of thing getting fixed
User31: neither am I, just an observation :)
User9: oh look, console-setup is really borked
User9: (crap, that's really my fault too)
User9: but it's probably on console-setup that is broken and evil
User9: *only
User2: Well, that's something.
User9: indeed, it hasn't changed much since wily
User9: maybe it isn't console-setup after all
User32: doko, release team.  what should we do about setuptools?  i guess first is to get dep8's passing.  can/should we unfreeze that once we do?
User32: pex 1.1.4-1 should pass, so that's just python-pbh5tools and pbgenomicconsesnsus amd64
User16: barry, what should be done?
User32: User16 oh, i just mean unblock it: Not touching package due to block request by freeze (contact #ubuntu-release if update is needed)
User16: barry, can't do that, I'm not in the release team
User32: User16 i just pinged you because you uploaded the new version.  presumably we want 20.3.1-1 in xenial, right?
User16: yes, wanted to have a recent version
User32: User16 excellent.  i'll take a look at dep8 failures
User16: slangasek, User2 didn't get any reply on my gcc-defaults-ports issue (update_excuses). Depends: gcc-defaults-ports gcc-5-cross-ports, but gcc-5-cross-ports doesn't show up in update_excuses
User13: cyphermox, Hi
User13: I've been testing Ubuntu and Ubuntu MATE.
User13: Just about to create a new bug, oem-config doesn't complete.
User9: ok
User13: After the system is prepared, the user setup runs, at the end of user setup the desktop is not started. Just a black screen.
User13: Same results on Ubuntu and Ubuntu MATE.
User13: Also a11y indicator is missing from all installs.
User13: And the is not network on oem-config user setup.
User13: *there is no network
User8: User13 possibly this: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1552621 ?
User6: Launchpad bug 1552621 in ubiquity (Ubuntu) "Can't login to desktop autometically after oem-config is finished on OEM mode" [Undecided,Confirmed]
User13: superm1, Thanks. That is exactly the issue.
User4: User16 gcc-defaults-ports - the dangling reference to gcc-5-cross-ports appears to be a britney bug, but the real problem is the error message above it, which I've never seen before.  Do these packages have cross-arch dependencies?
ubuntu-release
Ubuntu IRC