[00:26] <lifeless> it would be nice, yes
[00:39]  * wgrant sobs
[00:40] <wgrant> (@ the bug-columns-related new sort orders)
[00:50]  * StevenK tries to work out what to get run on qas to generate mail to qa bug 114753
[00:50] <_mup_> Bug #114753: Team membership status change emails should be gender neutral <lp-registry> <qa-needstesting> <teams> <trivial> <Launchpad itself:Fix Committed by stevenk> < https://launchpad.net/bugs/114753 >
[00:50] <StevenK> Or where the staging mailbox password even is. I thought I had it locally. :-(
[00:50] <wgrant> Probably cronscripts/send-person-notifications.py
[00:54] <lifeless> wgrant: StevenK: would like your opinions on bug 897442
[00:54] <_mup_> Bug #897442: maintained packages page not up to date after several weeks <Launchpad itself:Triaged> < https://launchpad.net/bugs/897442 >
[00:55] <wgrant> lifeless: Aw, you're ruining all the fun.
[01:00] <lifeless> wgrant: howso?
[01:01] <wgrant> Asking me directly about derived distros omissions that I pointed out a year ago, so I can't just sadly and derisively laugh at it from the sidelines.
[01:01] <StevenK> I *think* that was due to the gina fallout
[01:02] <nigelb> Morning!
[01:02] <nigelb> I can't wait to ask bigjools about cricket.
[01:02] <lifeless> StevenK: so, fixed already?
[01:02] <lifeless> StevenK: or 'operational glitch not a bug' ?
[01:03] <wgrant> Not fixed.
[01:03] <wgrant> The solution is undefined, and probably unclear.
[01:03] <lifeless> ok
[01:03] <wgrant> And to some extent probably impossible.
[01:03] <lifeless> can one of you define the problem clearly in the description then ?
[01:03] <wgrant> It's very similar to the notification issue, which was only vaguely solved recently.
[01:04] <lifeless> the symptoms are fairly clear, but too high level :)
[01:13] <StevenK> nigelb: Oh, why?
[01:14] <lifeless> 370 tech debt bugs
[01:14] <lifeless> wgrant: StevenK: ^ [please to be updating the bug]
[01:15] <nigelb> StevenK: England bowled out in the second innings for 72.
[01:16] <StevenK> nigelb: Bwahaha
[01:16] <StevenK> #1 in the world my left foot
[01:16] <nigelb> Exactly.
[01:22] <lifeless> wheee httpbis goes insnae
[01:34] <wgrant> lifeless: Oh? I've not been following it much.
[01:34] <wgrant> What have they done now?
[01:35] <lifeless> its about to be recharted
[01:36] <lifeless> rechartered
[01:36] <lifeless> httpbis is done, now onto a new version of http
[01:36] <lifeless> you can imagine the long carried concepts that this is dragging out of the woodwork
[01:36] <lifeless> some good
[01:36] <lifeless> some, uhm, less
[01:36] <wgrant> Oh yes.
[01:42] <lifeless> ok, htf does bug 235168 remain open ??
[01:42] <_mup_> Bug #235168: Database user fiera needs access to table GPGKeys <lp-soyuz> <soyuz-build> <Launchpad itself:Triaged> < https://launchpad.net/bugs/235168 >
[01:43] <lifeless> StevenK: wgrant: you may know. We should be seeing massive failure unless its been worked around somehow.
[01:43] <wgrant> lifeless: It *does* have access to gpgkey.
[01:43] <wgrant> Perhaps the bug is that it shouldn't need it.
[01:44] <wgrant> But it clearly should.
[01:44] <lifeless> ok
[01:44] <lifeless> s s/needs/has/ then close invalid
[01:44] <wgrant> Let me just check when it was added.
[01:44] <wgrant> It was added the day after that bug was filed.
[01:45] <wgrant> By al-maisan
[01:45] <wgrant> So I think it can be closed, as it's not a bug.
[01:46] <lifeless> yay timeouts
[01:47] <lifeless> wgrant: so it has access to the gpgkeys table to find folk from keys?
[01:47] <wgrant> lifeless: Right.
[01:47] <lifeless> thanks
[01:49] <wgrant> lifeless: Any idea why we can now sort bugs by tag or spec name?
[01:50] <wgrant> They both seem only marginally useful, if that.
[01:50] <lifeless> the bugcolumn project decided that every shown field should be sortable
[01:50] <wgrant> O_o
[01:50] <wgrant> o_O
[01:50] <lifeless> so they can show the fields being shown as 'columns'
[01:50] <wgrant> -_-
[01:50] <lifeless> and they can be clicked on to sort.
[01:51] <wgrant> This didn't raise performance concerns?
[01:51] <wgrant> It's both somewhat useless, and likely to be very slow.
[01:51] <lifeless> I flagged that with the team, yes.
[01:51] <lifeless> I don't know if they have measured.
[01:52] <lifeless> The original idea was to allow arbitrary combinations of sorts.
[01:52] <lifeless> importance + age, etc.
[01:52] <wgrant> Sure.
[01:52] <wgrant> That sort of thing is useful.
[01:52] <lifeless> Yes, but complex and hard to get right performance wise.
[01:52] <wgrant> But it's made a little more challening by having 9 billion combinations.
[01:52] <wgrant> 8.7 billion of which aren't useful
[01:52] <lifeless> sure
[01:53] <lifeless> anyhow, so a) the squad were, AFAIK, aware that performance is a factor
[01:53] <wgrant> I have a feeling that even ordering by assignee will no longer work for Ubuntu.
[01:53] <lifeless> and b) I don't know if they profiled the resulting queries.
[01:53] <wgrant> Indeed it does not.
[01:54] <lifeless> timeout?
[01:54] <wgrant> of course :)
[01:54] <lifeless> file a bug
[01:54] <lifeless> this probably needs revisiting
[01:54] <wgrant> I am trying to work out how to safely do the fact table.
[01:54] <wgrant> But there's about 10 useless sort orders that I really don't want to have to test against it.
[01:57] <wgrant> lifeless: Hah
[01:58] <wgrant> lifeless: Did you know that there are still several per-bug query regressions left in the new bug listings?
[01:58] <lifeless> I didn't
[01:58] <lifeless> please file a bug and flag for deryck
[01:58] <wgrant> I did a month ago :/
[01:58] <lifeless> That got fixed, I thought.
[01:58] <wgrant> So did I.
[01:59] <wgrant> Ah, no.
[01:59] <wgrant> Bug #901122
[01:59] <_mup_> Bug #901122: New bug listings need to preload more attributes <bug-columns> <regression> <timeout> <Launchpad itself:In Progress by deryck> < https://launchpad.net/bugs/901122 >
[01:59] <wgrant> It's the other one, with duplicated 4s queries, that got fixed.
[02:00] <wgrant> Nearly 2 months ago.
[02:00] <lifeless> ok
[02:01] <lifeless> I have a clal planned with deryck this week anyhow
[02:01] <lifeless> I will mention that bug
[02:01] <wgrant> Does the 5s policy not apply in weaker form to that sort of thing?
[02:01] <wgrant> Something like "can't release with known trivial performance regressions"?
[02:01] <StevenK> Hah
[02:02] <lifeless> yes,
[02:02] <rick_h> lifeless: wgrant I know he reported on it a couple of times during stand ups
[02:02] <lifeless> we're not meant to release with known regressions
[02:02] <rick_h> it's on our kanban and in coding
[02:02] <lifeless> and all new pages are meant to be 5s capped.
[02:02] <lifeless> we haven't yet agreed to 'changed pages need to be 5s capped' - I don't think we are quite ready for that.
[02:03] <wgrant> lifeless: Sure, but "changed pages shouldn't have obvious easily-fixed speed regressions" seems reasonable enough.
[02:03] <lifeless> wgrant: I think francis would support 'changed pages should not have regressions'
[02:04] <lifeless> we don't have a formal checkpoint for this today
[02:04] <lifeless> (and in fact if you check the current release process stuff, squads are not meant to rotate while there are regressions
[02:05] <lifeless> but we're not following through all that well yet; still figuring out the mechanics
[02:05] <wgrant> I've given up on pointing that bit out :)
[02:06] <lifeless> please don't give up
[02:06] <lifeless> sometimes just a reminder is very useful
[02:06] <wgrant> We conciously regressed with speed, usability, information density regressions.
[02:06] <wgrant> Presumably because the feature was dragging on.
[02:06] <wgrant> s/regressed/released/
[02:07] <lifeless> I was only aware that the latter one was considered
[02:08] <wgrant> Fortunately for products it's somewhat usable.
[02:08] <wgrant> As you can turn off location display.
[02:08] <wgrant> And get near-normal density.
[02:08] <wgrant> For Ubuntu you can't :/
[02:33] <lifeless> hates isp.
[02:34] <lifeless> StevenK: \o/ 114753
[02:34] <StevenK> lifeless: I think you should your ISP exactly what you think of them.
[02:34] <StevenK> At length.
[02:34] <StevenK> Sigh. Should *tell* your ISP
[02:34] <lifeless> StevenK: I've started whinging on twitter to them when it goes :P
[02:35] <StevenK> Oh sure, *that* will help.
[02:35] <lifeless> makes me feel better
[02:36] <lifeless> and back to the bug triage. wgrant - could you please comment on / update the description for bug 897442 ?
[02:36] <_mup_> Bug #897442: maintained packages page not up to date after several weeks <Launchpad itself:Triaged> < https://launchpad.net/bugs/897442 >
[02:39] <lifeless> hah, crazy, my if-I-had-to-choose tweet is *still* being retweeted
[02:40] <lifeless> to another 3K folk today. *boing*
[02:50] <wgrant> lifeless: Which tweet?
[02:54] <lifeless> https://twitter.com/#!/rbtcollins/status/160126945995141122
[02:55] <nigelb> ohyeah, I RT'd that the other day.
[02:55] <lifeless> .
[02:55] <lifeless> .
[02:55] <lifeless> .
[02:55] <james_w> hi lifeless
[02:55] <wgrant> Ah
[02:56] <lifeless> james_w: hi
[02:56] <james_w> hi wgrant
[02:56] <james_w> I've been looking at getting Django to include the oops id in the response body
[02:56] <james_w> I have an approach that does it, but it has to use thread local storage
[02:56] <wgrant> Hi james_w.
[02:57] <lifeless> james_w: can't you use the wsgi context?
[02:57] <james_w> hmm, possibly
[02:57] <james_w> and then get it back out from the report in the error_render function
[02:58] <lifeless> james_w: I was suggesting, at the point you decide you are oopsing (which is probably the django error handler, which is inside the wsgi shell)
[02:59] <james_w> at that point we can either publish the oops directly, dropping some of oops_wsgi from the stack
[02:59] <lifeless> that you use a timeuuid, (uuid1?) back that to a unicode string, stash it in the wsgi context in a oops.id or oops.context['id'] or some such
[02:59] <lifeless> and change the oops-wsgi default handlers to honour if from there, if found.
[03:00] <james_w> that would work, but would break publish_only_new
[03:00] <james_w> I wonder if that should use some mechanism other than the id to decide if the report has already been published?
[03:00] <lifeless> uhm
[03:01] <lifeless> I wouldn't publish directly, theres no value in doing so
[03:01] <lifeless> and you'd have to duplicate logic
[03:01] <james_w> yeah
[03:01] <lifeless> (consider that we also want to make oopses for soft timeouts, local 404's etc)
[03:01] <lifeless> the fact that django isn't structured like a wsgi app is a nuisance :)
[03:02] <james_w> yes
[03:05] <james_w> would a published key in the report work sufficiently well for publish_only_new to do the amqp->datedir fallback?
[03:10] <lifeless> we'd need to teach it
[03:10] <lifeless> e.g. have a requested_id field or some such
[03:11] <lifeless> allocation in publish() is very clean, but then we get this nasty django interaction
[03:13] <wgrant> lifeless: I've commented on that bug, but it has probably only confused matters :)
[03:13] <lifeless> one way would be to track 'published' separately
[03:13] <lifeless> (e.g. in a key, or as a separate publishing-state-variable)
[03:13] <wgrant> (most interpretations of the bug would have previously been very confused, but in too simple a fashion)
[03:14] <lifeless> another is to have a helper in the oops code that publishers can use to decide what id to use (see also the related 'preserve id' flag to DateDirRepo
[03:14] <lifeless> wgrant: thanks
[03:47] <lifeless> wgrant: whats the jargon for the 'functionality to which lifeless refers'
[03:49] <spm> 'impossibilities and other fantastic legends'
[03:49] <nigelb> zing!
[03:50] <StevenK> Haha
[03:50] <wgrant> lifeless: Not sure it has a name.
[03:51] <StevenK> +1 for calling it what spm did
[03:51] <spm> :-)
[03:51] <nigelb> All hail spm, the well-timed.
[03:51] <spm> years of practice
[03:51] <spm> :modest:
[03:52] <StevenK> lifeless: O hai. Can I please kill the maverick packages in the LP PPA?
[03:52] <StevenK> By rights we should kill natty too, but one DAS at a time
[03:52] <wgrant> There are still natty users
[03:53] <wgrant> I don't think anyone's still on maverick, though.
[03:53] <wgrant> In fact I think maverick's broken.
[03:53] <lifeless> StevenK: L, O and P should be all we need
[03:53] <lifeless> wgrant: what natty users?
[03:53] <wgrant> At least one LP dev uses natty.
[03:53] <lifeless> wgrant: !cite
[03:56] <StevenK> lifeless: There is an already existing Obsolete PPA which contains a bunch of hardy stuff, I'll copy the maverick packages there and then delete them
[03:56] <lifeless> coolio
[03:56] <lifeless> given the canonical policy for O/S use
[03:57] <lifeless> I wouldn't bother asking me about this, JFDI :) - after checking on buildbot and any non-prod machines, of course [as prod machines use the losa repo...)
[03:57] <spm> s/losa/is/
[03:58] <lifeless> 6/1 1/2 other
[03:58] <StevenK> lifeless: buildbot does not use the PPA
[03:58] <StevenK> ec2 and dev machines only
[04:00]  * StevenK gets distracted by changing the displayname of the obsolete PPA to something better
[04:00] <lifeless> StevenK: blargh, I knew whereof I meant.
[04:01] <lifeless> wgrant: what dev uses natty?
[04:01] <wgrant> lifeless: I don't recall, but I'm pretty sure it came up at the Thunderdome.
[04:02] <StevenK> I can recall hearing it too
[04:02] <StevenK> I think it was one of the mac fanbois
[04:02] <wgrant> That makes sense, yes.
[04:03]  * StevenK waits for the copied packages to be published before deleting them
[04:05] <lifeless> so, tough luck for them, really.
[04:05] <lifeless> we should all be dogfooding precise in the next month or so anyhow.
[04:05] <lifeless> and everyone should have gotten onto O in similar fashion.
[04:06] <StevenK> lifeless: I'll be mailing about Maverick after the fact, the mail warns about Natty.
[04:07] <lifeless> thanks
[04:08] <lifeless> lets aim to clean natty and O up a week or so after P ships.
[04:08] <lifeless> clean sweep
[04:08] <StevenK> That late? I was going to clean up natty this week
[04:08] <lifeless> oh, sure
[04:08] <lifeless> I was figuring you wouldn't want to fiddle with it again so soon
[04:08] <lifeless> but if you're inclined, I won't get in the way :)
[04:09] <StevenK> Meh, most of it is waiting for the PPA publisher
[04:09] <wgrant> StevenK: Why?
[04:09] <wgrant> You don't need to wait.
[04:09] <StevenK> wgrant: I'd prefer them to be published in the other PPA before I delete them from the first.
[04:10] <wgrant> Unnecessary, unless you're going to take more than 7 days to copy them.
[04:10] <StevenK> They just published, anyway.
[04:11] <StevenK> "Source and binaries deleted by Steve Kowalik request:"
[04:12]  * StevenK eyerolls
[04:27] <StevenK> wgrant: https://code.launchpad.net/~stevenk/launchpad/ppa-packages-deletion-grammar/+merge/90646https://code.launchpad.net/~stevenk/launchpad/ppa-packages-deletion-grammar/+merge/90646
[04:27]  * StevenK glares at his mouse
[04:27] <StevenK> wgrant: https://code.launchpad.net/~stevenk/launchpad/ppa-packages-deletion-grammar/+merge/90646 that is
[04:28] <wgrant> StevenK: Needs fixing, but you have to work out why :)
[04:28] <wgrant> It's not a bug you've introduced.
[04:29]  * StevenK peers at wgrant
[04:30] <StevenK> Can I have a clue? :-)
[04:30] <StevenK> messages = []; messages.append() is a horrid way of expressing it, so I've fixed that too
[04:30] <wgrant> It's not in the test, or the comment.
[04:31] <wgrant> I thought that was a reasonable way to do it, but I'm not too fussed.
[04:31] <lifeless> gnar
[04:31] <lifeless> I can't find the bug about bug 1
[04:31] <_mup_> Bug #1: Microsoft has a majority market share <ubuntu> <Clubdistro:Confirmed> <Computer Science Ubuntu:Confirmed for compscibuntu-bugs> <dylan.NET.Reflection:Invalid> <dylan.NET:Invalid> <EasyPeasy Overview:Invalid by ramvi> <Ichthux:Invalid by raphink> <JAK LINUX:Invalid> <LibreOffice:In Progress by bjoern-michaelsen> <Linux:New> <Linux Mint:In Progress> <The Linux OS Project:In Progress> <metacity:In Progress> <OpenOffice:In Progress by lh-m
[04:31] <StevenK> wgrant: Your issue is with the prose, then?
[04:32] <wgrant> No, it's a code bug.
[04:34] <lifeless> escaping?
[04:34] <wgrant> Bingo.
[04:34] <lifeless> cause we like xss ?
[04:34] <StevenK> Ah
[04:35] <StevenK> +        messages = [
[04:35] <StevenK> +            '<p>Source and binaries deleted by %(self.user.display_name)s:']
[04:35] <StevenK> wgrant: ^
[04:36] <lifeless> StevenK: ?
[04:36] <wgrant> wut
[04:36] <lifeless> StevenK: nice troll :P
[04:36] <lifeless> StevenK: display_name is untrusted data
[04:36] <lifeless> StevenK: you are assembling html.
[04:36] <StevenK> Obviously
[04:37] <lifeless> StevenK: so you need to html entity escape the display name to stop monkey business
[04:37] <wgrant> No.
[04:37] <StevenK> But that pattern is used like five lines down
[04:37] <StevenK>         messages.append("<p>Deletion comment: %(comment)s</p>")
[04:37] <lifeless> StevenK: oh yay, even more holes
[04:37] <StevenK> So I guess I get to fix both ...
[04:38] <lifeless> StevenK: actually, let me rephrase - that second one depends on the value of comment when the string is substituted
[04:38] <wgrant> dafuq.
[04:38] <wgrant>         # Replace the 'comment' content added by the user via structured(),
[04:38] <StevenK> comment = data.get('deletion_comment')
[04:38] <wgrant>         # so it will be quoted appropriately.
[04:38] <wgrant> I DO NOT GET IT
[04:38] <wgrant>         messages.append("<p>Deletion comment: %(comment)s</p>")
[04:38]  * wgrant blame
[04:38] <StevenK> wgrant: Shall I just go on a rampage and delete this code for being utter rubbish?
[04:39] <wgrant> No, you should fix it, while I write bzr blamestab.
[04:39] <StevenK> cprov
[04:40] <StevenK> wgrant: Hm, it is wrapped in structured() a few lines down?
[04:40] <wgrant> Oh
[04:40] <wgrant> So it is
[04:40] <wgrant> So yes, that bit is correct.
[04:40] <wgrant> (but that was only fixed relatively recently)
[04:41] <wgrant> In r5945
[04:41] <StevenK> Hah, recently
[04:41] <StevenK> wgrant: http://pastebin.ubuntu.com/822187/
[04:41] <wgrant> Amusingly there were two identical vulnerabilities in the preceding 10 lines, which were not fixed.
[04:42] <wgrant> StevenK: That's fixed one of them.
[04:42] <StevenK> And the source displayname?
[04:42] <wgrant> That one is probably not presently exploitable, due to some constraints in our current data model, but yes.
[04:42] <StevenK> Right
[04:42] <StevenK> I'm not sure how to fix that in the same way, given the loop
[04:43]  * StevenK wraps source.displyname in structured()
[04:43] <wgrant> Right, it may be best to use the nested structured() support that you added a while back.
[04:44] <StevenK> Like I just did? :-)
[04:48] <StevenK> Hmmm, wrapping source.displayname in structured didn't work
[04:49] <wgrant> How did you try it?
[04:49] <StevenK> % structured(source.displayname) effectively
[04:50] <wgrant> That's precisely the opposite of what you want.
[04:50] <StevenK> Which is utterly wrong, since I've just managed to swap in how to actually use it. :-)
[04:50] <wgrant> structured()'s first operand is markup.
[04:51] <StevenK> notification = "\n".join(messages)
[04:51] <StevenK>     TypeError: sequence item 1: expected string, structured found
[04:51] <StevenK> Oh, BAH
[04:52] <StevenK> This is utterly pointlessness to do it with an array. May as well build a string
[04:55] <wgrant> You know what would be good here? :)
[04:55] <wgrant> A... TEMPLATE! [jarring chord]
[04:55] <StevenK> Haha
[04:56] <StevenK> Oh, damn it, can't use += for strings and structured
[04:56] <wgrant> No, you'd have to use .escapedtext, which would be nice to avoid.
[04:57] <StevenK> Hopefully += works if everything is structured
[04:58] <StevenK> ... which it does not.
[04:58] <wgrant> No.
[04:58] <wgrant> This is where MarkupSafe is nice.
[04:58] <wgrant> But IE.
[04:58] <wgrant> IE destroys everything :)
[05:00] <StevenK> Sigh, this would be easy if it wasn't for the loop of sources in the middle.
[05:00] <wgrant> Sure. This is the sort of thing templates were invented for.
[05:02] <StevenK> Grrr
[05:03] <StevenK> I can't see a nice way to do this. I wonder how to pull in pystache
[05:04] <wgrant> Use escapedtext
[05:05] <wgrant> Or I guess you could use pystache, but eeeeh.
[05:05] <wgrant> mustache is slow and awful.
[05:08] <StevenK> Oh, bah, structured is replacing the < and > too
[05:10] <wgrant> Hmmm?
[05:10] <wgrant> That's the point of it.
[05:10] <StevenK> But I'm building HTML :-(
[05:11] <wgrant> How are you trying to use structured()? Because it's wrong :)
[05:11] <StevenK> wgrant: http://pastebin.ubuntu.com/822199/
[05:12] <wgrant> StevenK: So, you need to wrap the final thing in structured(), or addNotification will escape it.
[05:14] <StevenK> wgrant: That works. Other than that, I guess I'm using structed() correctly? :-)
[05:14] <StevenK> Sigh, structured()
[05:20] <wgrant> StevenK: Not correctly, but not wrongly.
[05:20] <wgrant> There's no correct way here.
[05:20] <StevenK> I think I can cope with "It's not perfect, but much better than what was there."
[05:21] <StevenK> wgrant: Diff updated.
[05:24] <wgrant> StevenK: Approved, with one change.
[05:26] <StevenK> wgrant: Like http://pastebin.ubuntu.com/822212/ ?
[05:28] <wgrant> StevenK: Right.
[05:29] <wgrant> Possibly with a comment "If you change the next statement, wgrant will send rabid dogs after you."
[05:32] <StevenK> Haha
[05:49] <StevenK> Hm, have we been wallyworld-less today?
[05:49] <wallyworld> no?
[05:49] <StevenK> You've just said nothing all day
[05:49] <wallyworld> been busy
[05:50]  * StevenK is getting quite tempted to upgrade the ec2 image
[05:50] <wallyworld> do, you know you want to
[05:54] <StevenK> jtv: You can delete your ec2 ami-2b5e9e42
[06:59] <StevenK> bac: You can delete your ec2 ami-9165a5f8 of id 521.
[06:59] <wgrant> lifeless: Do you know if anybody in maintenance is sorting out the remaining longpoll issue, or should I JFDI given that Red is no longer with us?
[07:01]  * StevenK purges Java off his system now that he doesn't need ec2-api-tools
[07:05] <wallyworld> poor Java :-(
[07:37]  * stub adds Zookeeper to -dependencies for a laugh
[07:39] <wgrant> I hope we'll need it eventually :)
[08:00] <stub> Ooh... counter troll.
[08:03]  * StevenK stabs Thunderbird, pulls the knife out, and stabs it again, twisting the knife.
[08:04] <StevenK> Why does every single mail client have to completly suck?
[08:05] <StevenK> Perhaps it's mandated in RFC 3501.
[08:20] <wgrant> StevenK: A combination of 3501 and 5322, yes.
[08:50] <adeuring> good mornig
[09:01] <lifeless> wgrant: they are not
[09:02] <lifeless> wgrant: if you want to DI, that would rock
[09:03] <wgrant> lifeless: Will need some CORS stuff in Apache, I suspect, but will look at some point.
[09:15] <danhg> Morning everyone
[09:16] <nigelb> Morning danhg, mrevell
[09:17] <nigelb> bigjools: Watched the cricket? I heard England had fun :D
[09:27] <stub> StevenK: Are we going to conflict with ec2 images or are you finished now? I'm just about to attempt to build a PG 9.1 image.
[09:27] <stub> (but that won't be public until testing is done, couple of days)
[09:28] <lifeless> stub: hey
[09:28] <wgrant> stub: That sounds dangerous, given that 9.1 on prod is probably some time away...
[09:28] <stub> lifeless: yo
[09:28] <lifeless> stub: so, I missed our catchup last week
[09:28] <stub> wgrant: Says who?
[09:28] <stub> lifeless: That is fine. I wasn't there either :)
[09:28] <lifeless> stub: I'd like to catch up tomorrow; reckon you could be around a bit earlier?
[09:30] <stub> lifeless: sure
[09:30] <wgrant> stub: Says me not trusting pg_upgrade, and an insufficient CPU count to do it any other way :)
[09:30] <wgrant> But if pg_upgrade works now, that's great.
[09:30] <lifeless> stub: also, there are about 4 bugs that all boil down to 'make a new user', wondering if you want to knock them over sometime soonish; seems like one straightforward patch should do it
[09:30] <lifeless> stub: I've tagged them 'dbuser'
[09:30] <stub> wgrant: I need to push it forward or it will never happen. There are problems, and we will go ahead when I have solutions :)
[09:30] <lifeless> stub: (tomorrow - thanks)
[09:30] <lifeless> and now, for me, gnight
[09:30] <stub> lifeless: k
[10:09] <StevenK> stub: I'm done, 524 was just an update since I got sick of waiting for ec2 to upgrade 80MiB worth of packages.
[14:04] <deryck> Morning, all.
[15:32] <sinzui> jcsackett, do you have time to mumble?
[15:52] <nigelb> Interesting quit message there :)
[15:53] <jcsackett> sinzui: i can mumble now, sorry i missed your ping.
[15:53]  * sinzui starts mumble
[15:53]  * jcsackett does too
[19:28] <lifeless> mornink
[19:28] <lifeless> deryck: hey
[19:56] <deryck> lifeless, hey man.  been meaning to reply to you all day.  sorry
[19:56] <deryck> lifeless, how about sometime after the TL call this week?
[19:57] <lifeless> mm, pretty sure that that morning is wall to wall calls
[19:57]  * lifeless consults calendar
[19:57] <lifeless> I think statik cancelled, so I could do tlstart + 2h as the start time
[19:58] <deryck> lifeless, 2100 UTC?
[20:02] <lifeless> I think so
[20:03] <flacoste> lifeless: hang out time?
[20:04] <lifeless> flacoste: sure, can you send a regular invite? that one is on the wrong machine :P
[20:05] <flacoste> lifeless: i did
[20:06] <lifeless> oh, google notifications fail
[20:06] <lifeless> 'this service is unavailable please try again later'
[20:06] <flacoste> i resent the invite
[20:08] <deryck> lifeless, I'll calendar you and move it if it's wrong.
[20:34] <lifeless> deryck: thanks, looks fine to me
[20:34] <deryck> lifeless, awesome
[20:56] <lifeless> danhg: hiya
[20:56] <lifeless> danhg: thanks!
[21:15] <wallyworld> deryck: hi, wanna have a quick chat?
[21:18] <wallyworld> deryck: sorry, network dropped out, not sure if you replied
[21:18] <deryck> wallyworld, hey.  sure.  I'm near EOD, and I'm nearly spent.  But I'll take a shot at it.  mumble or hangout?
[21:19] <wallyworld> deryck: mumble, just a quick one
[21:20] <deryck> ok
[22:42] <reed> hi folks
[22:43] <reed> is there a way for a manager to extract the list of email address of people in a LP team?
[22:43] <reed> need to run the openstack elections based on the members of openstack, I'd like to see if I can save some energy
[22:52] <sinzui> StevenK, This is a few days before NG agreed to hire me and 6 months are we took all the data out of illustra (proto-postgresql) and ran on python 1.2 http://web.archive.org/web/19961111220245/http://www.nationalgeographic.com/main.html
[22:52] <sinzui> it's so tiny
[22:59] <StevenK> wallyworld: https://code.launchpad.net/~stevenk/launchpad/combo-url/+merge/90093
[23:07] <sinzui> Ian. After the underpants protest, they stopped tampering with the pictures: http://web.archive.org/web/19961221170010/http://www.nationalgeographic.com/modules/contact2/dispatch/Nicolas/clickup/rd50up.html
[23:08] <wallyworld> sinzui: lol :-)
[23:08] <sinzui> Though think this through...if they have never been in contact with modern civ...why are they posing.
[23:08] <StevenK> Haha
[23:10] <wallyworld> you raise an excellent point, hmmm
[23:13] <wallyworld> wgrant: StevenK: yay, my 128GB SSD just arrived. now to clone my current hdd so i can run without my disk thrashing so much
[23:49] <StevenK> wallyworld: My desktop doesn't thrash at all, and my laptop has an SSD already. So I'm not sure why your laptop is so terrible
[23:49] <StevenK> Hah
[23:50] <StevenK> I see that lifeless' ISP is running in 'operational excellence' too
[23:59] <lifeless> yeah
[23:59] <lifeless> (not really)