[00:54] <wgrant> Nice easy one: https://code.launchpad.net/~wgrant/launchpad/html5-charset/+merge/100541
[00:55] <StevenK> wgrant: Meh, self-review :-P
[00:57] <StevenK> wgrant: r=me
[00:58] <wgrant> Thanks
[02:54] <StevenK> No Production OOPSes? Oh dear.
[02:54] <lifeless> carob may have been rebooted
[02:55] <StevenK> It has not.
[02:55] <StevenK> But we have Soyuz, qas and staging mails, just no prod.
[02:59] <lifeless> oh
[02:59] <lifeless> it will be chewing on fdt probably then
[02:59] <StevenK> For an hour?
[03:01] <lifeless> has on extreme cases in the past
[03:21] <wgrant> StevenK: It's contending with prune.
[03:21] <wgrant> postgres is not very happy.
[03:21] <wgrant> It's later than normal today, but still going.
[03:21] <wgrant> (you'll see it's been like an hour late for a few days)
[03:24] <wgrant> It's also eating a lot of RAM, oddly.
[04:19] <wgrant> lifeless: 12MB OOPSes make bson sad.
[05:12] <wgrant> Ah
[05:12] <wgrant> So that's why the report was so slow.
[05:12] <wgrant> Something is terribly broken.
[05:13] <wgrant> Although given the UA it might just be someone trying to exploit us.
[05:13] <wgrant> Who knows.
[05:13] <wgrant> It looks almost like someone assumed that every quoted string on the page was a URL
[05:14] <StevenK> ... Odd.
[05:14] <wgrant> Yeah
[05:14] <wgrant> It's an archival crawler.
[05:14] <wgrant> Which seems to be misbehaving.
[05:15] <wgrant> Yay
[05:15] <wgrant> No new bug write timeouts.
[05:15] <wgrant> I am safe.
[05:15] <StevenK> wgrant: Still can't figure out what to do in terms of Bug:+secrecy and multi-pillar bugs.
[05:15] <wgrant> StevenK: Oh?
[05:16] <wgrant> StevenK: I hadn't heard about this.
[05:16] <StevenK> wgrant: Currently, the UI omits private if it's a multi-pillar bug.
[05:16] <stub> Heh. Write robust code and forget WTF it does.
[05:16] <wgrant> StevenK: Ah
[05:17] <StevenK> wgrant: But that won't help given IBug.transistionToInformationType() will toss an exception no matter what you choose if the bug is multi-pillar.
[05:17] <wgrant> StevenK: That needs to stop.
[05:18] <StevenK> wgrant: And we do what instead?
[05:18] <lifeless> only proprietary ones cannot be multi-pillar
[05:18] <wgrant> StevenK: In the end only PROPRIETARY is forbidden to have multi-pillar
[05:18] <wgrant> What he said.
[05:19] <StevenK> Should I change that now, then?
[05:20] <wgrant> Probably. You can remove the FF at the same time.
[05:20] <StevenK> Right.
[06:24] <StevenK> wgrant: https://code.launchpad.net/~stevenk/launchpad/forbid-proprietary-multi-pillar/+merge/100557
[06:31] <wgrant> StevenK: What's with line 33?
[06:31] <wgrant> The new cancel_url.
[06:33] <StevenK> wgrant: Bug:+secrecy doesn't have a cancel link, it has annoyed me while I was working on the UI and it's one line.
[06:33] <wgrant> Heh
[06:33] <wgrant> k
[06:33] <wgrant> + def test_hide_private_option_for_multipillar_proprietary_bugs(self):
[06:33] <wgrant> StevenK: Oxymoron
[06:35] <StevenK> Right, but it will change when the UI does to show information_type.
[06:36] <wgrant> StevenK: The idea is that you can't make a multipillar bug proprietary.
[06:36] <wgrant> StevenK: The starting condition for that test is that there is a proprietary multipillar bug.
[06:36] <wgrant> That's invalid state.
[06:37] <StevenK> Hmmm.
[06:39] <danhg> Morning
[06:40] <StevenK> wgrant: Sadly, we can't test that with the UI having not switched.
[06:45] <wgrant> StevenK: Indeed.
[06:49] <wgrant> StevenK: Anyway, that test is invalid. Fix it if you can, otherwise delete it.
[07:42] <adeuring> good morning
[08:04] <StevenK> wgrant: But no approval? :-(
[09:24] <gmb> Well, today's going to be a fun one if I've got only a partially-working desktop.
[09:24] <gmb> Sigh
[09:25] <gmb> (Also, what's the word for that feeling you get when you encounter a bit of Launchpad that you're largely responsible for and wish fervently that you'd had the time to make it less clunky?)
[09:26] <lifeless> gmb: guilt
[09:27] <gmb> lifeless: Yeah. At least it's fleeting, because I have no actual soul.
[09:27] <czajkowski> gmb: see this is why I wanted people to reply to my thread on low bugs so I could get people to help
[09:27] <czajkowski> bu nobody replied :(
[09:27] <lifeless> czajkowski: well, I thought about replying
[09:27] <czajkowski> but you saw to many low bugs :)
[09:27] <lifeless> czajkowski: see, do you mean low as in 'unimportant' or low as in 'easy' / 'approachable' ?
[09:28] <gmb> czajkowski: Scheisse. I actually meant to, and then got sidetracked. But my question was the same as lifeless's.
[09:28] <lifeless> czajkowski: if you mean 'unimportant', well, it seems odd to motivate people to work on unimportant bugs.
[09:28] <czajkowski> lifeless: the latter
[09:28] <lifeless> czajkowski: look for bugs tagged trivial or easy.
[09:28] <czajkowski> ideally what I want to do is well get 5 bugs that people would love to see done in LP, but dont ahve the time and I could try and get people more involved and woarkign on patches
[09:28] <lifeless> czajkowski: there are many - hundreds - of those that are also 'high' importance.
[09:28] <czajkowski> nods
[09:29] <czajkowski> but thought i'd start with low first adn see if some of the smaller tweaks could get people involved and interested
[09:29] <czajkowski> and a place to start
[09:29] <lifeless> czajkowski: 'low' importance does not mean small.
[09:29] <lifeless> it means less important. :)
[09:31] <lifeless> czajkowski: but perhaps we're talking at cross purposes. Let me ask instead, why are you talking about 'low' bugs: what is attractive about them, and do you mean the same thing as I do when I say 'low' ?
[09:32] <czajkowski> hmm
[09:32] <czajkowski> so imo low was small tweaks to lp that people would like to see like the example I gave about cc'ing someone when you send a contact this person mail
[09:32] <czajkowski> lifeless: I was also just looking to get people talking and for people t suggest bugs
[09:33] <czajkowski> but that didn't happen :/
[09:33] <lifeless> assertion: there are small tweaks that are important, and small tweaks that are less important. What association do you see between 'low' importance and 'small tweak' ?
[09:34] <czajkowski> lifeless: I just started with low as a starting point, if you found me bugs that were high I'd also promote them :)
[09:35] <lifeless> czajkowski: so, I'm a bit like a terrier here :)
[09:35] <lifeless> why did you start with low; do you perhaps assume that low importance has some correlation with size of effort to fix the bug ?
[09:35] <czajkowski> lifeless:  nope no correlation
[09:35] <czajkowski> I start with low as a place to start
[09:36] <lifeless> I find that fascinating
[09:36] <lifeless> anyhow, the place I suggest you start is the tag 'trivial'
[09:37] <czajkowski> lifeless: care to suggest a bug then :)
[09:37] <czajkowski> at least you;ve entered into discussion
[09:37] <czajkowski> which is fascinating :)
[09:37] <lifeless> https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=trivial
[09:38] <lifeless> bug 869309
[09:38] <_mup_> Bug #869309: If folders in repository have unicode names, sometimes I get KeyError <navigation> <oops> <trivial> <unicode> <loggerhead:Triaged> < https://launchpad.net/bugs/869309 >
[09:38] <czajkowski> lifeless: thank you
[09:40] <gmb> czajkowski: I would suggest bug 353097 and bug 249471 as good ones to tackle. The second might be slightly more complex, IDK.
[09:40] <_mup_> Bug #353097: Marking a Bug as "Requiring Forwarding" text is missleading... <better-forwarding> <confusing-ui> <docs> <lp-bugs> <trivial> <Launchpad itself:Triaged> < https://launchpad.net/bugs/353097 >
[09:40] <_mup_> Bug #249471: Reporting a bug with an attachment produces two info alerts <lp-bugs> <trivial> <Launchpad itself:Triaged> < https://launchpad.net/bugs/249471 >
[09:40] <lifeless> nn all
[09:40] <czajkowski> lifeless: nn
[10:21] <cjwatson> lifeless: IME Launchpad's low importance doesn't always imply that the bug is of low importance to the user or group who reported it (and rightly so; Launchpad has to prioritise)
[10:24] <cjwatson> lifeless: for instance, bug 930217 is likely to be of considerable use to Ubuntu, but it was triaged as Low, and I think that was reasonable for LP to do (we could have used up some stakeholder credit to escalate it to Critical, but I think it's better to use such credit for things we can't fix ourselves)
[10:24] <_mup_> Bug #930217: Make proposed pocket useful for staging uploads <qa-ok> <Launchpad itself:Fix Released by cjwatson> < https://launchpad.net/bugs/930217 >
[10:28] <wgrant> cjwatson: Don't get lifeless started on multitenancy :)
[10:28] <StevenK> Haha
[10:29] <cjwatson> Heh, well, my other argument would be that if you want to get more people involved then the message of "these are things we aren't currently planning to fix at all, but you can" is stronger than "these are things we're planning to fix eventually, but you can make it happen sooner"
[10:38] <jml> cjwatson: perhaps we just need to spread the message that "not Critical" means "not planning on fixing at all"
[10:39] <wgrant> And "Critical" means "planning on fixing eventually but it'll never actually happen" :)
[10:40] <jml> "'The matter is under consideration' means we have lost the file. 'The matter is under active consideration' means we are trying to find the file."
[10:47] <cjwatson> Yes Minister++
[10:47] <cjwatson> or was that Yes Prime Ministere?
[10:47] <cjwatson> -e
[10:47] <jpds> Both.
[11:12] <jml> cjwatson: I think it was Yes Minister.
[11:53] <mabac> salgado, lost you
[11:54] <salgado> yep, trying to reconnect
[12:09] <benji> let me check my notes
[12:09] <benji> ...for which channel I want to be in
[12:56] <deryck> Morning, everyone.
[12:56] <czajkowski> deryck: ello
[12:59] <StevenK> benji!!
[13:00] <benji> StevenK!!
[13:00]  * benji hears string music well up in the background.
[13:00] <rick_h> StevenK: you still around? I wanted to chat with you. I broke the convoy build setup you had by adding a makefile :/
[13:00] <StevenK> benji: Oh, just that you fixed the unclean reactor terribleness with a branch of awesome
[13:01] <benji> I hope I got it all.  I'm not very... twisty
[13:01] <StevenK> rick_h: Ish. Chatting with friends and trying to avoid work.
[13:02] <rick_h> StevenK: ah, gotcha. Nvm then. I'll send an official email and all that
[13:02] <rick_h> go get more wine!
[13:04] <StevenK> rick_h: Chatting with friends on *IRC*
[13:04] <StevenK> rick_h: So I'm here at the computer, so you can ask if you wish.
[13:04] <rick_h> StevenK: just wanted to have the conversation on updating hte packaging and see what needs to be done. I figure I need to update the Makefile I added to not bork whatever needs to go on
[13:05] <rick_h> we've filed an RT to get it on production so figured I should unbreak things before that happens, but not sure what you had in mind when you mentioned 'unsucking' the packaging
[13:06] <StevenK> rick_h: We should fix the packaging before we go forward to production.
[13:06] <rick_h> StevenK: rgr, so I wanted to ping and get a list of what we need to do so that we can get it done.
[13:07] <StevenK> rick_h: So I think you should organise a call/hangout with you, me, the Landscape guy that admits to knowing what convoy is, and the same for U1.
[13:08] <rick_h> ok, I'll put together an email. I know sidnei is brazil-ish, not sure on the landscape guy. Will try to find some common time ground.
[13:08] <jml> do any of you have any tricks for pairing on LP hacking?
[13:08] <StevenK> rick_h: It's a one time call, so I'm happy to take a hit if I need to -- like 10pm or so.
[13:09] <rick_h> StevenK: rgr, thanks. Don't think it'll be necessary, but will see
[13:09] <rick_h> jml: I thought some people did some shared desktop stuff in hangouts recently that worked ok, but not really
[13:11] <jml> rick_h: ta
[13:11] <jml> How do I run ec2 from lp-dev-utils?
[13:12] <rick_h> jml: you have to add it to your path. I symlinked the stuff into my ~/bin dir
[13:12] <rick_h> had the same question myself heh
[13:13] <jml> rick_h: thanks.
[13:18] <StevenK> I symlinked into ~/bin, it was easier
[13:24] <jml> please remind me what set_schema in zcml means
[13:24] <StevenK> That you have permission to set the attributes exported by that class
[13:26] <wgrant> interface
[13:27] <jml> ah ok.
[13:27] <jml> so, IIUC, you only need view permissions on IPerson to call createPPA?
[13:28] <wgrant> That seems to be correct.
[13:29] <jml> wgrant: where's the logic that prevents me from creating a PPA in ~wgrant?
[13:30] <wgrant> jml: There probably isn't any.
[13:32] <wgrant> Aha
[13:32] <wgrant> It's not my fault after all
[13:33] <wgrant> I apparently reviewed the commit that exports the method (despite it being before I started), but it was not added to ViewRestricted
[13:33] <wgrant> When did that change...
[13:36] <jml> wgrant: but ViewRestricted means "you need launchpad.View", right? surely createPPA should require launchpad.Edit?
[13:36] <wgrant> jml: One would certainly think so.
[13:36] <wgrant> I'm saying that your analysis is correct.
[13:36] <wgrant> Not that the current state of things is in any way justifiable.
[13:36] <jml> wgrant: oh ok.
[13:37] <jml> wgrant: as some context, james_w and I are exploring the LP code base, hoping to make whatever changes we need so a bot can create private, commercial PPAs.
[13:38] <wgrant> jml: Didn't you land a change recently to permit creating private ones?
[13:38] <jml> wgrant: maybe. I tend to forget things like that.
[13:38] <StevenK> Or Cody did.
[13:38] <wgrant> [r=julian-edwards][bug=814567] Add an API to create private PPAs,
[13:38] <wgrant> rather than changing privacy status post creation.
[13:39] <wgrant> 'twas jml
[13:39] <jml> yeah, found the branch.
[13:39] <jml> right. that was clever of me.
[13:40] <jml> I guess it's the 'commercial' bit that we need now.
[13:42] <jml> You know, as an interview question, SteveA asked me how I would build a permission system. I wish I had had a really good answer.
[13:42] <wgrant> ZTK's is terrible.
[13:42] <wgrant> But it's one of the better ones I've seen.
[13:42] <StevenK> Oh, it doesn't serve as a warning?
[13:44] <StevenK> jml: One of my interview questions with mdz was him asking me which VCSes I had experience with, and I commented that I had a few personal projects in tla, which prompted him to say "You've done ... *real* work ... with tla?"
[13:49] <james_w> james-w is not allowed to make private PPAs
[13:49] <jml> it's hard to judge ZTK's permission system based on LP
[13:50] <james_w> which is <person on which the PPA is being created> is not allowed to make private PPAs
[13:50] <jml> except that you learn that it's not easy for developers to use
[13:50] <jml> james_w: yeah, that's from Archive.validatePPA
[13:50] <jml> james_w: which does a *manual* check for celebrity membership
[13:50] <jml> james_w: rather than asked if person has launchpad.Commercial on something
[13:53] <nigelb> StevenK: haha, that's a great question :P
[14:06] <jml> basically, LP doesn't really have an internal language for "this user is allowed to make private stuff"
[14:11] <jml> maybe it should have something like launchpad.AppendRestricted
[14:18] <jml> how do I shell into the ec2 machine that the ec2 script creates?
[14:18] <jml> as in, what key do I use?
[14:21] <rick_h> jml: I think it creates the key and in the log it mentions the name? not 100% sure thogh
[14:28] <jml> rick_h: there's a *lot* of log
[14:28] <rick_h> jml: yea, but when you run it dumps out to terminal the startup bits as it builds up for the ec2 instance
[14:29] <rick_h> it's in there before the instance fires up I believe
[14:29] <rick_h> jml: if you look at the instance in the ec2 web tools I htink it lists what the key is that it's using? bah, I got this to work once, but not needed to do it again
[14:30] <jml> hmm. nope.
[14:31] <jml> I mean, there's a key there, but I can't get at it.
[14:31] <rick_h> right, but does it give a hint for the filename to look for locally?
[14:31]  * rick_h goes to peek at the aws console
[14:33] <jml> rick_h: no, it doesn't.
[14:34] <rick_h> jml: so when I click on my running instace in the ec2 web console it says the key pair name on the left?
[14:35] <jml> rick_h: yes. where am I expected to find that on my laptop?
[14:35] <rick_h> I don't recall, but if you updatedb/locate does it come up?
[14:36] <jml> rick_h: no, it doesn't.
[14:36] <rick_h> bah sorry, don't recall then. Maybe someone else knows.
[14:37] <jml> rick_h: well, thank for trying.
[14:44] <jml> rick_h: the trick is to ssh in as the 'ec2test' user
[14:45] <rick_h> jml: doh, thanks
[14:46] <jcsackett> we need an ec2 ssh command.
[14:46] <jcsackett> well, maybe not need.
[14:47] <jml> james_w:   ssh -A ec2test@ec2-184-73-132-244.compute-1.amazonaws.com
[14:47] <jml> jcsackett: it'd be pretty easy to do.
[14:48] <jml> jcsackett: I remember asking myself "why didn't I do that when I first thought of it?" when I added ec'2 list'
[14:48] <jcsackett> ec2 list, btw, is a fantastic command. :-P
[14:48]  * rick_h goes to look up ec2 list
[14:48] <jcsackett> jml: yeah, it doesn't strike me as that difficult. might look at it when i next have slack time.
[14:48] <jcsackett> rick_h: it lists all your running instances. handy way to make sure you don't leave something running.
[14:49] <rick_h> ah, very cool then. I tend to hit the webui which can be a pita
[14:50] <jcsackett> rick_h: yeah. and the verbose options tell you which branches are running with what instance ids. which is handy when you then want to `ec2 kill` something.
[14:50] <rick_h> ooh, json decode backtrace :/
[14:50] <jcsackett> basically, the less i have to jump to the webui, the happier i am.
[14:50] <rick_h> yea, definitely
[14:52] <james_w> jml, http://www.debian-administration.org/article/Using_GNU_screen%27s_multiuser_feature_for_remote_support
[15:02] <rick_h> gmb: a bit of reading if you get some time please? https://code.launchpad.net/~rharding/launchpad/email_notice_959482/+merge/99995
[15:02] <gmb> rick_h: Sure thing.
[15:02] <rick_h> gmb: first real change in this area, so feel free to be a bit brutal to show me the ropes and beat proper things into my head.
[15:02] <gmb> Okidoke.
[15:02]  * gmb cracks knuckles
[15:02]  * rick_h runs and hides
[15:41] <jml> :(
[15:56] <jml> https://code.launchpad.net/~jml/launchpad/create-commercial-ppa/+merge/100635 up for review
[15:57] <rick_h> danhg: ping, my MP with the email and updated wording is here https://code.launchpad.net/~rharding/launchpad/email_notice_959482/+merge/99995
[15:57] <rick_h> danhg: the reasoning/etc are tied into the bug and MP description, I think that'll answer most of your questions you had via email
[16:17] <gmb> rick_h: Approved with comments (all about tests and documentation).
[16:21] <rick_h> gmb: ty much will peek at the damage
[16:22] <gmb> rick_h: The code looks fine; good work!
[16:22] <rick_h> gmb: thanks, I might understand how this stuff works yet! :)
[16:22] <gmb> :)
[16:23] <benji> gmb: if you have a minute, I have a small branch for review: https://code.launchpad.net/~benji/launchpad/bug-972456/+merge/100645
[16:23] <gmb> benji: Sure
[16:24] <abentley> abel: could you please review https://code.launchpad.net/~abentley/launchpad/celery-job-feature-flag/+merge/100647 ?
[16:25] <gmb> benji: Approved.
[16:27] <benji> gmb: thanks
[16:37] <abentley> gmb: Could you please review https://code.launchpad.net/~abentley/launchpad/celery-job-feature-flag/+merge/100647 ?
[16:37] <gmb> abentley: Sure
[16:37] <gmb> Merge proposals are like buses...
[16:37] <gmb> Anyway.
[16:50] <gmb> abentley: Approved; nice work.
[16:50] <abentley> gmb: Thanks.
[17:52] <stokachu> hi, using python-launchpadlib to retrieve messages the date_created field are unicode strings instead of datetime objects, is this expected?
[17:53] <stokachu> the parent bug will return a datetime object so i was curious
[17:55] <rick_h> stokachu: update your version of waddlib, that was fixed a week or two ago I think
[17:56] <stokachu> rick_h: ok ill do that, i saw the bug where the date_created field in a bug was fixed not sure if it extended to messages
[17:56] <rick_h> I think it was fairly general
[17:56] <stokachu> ok
[17:58] <stokachu> did the fix make it into pypi?
[17:58] <rick_h> believe so
[17:59] <rick_h> yea, 1.3.1 mentions the datetime bug
[17:59] <stokachu> i have waddlib 1.3.1 installed
[17:59] <rick_h> ok, then you might submit a new bug on it with the steps to reproduce please (or a patch :) )
[18:00] <stokachu> ok sounds good, just making sure it was an oversight
[18:02] <stokachu> rick_h: im going to file a bug and hopefully get a patch but just for my sake could you look at this snip: http://pastebin.ubuntu.com/913394/
[18:03] <rick_h> hmm, you're not accessing it via the object interface so not sure you'll get anything but that string
[18:03] <rick_h> I think what the wadllib and such do is convert that dict access to message.date_created or something
[18:03] <rick_h> based on the object definition from the wadl file
[18:04] <rick_h> at least that's my understanding
[18:04] <stokachu> ah makes sense, so im probably just calling it incorrectly
[18:07] <rick_h> all the tests are doing things like xx.get_parameter('a_date').get_value()
[18:07] <rick_h> which return a datetime object
[18:08] <stokachu> hmmm ok ive been looking through the collections doc but im sure im doing something wrong
[18:08] <rick_h> yea, well you're at the lplib layer which uses wadllib underneath so not sure how it exposes it
[18:15] <stokachu> yea im not totally sure either, every way i slice it comes back as dict
[18:16] <stokachu> bug.message is a collection object
[18:18] <stokachu> when doing a bug.messages.resource_type_link
[18:18] <stokachu> u'https://api.launchpad.net/1.0/#message-page-resource'
[18:18] <stokachu> that doesn't exist in the api
[18:20] <rick_h> sec, trying something out
[18:21] <stokachu> cool no worries
[18:21] <rick_h> sorry, not quite an api pro heh
[18:21] <stokachu> me either, took me a week to understand that person and team were the same thing :X
[18:29] <stokachu> andd my internet craps out
[18:31] <salgado> is there a way to do sequence unpacking in TAL?  I thought there was but can't seem to find out how
[18:32] <rick_h> stokachu: hmm, so what comes back to you is really just a dict plain and simple. It seems like there shuold be a way to get a real object out of there but don't see it with casual print dir()'ing
[18:33] <stokachu> rick_h: ok, yea im getting that same impression
[18:35] <jcsackett> given a set of bug ids, is there a set based way to feed them to bug search? i see bugparams can take a bug param, but that looks like a single thing, not a set thing. i'd rather not iterate over the whole set.
[18:38] <rick_h> stokachu: http://pastebin.ubuntu.com/913443/
[18:38] <rick_h> ok, so that's some playing, it doesn't support negative indices
[18:38] <rick_h> and that comes out as a datetime object
[18:38] <rick_h> not a string
[18:38] <stokachu> ah
[18:38] <rick_h> http://pastebin.ubuntu.com/913444/
[18:38] <rick_h> is a bit better with the output
[18:39] <stokachu> ok cool, thanks! :)
[18:39] <rick_h> so hopefully that helps a little bit, sorry
[18:44] <stokachu> rick_h: thats perfect
[18:44] <stokachu> rick_h: wish it allowed negative indices
[18:46] <stokachu> guess i could do message = bugs.messages[len(bugs.messages.entries)]
[18:46] <rick_h> stokachu: yea, not sure if there's a way to get the length and guess the right index off of it
[18:47] <rick_h> there's a property for count or size I saw while dumping out dir() of things
[18:47] <rick_h> try dir(bug.messages)
[18:47] <stokachu> ah lemme look into that
[18:50] <salgado> rick_h, do you know if there's a way to do sequence unpacking in TAL?
[18:54] <rick_h> salgado: sorry, I know next to nothing of tal
[18:54] <salgado> rick_h, heh, ok.  no worries
[19:12] <lifeless> cjwatson: so, I agree; you'll note I didn't end up recommending 'start with trivial+high', just 'trivial', once I felt I understood czajkowski's desire a bit better
[19:12] <lifeless> cjwatson: and yeah, we have actually speculated about a very einsteinian model for importance and sorting :)
[19:16] <cjwatson> right, more important to be fixable easily than to be important, in this case
[19:17] <cjwatson> of course there's also the importance/urgency inequality
[19:17] <lifeless> fortunately we don't have urgency, it doesn't exist :P
[19:18] <cjwatson> it gives you a simpler and probably more usable model, certainly; still leaves you mapping two not-quite-parallel dimensions onto one :)
[19:19] <cjwatson> I agree that that trade-off was worthwhile, but it's something contributors will likely be thinking about
[21:59] <jono> hey folks
[22:23] <lifeless> hi
[22:24] <salgado> StevenK, hey there.  it'd be great if you could review https://code.launchpad.net/~linaro-infrastructure/launchpad/team-engineering-view-ui/+merge/100707 for us (it seems like you're the on call reviewer today?)
[22:25] <StevenK> salgado: On the phone, I'll look afterwards.
[22:26] <salgado> StevenK, thanks a lot!
[22:27] <cjwatson> Are there any examples in LP of something whose DB/Python representation is multiple levels, but which we collapse down to one level for exposure in the web service API?  Say the Python representation is Foo.Bar.attribute, but I'd like to have the API be more like foo.attribute.
[22:27] <cjwatson> I'm not quite familiar enough with the patterns and so it's hard to grep for.
[22:28] <StevenK> cjwatson: SPPH does that when it exports things from SPR.
[22:28] <cjwatson> Ah, of course.  Thanks.
[22:28] <StevenK> return self.sourcepackagerelease.<>
[22:29] <cjwatson> So just exported() in the interface and a @property in the model.  Great.
[22:29] <StevenK> With a test, that should be great.
[22:29] <cjwatson> I'm trying to do something similar in PackageUploadSource.
[22:32] <jono> has anyone here got any experience with intltool-update? I am trying to generate a .POT file for a .desktop like file I can import into Launchpad
[22:33] <cjwatson> Only in conjunction with autoconf/automake, where you do @INTLTOOL_DESKTOP_RULE@ in Makefile.am and declare the files in desktop* targets and it takes care of the rest.
[22:33] <cjwatson> That's a fair bit to pull in if you aren't already using automake, though.
[22:34] <jono> cjwatson, from what I understand i I have POTFILE.in in my po/ dir and just run intltool-update --pot --gettext-package=foobar it should process my file and generate a .POT file
[22:34] <cjwatson>   INTLTOOL_DESKTOP_RULE='%.desktop:   %.desktop.in   $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< [$]@'
[22:34] <jono> the problem is that it is not generating the file
[22:34] <cjwatson> possibly helpful if you want to unpick all those expansions
[22:35] <jono> I have no idea what that is :-)
[22:35] <cjwatson> Ah, that's the other end, that merges the translations into an output .desktop file
[22:36] <jono> gotcha
[22:36] <jono> so I have the following in foo.desktop:
[22:36] <jono> [Desktop Entry]
[22:36] <jono> Encoding=UTF-8
[22:36] <jono> _Name=MyApplication
[22:36] <jono> _Comment=A useful application that does useful things
[22:37] <cjwatson> something like what you said sounds right, though it needs to be POTFILES.in, not POTFILE.in
[22:37] <jono> and then in a po/ dir I have POTFILES.in with foo.desktop in it
[22:37] <jono> and I run: intltool-update --pot --gettext-package=foobar
[22:37] <jono> but then there is no output
[22:37] <cjwatson> it has a --verbose
[22:38] <jono> ahhh
[22:38] <jono> it says: None of the files in POTFILES.in contain strings marked for translation.
[22:38] <jono>  -- which is odd as I have underscore before the keys in the .desktop file
[22:39] <lifeless> jono: -> #launchpad, I suspect you'll get more help there
[22:39] <jono> lifeless, it was pretty quiet earlier when I asked, but will try again
[22:39] <jono> thanks cjwatson