[00:14] <amjjawad> 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 ..
[00:20] <infinity> amjjawad: Erm, honestly not sure.  I seem to always have someone else do it.
[00:20] <infinity> stgraber: ^
[00:21] <stgraber> infinity: they are manually added through the web UI
[00:21] <stgraber> I can do it if you'd like
[00:22] <stgraber> Admin -> Builds, tick as appropriate, put current timestamp as version and select milestone
[00:22] <stgraber> added
[00:26] <amjjawad> stgraber, many thanks :D thanks too infinity :D
[01:25] <infinity> ^-- Best package name ever.
[01:26] <slangasek> infinity: it's a paulwiseism
[01:26] <tsimonq2> +1 infinity :D
[01:26] <tsimonq2> !info check-all-the-things xenial-proposed
[01:26] <tsimonq2> !info check-all-the-things
[01:26] <tsimonq2> huh, new package XD
[01:27] <infinity> slangasek: Not surprising.
[01:27] <nacc> it's an interesting package, for sure
[02:43] <superm1> cyphermox: actually i'm wrong - mokutil 0.3 fixes this.  it uses efivar to create the variables which understands how to work with immutable variables
[02:43] <superm1> that's the right way to fix it
[02:43] <superm1> uploaded it and sitting in unapproved
[02:48] <cyphermox> superm1: ok
[02:48] <cyphermox> superm1: I can't approve stuff, I'm not old enough ;)
[02:48] <superm1> heh
[02:48] <cyphermox> (and also I'm busy cursing vistaprint and trying to finish wedding invites
[03:00] <infinity> slangasek: 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?
[03:01] <infinity> The actual code delta is fairly reasonable, once you filter out all the crap. :P
[03:09] <superm1> 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
[03:10] <infinity> superm1: 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. :)
[03:16] <cyphermox> superm1: can we copypasta the mokutil magic so that fwupdate is happy too?
[03:16] <superm1> cyphermox: i made fwupdate happy with some changes to it's install script
[03:17] <cyphermox> oh, awesome, thanks
[03:17] <superm1> sure
[03:36] <infinity> tyhicks: Seriously?  *sigh*
[06:30] <Skuggen> infinity: Patch for innobase and innodb_memcached
[06:30] <Skuggen> http://paste.ubuntu.com/15477836/
[06:31] <infinity> Skuggen: Lovely.  I'll use this to stress-test a PPC machine I just set up.
[07:04] <tjaalton> oh f...
[07:05] <tjaalton> could someone drop freeipa from the queue?
[07:05] <tjaalton> was meant for a ppa :P
[07:06] <infinity> tjaalton: It's kinda already accepted and built.
[07:06] <tjaalton> but in new?
[07:06] <tjaalton> and proposed
[07:06] <infinity> Yeah, I can delete it from proposed.
[07:06] <tjaalton> cool
[07:06] <tjaalton> thx
[07:32] <infinity> Skuggen: You win.
[07:33] <infinity> Skuggen: If you want a log to pass back to folks, http://lucifer.0c3.net/~adconrad/mysql-powerpc.log
[07:33] <infinity> Skuggen: I'll upload all of this to the archive shortly.
[07:36] <Skuggen> Whooo
[07:36] <infinity> Skuggen: Thanks for the quick turnaround.
[07:38] <Skuggen> No problem. I'll pass it on :)
[07:38] <Skuggen> 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.
[07:39] <infinity> Skuggen: Whatever testsuite is run at build time succeeded on all 7 arches.
[07:40] <Skuggen> 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.
[07:41] <infinity> Skuggen: ibm-long-double arches (ppc* and s390*) definitely give slightly different fastfp results from the rest of the world.
[07:41] <infinity> Skuggen: But both passed here, so you must not be testing that at build time. :P
[07:42] <infinity> Skuggen: http://launchpadlibrarian.net/249671602/mysql-5.7_5.7.11-0ubuntu1_5.7.11-0ubuntu2.diff.gz
[07:42] <Skuggen> 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 :)
[07:42] <infinity> Skuggen: There's the final packaging diff, if you wanted to import that into your git tree.
[07:43] <Skuggen> Thanks
[07:43] <infinity> Skuggen: 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)
[07:44] <infinity> Skuggen: 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.
[07:44] <Skuggen> Yeah, true
[07:45] <Skuggen> 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 :)
[07:45] <Skuggen> e.g. tests trying to write files in weird places
[07:46] <Skuggen> Seems dep8 runs the same suite as build time
[07:48] <infinity> Yeah, that's common, but not necessarily ideal. :)
[07:48] <Skuggen> But that suite is fairly limited right now. I think it was cut back some time ago to reduce build time
[07:48] <Skuggen> But if we can make it faster we could expand testing during builds
[07:49] <infinity> I don't mind long builds, really.
[07:49] <infinity> Not when there's a good reason, anyway.
[07:58] <infinity> darkxst: Oops, I triggered a world rebuild right before I noticed you'd just done GNOME.  You'll get another one shortly. :P
[08:06] <darkxst> infinity, ha ok, guess it will be the same atleast!
[08:10] <darkxst> infinity, my respin (that you just trumped) is winning btw, so hopefully everything is good now, although of course something else will pop up
[09:00] <flexiondotorg> cjwatson, I noticed something very strage with the archive.
[09:01] <flexiondotorg> cjwatson, Yesterday I had some packages synced, one of them was mate-tweak 3.5.8.
[09:01] <flexiondotorg> cjwatson, I saw is sitting in universe proposed.
[09:02] <flexiondotorg> cjwatson, This morning mate-tweak 3.5.8 is no longer listed for proposed and only 3.5.7 is listed for xenial.
[09:03] <flexiondotorg> I see the same behaviour with mate-dock-applet and mate-settings-daemon.
[09:22] <cjwatson> flexiondotorg: How curious, seems to have lost the copies.  I'll dig.
[09:23] <flexiondotorg> ty
[09:27] <cjwatson> NotOneError in BinaryPackageBuildSet.getBySourceAndLocation, how, er, exciting :-/
[09:28] <cjwatson> Which is indeed borne out by https://launchpad.net/ubuntu/+source/mate-tweak/3.5.8-1
[09:29] <cjwatson> And those are the three packages where I noticed duplicate announcements to xenial-changes yesterday
[09:29] <cjwatson> I reckon these were each synced by you and by barry, and perhaps accepted simultaneously or something
[09:31] <flexiondotorg> cjwatson, I have no repository super powers.
[09:32] <Laney> I accepted those
[09:33] <Laney> using queue accept
[09:33] <Laney> which probably would have accepted both queue entries
[09:33] <cjwatson> flexiondotorg: syncing doesn't require superpowers, only upload permissions
[09:33] <cjwatson> flexiondotorg: anyway I'm not saying it was your fault, I'm just trying to work out the exact history
[09:33] <flexiondotorg> cjwatson, I don't have any of those either.
[09:33] <cjwatson> flexiondotorg: Ah, Mirv sponsored it for you
[09:34] <flexiondotorg> Yeah, I know you're not point the finger at me :-(
[09:34] <flexiondotorg> Opps :-)
[09:34] <flexiondotorg> I'm just explaining I didn't upload anything :-)
[09:56] <doko> gcc-defaults-ports (1.149ubuntu2 to 1.150ubuntu1)
[09:56] <doko> Maintainer: Debian GCC Maintainers
[09:56] <doko> Section: universe/misc
[09:56] <doko> 0 days old
[09:56] <doko> Impossible dependency: gcc-defaults-ports -> gcc-5-cross-ports/amd64
[09:56] <doko> Impossible dependency: gcc-defaults-ports -> gcc-5-cross-ports/i386
[09:56] <doko> Depends: gcc-defaults-ports gcc-5-cross-ports
[09:56] <doko> Valid candidate
[09:57] <doko> this looks odd. it references gcc-5-cross-ports, but that is not part in update_excuses
[10:00] <cjwatson> flexiondotorg: https://bugs.launchpad.net/launchpad/+bug/1560889 - I'm uploading rebuilds to work around this now, since that's by far the simplest option
[10:00] <flexiondotorg> cjwatson, Thanks.
[10:00] <flexiondotorg> cjwatson, I have an RC issue as well :-(
[10:00] <flexiondotorg> cjwatson, Could you sponsor an upload for me please?
[10:01] <cjwatson> flexiondotorg: no, sorry, need to go back to LP work
[10:01] <flexiondotorg> cjwatson, OK.
[10:01] <cjwatson> should be somebody else around who can
[10:01] <cjwatson> (I mean, all the above is LP work, but YKWIM)
[10:01] <flexiondotorg> Laney, I have an RC issue with Beta 2 image for Ubuntu MATE. Could sponsor and upload for me please?
[10:01] <flexiondotorg> https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-welcome/+bug/1560517
[10:02] <cjwatson> Laney: ^- penance for you
[10:03] <Laney> k. ta
[10:05] <Mirv> flexiondotorg: I managed to get your packages to explore corner cases of LP!
[10:06] <flexiondotorg> Mirv, hah!
[10:06] <flexiondotorg> cjwatson, Thanks for your help.
[10:52] <bluesabre> 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
[10:52] <bluesabre> (xubuntu-docs)
[11:00] <flexiondotorg> Ubuntu MATE needs some help please. We have complete uninstallable images.
[11:01] <flexiondotorg> https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-welcome/+bug/1560517
[11:01] <flexiondotorg> I'm testing upgrades right now.
[11:25] <flexiondotorg> Laney, thanks for the help!
[11:33] <LocutusOfBorg> mapreri, ^^^
[11:34] <mapreri> LocutusOfBorg: cool
[11:41] <LocutusOfBorg> not sure why the syncs goes in unapproved, but well, somebody is accepting fast :D
[11:42] <mapreri> LocutusOfBorg: that was indeed weird, since the package is not seeded anywhere
[11:45] <cjwatson> LocutusOfBorg: unapproved> because xenial is frozen
[11:45] <cjwatson> that just lands everything in unapproved; the "not seeded" etc. logic is implemented by the auto-accept bot
[11:45] <cjwatson> so that's also why you see "somebody" (a robot) accepting things quickly
[11:45] <cjwatson> at least in some cases
[11:46] <LocutusOfBorg> thanks
[11:46] <LocutusOfBorg> :)
[11:47] <flexiondotorg> cjwatson, Roughly how long will is take for accepted packages to transition from proposed to universe?
[11:48] <cjwatson> flexiondotorg: category error.  proposed and universe are different axes
[11:48] <mapreri> is this a good day to poke for a couple of RM?
[11:48] <mapreri> #1556226 & #1556229
[11:48] <cjwatson> flexiondotorg: 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
[11:49] <flexiondotorg> cjwatson, Good enough for me. Thanks :-)
[11:49] <flexiondotorg> Just working out when I maybe able to rebuild.
[11:51] <davmor2> 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
[11:53] <davmor2> cyphermox: two for you https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1560940 and http://launchpad.net/bugs/1546317
[13:11] <superm1> davmor2: bug 1569040 may actually be resolved with the fix for bug 1560764
[13:12] <superm1> We discovered some kernel behavior change on immutable variables that make mokutil unable to write variables properly
[13:30] <davmor2> superm1: could be then we'll see when things are fixed there if it fixes this too then
[13:31] <superm1> Not sure which point the variable is written in Python though, so that might be a second issue :)
[13:32] <apw> 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 /
[13:32] <apw> superm1, kernel side ?  correct ?
[13:32] <superm1> apw: yes shouldn't have to do anything kernel side unless mokutil 0.3 isn't accepted for xenial
[13:33] <apw> superm1, heh well changing the kernel takes 2 days, so we'll not be doing that in time i suspect
[13:44] <apw> superm1, anyhow, who is making the decision on that
[13:46] <superm1> apw:  (per discussion with infinity last night) waiting on slangasek as he's Debian maintainer for mokutil
[13:46] <apw> superm1, ack thanks, just in case we do have to do something
[13:46] <superm1> Yeah that's why left a Linux task on so you are in the loop
[14:03] <davmor2> slangasek: damn it I was close
[14:03] <slangasek> superm1: 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
[14:17] <balloons> infinity, are you aware of the new juju2 package trying to land in xenial?
[14:20] <balloons> I wanted to make you aware and see if you had any questions / concerns
[14:23] <slangasek> infinity: 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...
[14:28] <coreycb> hello, can a release team member review the python-oslo.* and python-*client openstack dependency packages in the xenial review queue?
[14:29] <coreycb> infinity, ^
[14:56] <pitti> cyphermox: hey Mathieu, how are you?
[14:57] <pitti> 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
[15:01] <cyphermox> pitti: hey, I'm alright
[15:01] <cyphermox> you?
[15:01] <cyphermox> there's nothing that small
[15:01] <cyphermox> the most critical thing that needs help is upgrades, I think
[15:04] <pitti> cyphermox: ok, got some fever/infection since yesterday, going a bit slow; but I hope I'll be fully back tmw
[15:05] <cyphermox> pitti: no worries, get well soon!
[15:05] <pitti> cyphermox: any particular upgrade bugs to look into? these usually can still be looked into after the actual release
[15:05] <cyphermox> pitti: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1555237
[15:20] <flexiondotorg> 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?
[15:20] <flexiondotorg> *there
[15:20] <cjwatson> needs manual unfreezing by a member of the release team
[15:20] <cjwatson> you can see this on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ubuntu-mate-welcome
[15:21] <cjwatson> (I did say the timing depended on a lot of things ...)
[15:21] <flexiondotorg> Laney, please can yu unfreeze ubuntu-mate-welcome, mate-tweak, mate-dock-applet, eom and pluma please.
[15:22] <flexiondotorg> cjwatson, Yes, you did. I've used my time to do some testing for Ubuntu proper :-)
[15:22] <flexiondotorg> Laney, and mate-settings-daemon
[15:22] <cjwatson> (you don't want mate-settings-daemon too?)
[15:22] <cjwatson> aha
[15:22] <Laney> flexiondotorg: can you give me it in this format: unblock package1/version1 package2/version2 ... please?
[15:22]  * Laney has a crisis and can't remember if that works with multiple packages per hint
[15:23] <flexiondotorg> Laney, Wilco. One sec.
[15:23] <flexiondotorg> Laney, unblock ubuntu-mate-welcome/16.04.6
[15:24] <flexiondotorg> Laney, unblock mate-tweak/3.5.8-1build1
[15:24] <flexiondotorg> Laney, unblock mate-dock-applet/0.70-1build1
[15:25] <flexiondotorg> Laney, unblock mate-settings-daemon/1.12.1-2build1
[15:26] <flexiondotorg> Laney, unblock  eom/1.12.2-2
[15:26] <flexiondotorg> Laney, unblock pluma/1.12.2-2
[15:26] <flexiondotorg> Laney, and thanks for helping.
[15:27] <Laney> thx
[15:28] <Laney> next time maybe pastebin would be easier for me to put in place :-)
[15:28] <flexiondotorg> Laney, will do.
[15:28] <Laney> pushed
[15:28] <flexiondotorg> cjwatson, So are any packages automatically unfrozen right now?
[15:29] <flexiondotorg> Laney, ty
[15:30] <Laney> the block is for packages that are participating in this beta
[15:30] <Laney> Things that get through it should be more or less the same as the ones that get auto accepted
[15:30] <cjwatson> multiple packages per hint should work fine
[15:31] <Laney> I didn't do it, out of fear of crashing britney :)
[15:31] <Laney> there's only single-package hints in place currently
[15:47] <slangasek> hmm, boost binary rejects?
[15:52] <doko> slangasek, was me. mpi not building mpi
[16:08] <cyphermox> jgrimm: rharper: slangasek: infinity: 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.
[16:14] <infinity> slangasek: Eek.  It was snappy writing that interfaces snippet?  Whee.
[16:31] <AlbertA> Could somebody approve mir 0.20.3+16.04.20160322-0ubuntu1 ?
[16:31] <slangasek> that is a question
[16:32] <slangasek> infinity: ^^ 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?
[16:33] <infinity> slangasek: 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.
[16:33] <infinity> slangasek: We can accept it, though, it should be blocked from migration.
[16:33] <kgunn> thanks guys
[16:34] <slangasek> infinity: 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?
[16:34] <slangasek> i.e. let it in xenial, let it get picked up or not with any subsequent respins
[16:38] <infinity> slangasek: Well, it would make the source ISOs not match, but that's probably not the end of the world.
[17:16] <balloons> infinity, can we talk about accepting juju2?
[17:27] <lamont> infinity: plan is to upload some postfix love "sometime this week"... guessing you'd prefer that be "after beta ships", true?
[17:30] <infinity> lamont: You can upload whenever, it just might stick in the queue for a day.
[17:30] <infinity> balloons: We can talk about it.
[17:34] <lamont> infinity: kewl
[17:38] <ypwong> Laney, hi
[17:42] <davmor2> infinity: just remember the answer is no, you give in to balloons once and he'll never stop ;)
[17:47] <wxl> ooh did the d-i/ubiquity issues get fixed?
[17:47] <teward> wxl: you mean with the keyboard selection?  or a different issue?
[17:47] <teward> (there's several I'm aware of now)
[17:48] <wxl> teward: well, any of the above :)
[17:48] <infinity> wxl: The not starting one was fixed.
[17:48] <teward> E: Ambiguous
[17:48] <infinity> teward: What's the keyboard one?
[17:48] <wxl> yay
[17:48] <teward> infinity: cyphermox was going to look at it
[17:48] <infinity> Kay.
[17:48] <teward> let me grab the bugs again
[17:48] <infinity> teward: d-i, ubiquity, or both?
[17:48] <teward> infinity: different bugs on each, but similar issue on both
[17:48] <teward> https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1559507
[17:49] <teward> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1549529
[17:49] <teward> 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
[17:49] <cyphermox> yeah, I'm going to look at console-setup; first try to reproduce this in d-i
[17:49] <teward> (steps require us to manually selevct keyboard layout)
[17:49] <infinity> teward: I just did a French ubiquity install, and got a horrible azerty keyboard out of it, so the second one seems to be fixed.
[17:49] <flexiondotorg> Laney, cjwatson Thanks for you help today. The new Ubuntu MATE image appears to be working :-)
[17:50] <infinity> cyphermox: This might have been fallout from locales merge stuff, since we leverage locales to guess keyboards.  The ubiquity bug certainly seems unreproducible here.
[17:50] <cyphermox> right, but it still should be checked
[17:50] <teward> infinity: 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
[17:51] <wxl> so there's a possibility that the keyboard issues affecting both d-i and ubiquity are related?
[17:51] <infinity> Oh, but this bug was reported long before I changed the world.  Hrm.
[17:51] <teward> infinity: 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
[17:52] <infinity> Right, okay, so not my issue, though my issue may have compounded it briefly.
[18:00] <cyphermox> infinity: I agree ubiquity does what it should, testing d-i now
[18:01] <infinity> cyphermox: Note that the ubiquity bug seems deeply concerned specifically with Swedish keyboards, maybe that's extra broken somehow.
[18:01] <cyphermox> (well, anyway, various French keyboards work, and so does the hebrew one
[18:01] <infinity> (or maybe it relates to which langpacks are and aren't preinstalled)
[18:01] <Laney> Blame Gunnar
[18:01] <cyphermox> dah
[18:01] <cyphermox> Swedish was always a bit of an issue
[18:01] <infinity> Agreed, but they make good meatballs.
[18:01] <cyphermox> admittedly, I didn't try that one
[18:02] <cyphermox> the keyboard, not the meatballs
[18:02] <cyphermox> good thing I'm so good at languages I can't read
[18:03] <cyphermox> oh
[18:04] <cyphermox> is Svenska Swedish?
[18:04] <infinity> Thankfully, driving ubiquity doesn't really require reading.
[18:05] <infinity> Svenska is Swedish, yes.
[18:07] <cyphermox> it's some sort of casper issue I think
[18:08] <cyphermox> at least for ubiquity
[18:08] <cyphermox> If i pick Svenska at gfxboot, I will be able to continue with the install with no issues
[18:11] <infinity> cyphermox: If you pick it at gfxboot, casper creates the locale in the target before booting.
[18:12] <cyphermox> yes
[18:12] <cyphermox> and if you boot EFI, that won't happen
[18:12] <infinity> cyphermox: If you don't, then I assume something else is meant to be responsible later.
[18:12] <cyphermox> right
[18:12] <infinity> That "something else" would be d-i/ubiquity, no?
[18:12] <cyphermox> the key is in a message that pops up in Swedish, about XKBLAYOUT or something
[18:12] <cyphermox> yeah
[18:12] <cyphermox> console-setup isn't quite doing what it should
[18:13] <cyphermox> 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
[18:14] <teward> cyphermox: 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
[18:14] <teward> fine if you are US/English format, poor if you're not.
[18:15] <teward> and matsubara confirmed the issue exists, so it tends to be something of a very evil thing, in my (tiny) opinion
[18:17] <infinity> No disagreement on the evil.  Might be post-beta evil, though, if the fix isn't immediately obvious.
[18:18] <teward> infinity: indeed.  though, if not fixed in beta, it should definitely be fixed before final
[18:18] <teward> otherwise we're going to have some very large complaints
[18:19] <infinity> Quite.
[18:19] <cyphermox> teward: I'm not worried about this kind of thing getting fixed
[18:19] <teward> neither am I, just an observation :)
[18:20] <cyphermox> oh look, console-setup is really borked
[18:20] <cyphermox> (crap, that's really my fault too)
[18:21] <cyphermox> but it's probably on console-setup that is broken and evil
[18:21] <cyphermox> *only
[18:22] <infinity> Well, that's something.
[18:23] <cyphermox> indeed, it hasn't changed much since wily
[18:23] <cyphermox> maybe it isn't console-setup after all
[19:34] <barry> 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?
[19:35] <barry> pex 1.1.4-1 should pass, so that's just python-pbh5tools and pbgenomicconsesnsus amd64
[19:49] <doko> barry, what should be done?
[19:50] <barry> doko: oh, i just mean unblock it: Not touching package due to block request by freeze (contact #ubuntu-release if update is needed)
[19:54] <doko> barry, can't do that, I'm not in the release team
[19:55] <barry> doko: i just pinged you because you uploaded the new version.  presumably we want 20.3.1-1 in xenial, right?
[19:56] <doko> yes, wanted to have a recent version
[19:56] <barry> doko: excellent.  i'll take a look at dep8 failures
[20:00] <doko> slangasek, infinity: 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
[20:21] <flexiondotorg> cyphermox, Hi
[20:21] <flexiondotorg> I've been testing Ubuntu and Ubuntu MATE.
[20:22] <flexiondotorg> Just about to create a new bug, oem-config doesn't complete.
[20:22] <cyphermox> ok
[20:23] <flexiondotorg> After the system is prepared, the user setup runs, at the end of user setup the desktop is not started. Just a black screen.
[20:23] <flexiondotorg> Same results on Ubuntu and Ubuntu MATE.
[20:23] <flexiondotorg> Also a11y indicator is missing from all installs.
[20:23] <flexiondotorg> And the is not network on oem-config user setup.
[20:23] <flexiondotorg> *there is no network
[20:30] <superm1> flexiondotorg: possibly this: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1552621 ?
[20:31] <flexiondotorg> superm1, Thanks. That is exactly the issue.
[22:02] <slangasek> doko: 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?