[00:05] <flexiondotorg> infinity, Well done. You can have that sleep now ;)
[00:06] <infinity> flexiondotorg: Not until I verify a bunch of bits and send an email.
[00:06] <infinity> flexiondotorg: But yeah, close.
[00:06] <flexiondotorg> I posted my release notes. Time for sleeping...
[00:06] <infinity> flexiondotorg: G'night. :)
[00:06] <flexiondotorg> Zzz..
[00:41] <cyphermox> o/ am back.
[00:48] <infinity> cyphermox: Good, you can proof-read the release announcement.
[00:49] <infinity> cyphermox: http://paste.ubuntu.com/10686986/
[00:49] <infinity> cyphermox: Most of it is copy-and-waste from 6 months ago, but the hilighting of the two important bugs isn't.
[00:49] <infinity> Riddell: ^-- That wording seem sane to you?
[00:51] <doko> you start with "ubuntu team", but end with "ubuntu release team"
[00:52] <infinity> doko: Yeah, well.  The release team is sending the email, but the broader Ubuntu team is responsible for the 5 months of work that went into it.  At least, that's how I read it.
[00:54] <infinity> But if no one has any input on the wording of the section about the two bugs, I'll just go click send. :P
[01:03] <Riddell> awooga
[01:23] <cyphermox> so, who's going to update the slideshow to get rid of the unicorn and replace it with a vervet or a reasonable facsimile?
[01:24] <infinity> cyphermox: Well, if we follow with tradition from last release, it'll be me, on release day.
[01:24] <infinity> cyphermox: So, let's not go with tradition and chase up some design people next week. :P
[01:49] <cyphermox> infinity: sorry to remove the fun work from your plate.
[02:34] <cyphermox> fwiw I just did a ubuntu oem install and the user got removed... it didn't quite work as well as it should have though, the reboot after running oem-prepare showed a userdel warning on screen on VT1, VT2 was fine to login, VT7 I can't remember.
[02:36] <cyphermox> I still can't make the casper eject prompt answer to enter, I'm still thinking it's some kind of issue in plymouth given that it works properly if I remove splash altogether; but I'm going to sleep on it
[02:36] <infinity> cyphermox: Interesting.  So maybe it's racy?
[02:36] <cyphermox> infinity: probably
[02:36] <cyphermox> like you said, more fun stuff to port to sytemd
[06:31] <Mirv> hey archive admins. again the train would like to bypass binNEW queue if I
[06:31] <Mirv> 'd push publish, so I'd like you to review the new doc/doc-html packages at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-028/+packages similar to what you would do if they were in NEW queue
[06:32] <Mirv> qtpim5-doc, qtpim5-doc-html, qtfeedbac5-doc, qtfeedback5-doc-html
[07:53] <jamespage> infinity, nudge re oslo packages in NEW (guess you've been a bit busy :-))
[10:07] <infinity> Mirv: Looks sane to me.
[10:09] <Mirv> thank you
[10:12] <infinity> Mirv: Oh, wait.  One thing I didn't check, were those docs previously shipped in other packages, or are they entirely new files?
[10:13] <infinity> Mirv: I see no Breaks/Replaces on anything, so I hope they're all new files.
[10:13] <Mirv> infinity: too late! but no not previously shipped anywhere.
[10:14] <infinity> Mirv: Mmkay, then +1 for having docs we didn't have before. :P
[10:14] <infinity> (I do wonder how often the modern user uses doc packages, but I'm sure someone does)
[10:14] <Mirv> thank you, again. the community team wants them in archives from where they can fetch their web documentation, and SDK team wants to include them in the Qt Creator index.
[10:15] <infinity> Maybe I'm weird, but I live in an old skool new skool mix where I look for a manpage, and if man can't help me, it's Google.  Very little in between.
[10:16] <Mirv> quite few people probably install html documentation and then point their browser to those instead of online copy that surely exists. but the inline .qch documentation in qt creator is useful so that one does not need to switch to browser.
[10:17] <infinity> Ahh, yeah, I assumed from the file extension that it was a help browser format.
[10:17] <infinity> Though, I think the most helpful thing one can do with help browsers is write about 300 pages on every single possible way your Internet connection might be broken and how to diagnose and fix it.
[10:18] <infinity> And then, Appendix A: Firefox, Appendix B: Google. :P
[10:19] <infinity> My parents, on the other hand, use in-app help extensively, and refuse to admit that strangers on the Internet might know the answers.
[10:19] <infinity> So, to each their own.
[17:47] <ianorlin> hmm id the cron job not back on?
[18:20] <ianorlin> I don't see cron jobs back on
[20:31] <infinity> ianorlin: Nope, I'll re-enable them.
[20:33] <elfy> where would you look to see? other than noticing nothing new on the tracker ...
[20:33] <infinity> elfy: crontab on a host no one has access to.
[20:34] <infinity> elfy: But re-enabled now.
[20:34] <elfy> ok :)
[20:34] <elfy> so - just noticing that nothing new is on the tracker for us meremortals :D
[20:36] <infinity> elfy: Sure, I enabled the cronjob, that didn't magically build new images.  They'll build at their scheduled times over the next day.
[20:37] <elfy> infinity: not quite what I meant - for me to see that - just seeing there's not been a new image on tracker is the way?
[20:37] <infinity> elfy: Well, tracker or the usual dated directories on cdimage, or the build logs on people if the builds are failing.
[20:37] <elfy> yep
[20:38] <elfy> I'd look on tracker first - usually bleary eyed
[20:38] <elfy> anyway - thanks :)
[21:02] <slangasek> infinity: I see that ubuntu-core arm64 builds are still failing, now with a keyserver.ubuntu.com connection failure.  is that RT still in progress?
[21:03] <infinity> slangasek: The RT still exists, I didn't push anyone to add a cowboy, since no one was attempting builds (or mentioning failures).
[21:03] <slangasek> infinity: not looking for a cowboy, but a proper fix
[21:03] <infinity> slangasek: Right, well the other firewall change was a cowboy, the RT is to make it permanent.
[21:03] <slangasek> yep
[21:04] <infinity> slangasek: But given backlogs, a cowboy is your best bet if you need the images working ASAP.
[21:05] <infinity> slangasek: Compounding the hilarity, lamont is working on replacing the firewall in question.
[21:06] <slangasek> ah fun
[21:06] <infinity> slangasek: The current one is, I believe, lucid-only hardware, so needs to go.  Much like chinstrap, and a few others.
[21:19] <lamont> infinity: the current one is actually post-lucid capable, but lucid needs to go, and that's a reboot, and the new one is just sitting there.  so rather than reboot for the outage, we're going to cutover for the possible non-outage
[21:20] <lamont> infinity: I have a littel more testing before it becomes a "hey, I think we can pretend it never happened" or "there will be a reboot of the firewall at $DATETIME"
[22:20] <infinity> lamont: Fair enough.
[22:21] <lamont> infinity: and the former case there is "brace for possible outage" mixed with some mitigation, depending on how scarry the cutover testing proves
[22:22] <lamont> infinity: all of which means: have you any pariticular dates in the next couple weeks that I should avoid for cutover day?
[22:24] <infinity> lamont: The sooner, the better, and have me on hand when you do it.
[22:24] <infinity> lamont: Don't want it to happen during release week nor, ideally, the week before.
[22:24] <infinity> lamont: So, sometime in the next two.
[22:24] <infinity> lamont: In the next two, or wait for a month, I guess.
[22:25] <lamont> ack.  I'll work on my testing between now and monday, for the additional reason of wanting to get the 4 laptops and the switch off my desk.
[22:25] <infinity> lamont: Most intense pain (at least for the buildds) can be mitigated by just stopping buildd-manager before you screw with firewalls, mind you.
[22:25] <lamont> infinity: that is a "definitely-do" step
[22:25] <infinity> lamont: But if this is kiwi (it is, right?), there's a lot more behind that, so I assume you need a better downtime plan than just "make the buildds happy".
[22:26] <lamont> yep
[22:26] <lamont> "Even if we do this as a seamless cutover, stop the buildd-manager while it's happening, and restart it after we're done. trivial step that saves worlds of pain if we trip."
[22:28] <lamont> infinity: and by "next two" you mean the weeks beginning 30 mar and 6 apr, yes?
[22:28] <infinity> lamont: Yeahp.
[22:28] <infinity> lamont: Anything later than that is probably "too late" until after release.
[22:29] <lamont> ack
[22:30]  * lamont put s"must be done by 9 apr" on that
[22:30] <infinity> lamont: Since we're talking firewalls, could I get you to cowboy something for slangasek on the current firewalls? :P
[22:30] <lamont> no
[22:31] <lamont> how many firewalls, how many commands?
[22:31] <infinity> lamont: Sadness.
[22:31] <infinity> lamont: 1SS buildds need to see keyserver.ubuntu.com:11371 TCP.  Not sure how many firewalls that is.  See RT#79768
[22:32] <infinity> lamont: My bet it it's only one firewall blocking it.
[22:32] <infinity> s/it it/is it/
[22:32] <lamont> ugh.  let me see if I can find you a victim
[22:33] <infinity> lamont: Anyhow, the real subject of RT#
[22:33] <infinity> Err.
[22:33] <infinity> lamont: Anyhow, the real subject of RT#79768 (normalize 1SS firewall setup with 3FP) should hopefully be on your radar for the cutover.
[22:33] <lamont> I assume that an RT got filed for it?
[22:33] <infinity> lamont: The above referenced RT, yes.