[01:41] cjohnston: no calendar program on your mobile is going to make the value if X-Blueprint readily accessible [01:42] daker_: not at a quick glance, no [01:42] the decorator unfortunately muddles the traceback [03:15] mhall119: since guidebook doesnt use json [03:18] guidebook won't use X-Blueprint either will it? [03:23] I think it could be made to? [03:32] maybe, would blueprints be useful on a phone though? [03:34] dunno [03:34] make a hold tag and hold it? [03:35] off to bed [03:35] g'nite === daker_ is now known as daker [13:27] cjohnston, mhall119: Welcome to our latest summit contributor \m/ https://code.launchpad.net/~pendulum/summit/665589-launchpad-request-retries [13:27] yay! [13:27] Pendulum++ [13:29] we'll see how y'all feel about it in a month when I still don't know what I'm doing :P [13:30] Pendulum: we've all been there :-) [13:31] mhall119: I'm voting that we get joey to organize a summit hackathon and get james_w and salgado to review all the summit merges :P [13:36] I'm pretty sure nigelb is still winging it [13:37] mhall119: winging? [13:37] improv [13:37] playing by ear [13:37] making it up as you go [13:37] mucking around in production just to see what breaks [13:37] oh, haha :p [13:37] No, I have my own set up which plays with my own launchpad. [13:37] So its awesome ;) [13:38] nice [13:38] I can do anything on the sprint and get feedback immediately [13:38] nigelb: do you think the linaro guys are familiar enough with the summit codebase to be doing code reviews? [13:39] mhall119: I think james_w is. But if you insist, you can do them all yourself. [13:39] mhall119: did you tell him about what you found last night? [13:39] mhall119: Right now, the merges are getting stale. [13:39] cjohnston: what? [13:39] then dont make code that makes code change [13:39] nigelb: oh, there are *still* changes in production [13:39] mhall119: wtf. [13:40] Daviey: PING. [13:40] Daviey: ^^ [13:40] Daviey: You said there aren't any more changes in production :/ [13:40] bzr st shows something was changed [13:40] mhall119: lots of changes? [13:41] maybe it'http://paste.ubuntu.com/621728/ [13:41] nigelb: o/ [13:42] Daviey: :( More changes in production, that's not checked in :( [13:42] nigelb: that change was not there when i told you it was clean. [13:43] When i said, there is no diff in production, that was valid for that time - not forever in the future. [13:43] Daviey: oh, wait. That change is now committed. I believe we can ignore. [13:43] mhall119: ^^ [13:43] :( [13:43] who commited that change nigelb ? [13:43] I see a similar but not exact change in the bzr history [13:43] Would like to get an idea of who edited it. [13:43] Daviey: I did. The edit was done by you on my suggestion. I remember sitting the back of the ballroom and doing that ;) [13:44] * nigelb takes blame for this diff. [13:44] nigelb: check rev 111 of the summit trunk, that looks the closest, but it's not the same [13:44] mhall119: Remember you rejected one of my MPs? [13:45] mhall119: the last time you did code reviews, this was the change. [13:45] oh, so the code I rejected is already in production? [13:45] :(++ [13:45] mhall119: no, I accidentally had that code in a unclean branch which you committed before reviewing that. [13:46] basically, its all goo [13:46] basically, its all good [13:46] The code is all committed now. [13:46] nigelb: I'm still not seeing that exact change in the bzr tree... [13:46] so which is correct? [13:46] yes [13:46] I believe, yes [13:47] :o [13:47] that wasn't a yes or no question [13:47] oh right. [13:47] I believe the code committed is correct. [13:47] * mhall119 needs more coffee for this [13:48] I can't get to my summit install to test and give you updated results. [13:48] * nigelb is still at work. [13:48] okay, let me know for sure later, as we'll have to revert what's in production before we deploy in order to avoid a conflict [13:49] mhall119: okay, sure. [13:49] mhall119: are we doing something this weekend for summit? [13:50] drinking, it seems [13:50] btw, http://paste.ubuntu.com/621734/ is going up somewhere [13:51] mhall119: I read that line without the "so" ;) [13:51] it read like a rhetoric question [13:51] oh, I see now [13:51] I no longer think you're totally insane then [13:52] I'm not sure I like the "totally" there ;) [13:52] well, you are still working on summit code, that can't be normal [13:52] heh [14:26] the invisible window sucks >:( [14:28] +1 mhall119 [14:29] He's just working excuses to get out of it.. kinda like comitting to production [14:31] I told him the other day that the only way to get away from the curse of summit development was to trick somebody else into taking over, and he's already got Pendulum submitting patches [14:39] does anyone know where I can download the theme for planet.ubuntu ? I can find the config file in LP, but not the templates. [14:40] I don't think they are public [14:40] I could be wrong tho [14:40] Would there be a reason for not publishing them? [14:41] they are public [14:41] sbc, https://code.launchpad.net/~rhlee/ubuntu-website/light-planet-theme2 [14:41] o [14:41] cool [14:41] sbc: what are you wanting to do with it? [14:41] cjohnston: update the theme we use for the Danish planet. [14:41] daker: Thanks! [14:43] yw === daker is now known as daker_ [22:08] mhall119: is the only reason that we havent asked for a Django and South update on cranberry because we had wanted to throw in the django-openid-auth at the same time? [22:25] daker: bug 794756 please when you get a moment [22:25] Launchpad bug 794756 in ubuntu-cloud-portal "Link in footer to report a bug (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/794756 [22:25] sure [22:25] ty [22:30] cjohnston: no, it's because it would affect all sites on cranberry, so we'll need to make sure they're all compatible, or use some method of isolating them [22:30] gotcha [22:31] has anyone began checking into this that you are aware of? [22:31] either that or they'd have to setup a new server and move those sites over that are ready [22:31] not that I'm aware of, no [22:34] what versions are we wanting to go to? [22:35] it looks like natty is running 1.2.5-ubuntu1 [22:35] and 0.7-1 [22:41] I guess we can go to 1.2.5 [22:41] though we have packages for 1.3 [22:41] so, what would be the rational for using 1.2.5? [22:45] I'm +1 for going 1.3.. I was just thinking 1.2.5 already has packages.. but if 1.3 does, then I'm all for it [22:45] it has packages in a PPA [22:45] and I can setup LTP to use virtualenv for local development [22:49] mhall119: http://pad.ubuntu.com/daY3vyyn3C [22:53] cjohnston: might be worth it to just ask the sysadmins first if it would be easier to get a new server for those sites we're upgrading