[08:01] <mrevell> Hello!
[08:03] <oier_> hi, I am not sure if I am on the correct channel. I have a question regarding translators credit.
[08:04] <oier_> If I set a translatable string in my app (in the about diago) as"translators-credit", does Launchpad automatically translate that string with the translators? or does each translator have to append its name there?
[09:04] <poolie> sladen, hi
[09:05] <sladen> poolie: hello
[09:05] <sladen> poolie: wgrant appears to have tracked it down to twisted-web
[09:05] <poolie> wgrant and robert worked out the underlying cause of broken mime types, and it's clearly not the proxy
[09:06] <poolie> wondered why you marked the twisted thing incomplete
[09:07] <sladen> poolie: because I don't know the exact line-number ... if other people have more information, I'm sure it's not quite so incomplete
[09:41] <poolie> sladen, the exact line number?
[09:42] <sladen> poolie: if the problem is completely identified, I'm happy to change it to Triaged :-)  At the time of adding it, I wasn't in a position to know /if/ it had been suitably identified
[09:42] <poolie> to me 'incomplete' means "this bug can't progress unless it gets more information"
[09:44] <sladen> poolie: same here.
[09:45] <sladen> poolie: I don't think there's /quite/ enough information on the bug report for a random developer to pick it up and understand the problem completely w.r.t specifically to twisted-web
[09:46] <poolie> there is
[09:46] <poolie> i'll file an upstream report
[09:47] <sladen> poolie: I don't think one could provide any more information to the LP team, but it's possible that the LP team may need to provide more information to enable tackling the twisted element
[09:47] <sladen> poolie: yup
[10:18] <esteve> hi all, I'm seeing errors like this when submitting comments to merge proposals:
[10:18] <esteve> "Server error, please contact an administrator. OOPS ID:OOPS-2019J48"
[10:19] <esteve> thought the feedback may be useful to you
[10:19] <poolie> hi esteve
[10:21] <poolie> oops
[10:22] <poolie> esteve, we're working on it
[10:22] <esteve> I'm also getting logged out randomly
[10:22] <esteve> for example, just claimed a merge review and got this:
[10:22] <esteve> "Application error.  Unauthenticated user POSTing to page that requires authentication."
[10:25] <poolie> yep
[10:31] <poolie> esteve, if you log in again it should be ok
[10:32] <esteve> poolie: I tried and got an "Already logged in" message
[10:32] <esteve> poolie: will logout and log in
[10:33] <wgrant> esteve: 5 minutes ago it would have done that. Now you should really be logged out.
[10:33] <wgrant> And can log in again.
[10:33] <esteve> wgrant: ok, thanks!
[10:34] <poolie> wgrant the actual oops he got is a bit interesting
[10:34] <poolie> https://lp-oops.canonical.com/oops.py/?oopsid=2019J48
[10:34] <poolie> not totally obvious to me that that is the same cause
[10:35] <wgrant> poolie: Oh, has it synced?
[10:35] <wgrant> I synced it to my ~ manually.
[10:35] <wgrant> You'll see the request is anonymous.
[10:35] <wgrant> So it used the slave store.
[10:35] <wgrant> Where the comment didn't exist yet.
[10:35] <poolie> of course
[10:36] <wgrant> Now, normally I'd expect an SQLObjectNotFoundError to cause it to retry with the master, but apparently not this time..
[10:36] <wgrant> Maybe it doesn't do that on the webservice.
[11:06] <aboudreault> why my ticket disappear
[11:08] <aboudreault> ha ok.. my session was expired. and the bug is a security one.
[11:11] <commandoline> Hello, does anyone know what a normal time is for translation imports from branches to stay on 'Needs Review'? (It's the first import since a new directory structure.)
[11:13] <maxb> Somewhat variable, I think
[11:13] <maxb> I don't really know much about the translations side of LP, though
[11:13] <maxb> danilos: ?
[11:20] <danilos> commandoline, they usually do that for only a few hours (tops, sometimes mere minutes), but if there's an issue, they stay like that forever until someone reviews them manually (which we do once a day for .pots, never unless asked for for translations themselves)
[11:22] <commandoline> ok, I'll just wait some more time then first.
[11:22] <commandoline> thanks danilos and maxb
[11:47] <mwhudson> <insert whine about ppa queue>
[11:48] <bigjools> it's a bit like people who, sat in traffic, moan about it.
[11:49] <smspillaz> when you could just as quickly cycle :)
[11:51] <wgrant> mwhudson: Some builders have just returned.
[11:51] <wgrant> With luck the rest will come back soon.
[11:51] <mwhudson> wgrant: oh cool
[11:52] <maxb> At least it's only a queue of hours :-)
[11:52] <wgrant> Oh, 10 more have come back in the last 5 minutes.
[11:53] <mwhudson> it's just amazing how you come to depend on/expect packages building in a few minutes
[11:53] <wgrant> Yes :(
[11:54] <bigjools> the build farm is quite popular
[12:35] <aquarius> in the code browser, the "download file" link for a particular file looks like this: http://bazaar.launchpad.net/~sil/+junk/save-into-ubuntu-one/download/head:/saveintoubuntuone-20110712102419-zvja3yvh0fi0zmj3-3/Save%20into%20Ubuntu%20One
[12:36] <aquarius> if I push a new version of the branch that that file's in (with a new version of that file), will that download link still fetch the old version?
[12:36] <aquarius> and if so, is it possible to get a "download file" link which always gets the most recent version of that file?
[12:36] <aquarius> I note that the URL has "head:" in it, but it's also got a date...
[12:47] <james_w> aquarius, that url will download the latest version of that file
[12:47] <james_w> it will likely break if the file is renamed though
[12:47] <aquarius> james_w, always? even if I push newer versions? Nice
[12:47] <james_w> (though it may work, I don't know if the last segment is ignored)
[12:48] <aquarius> yeah, I'm not worried about it breaking on renames :)
[12:48] <james_w> yeah, you need to replace head: if you want a specific revision
[12:48] <aquarius> what's the 20110712102419-zvja3yvh0fi0zmj3-3 bit for then?
[12:48] <aquarius> I mean, I believe you, I'm just curious :)
[12:49] <james_w> it's part of the file id
[12:49] <james_w> so it's associated with the file rather than the revision
[12:50] <aquarius> ah! cool :)
[12:50] <james_w> it's an arbitrary random-ish string generated when bzr starts tracking the file
[12:50] <james_w> it survives renames, but given that the URL has the filename at the end I don't know if it will work
[14:30] <sinzui> jcsackett, do you have time to mumble?
[14:31] <jcsackett> sinzui: yes, though we may have some fun getting that work. my computer is haunted today.
[16:11] <CasW> I came to use (Python) launchpadlib, but I can't seem to find documentation except for that getting started-guide
[17:05] <cgregan> Hello Launchpad Team...my a LP team of mine seems to have vanished.....anything known to be going on with LP today?
[17:06] <cgregan> wow awesome english to boot on this one........."A LP team of mine................
[18:58] <Darxus> I just got some "failed to upload" and ".changes rejected" emails for daily builds that I haven't touched in a while and which built and uploaded successfully 11 hours ago.  I can safely ignore those, right?
[19:09] <maxb> Darxus: Most likely means that they got triggered by a change to a component branch which wasn't included in the version expression in the recipe, so the new builds clashed with the existing version string
[19:10] <Darxus> Weird.
[19:12] <Darxus> It was from https://code.launchpad.net/~spamassassin/+recipe/spamassassin-daily
[19:13] <Darxus> The last two automated attempts to sync lp:spamassassin, which is basically all that it builds, crashed.
[19:13] <Darxus> sqlite3.OperationalError: database is locked
[19:48] <maxb> Darxus: You would get a "failed to upload" if you updated lp:~spamassassin/+junk/spamassassin-pkgrules, and lp:spamassassin had not also been updated meanwhile
[19:49] <maxb> the database is locked thing is unfortunately a bug whenever two imports from the same svn repository happen on the same importd machine simultaneously
[19:58] <Darxus> I suspected something like that (known bug).  Do you know if there's actually a bug open for it?
[19:59] <Darxus> (I didn't update lp:~spamassassin/+junk/spamassassin-pkgrules.)
[19:59] <maxb> Not sure how the new builds got triggered, then
[20:00] <Darxus> Yeah, it's weird.
[20:01] <Darxus> I wish there was a way to get it to only trigger a build if something, say, not in the rules or rulesrc directories of that svn repo got modified.  Because they aren't included in the package.
[20:01] <Darxus> And they're most of the changes.
[20:02] <maxb> That's a bit advanced
[20:02] <maxb> Though, nothing stops you setting it to manual build only, and triggering the build as required - possibly via an external cronjob
[20:05] <Darxus> Not worth the complexity of an external cron job.
[20:05] <Darxus> It works just fine the way it is.  It just builds more often than it needs to, and my server nags me to upgrade it unnecessarily often (every day) :)
[21:03] <CasW> I want to register a bug using (python-)launchpadlib, but I can't seem to find out how
[21:04] <CasW> Anyone here with tips?
[21:05] <ivoks> any known issues with launchpad.net? when i login, i get different username, and it asks me to pick a password
[21:19] <lifeless> ivoks: hi, we reset the session database overnight
[21:19] <ivoks> i think my got screwed
[21:19] <lifeless> ivoks: make sure you're logged into login.launchpad.net with your normal account
[21:20] <ivoks> well, i am
[21:20] <ivoks> as in correct email and correct name
[21:20] <lifeless> I'll see if I can grab someone that can poke at the relevant bits
[21:20] <ivoks> ok, thanks
[21:22] <CasW> Is there a way to register bugs with launchpadlib?
[21:22] <CasW> (Or does anyone here know a room where I can find the devs?)
[21:22] <mbarnett> ivoks: lifeless: forgive my distraction for the next couple minutes.  Just finishing up a call.
[21:23] <lifeless> CasW: have you seen the api doc? https://launchpad.net/+apidoc/1.0.html
[21:23] <CasW> Yeah, I have, but I couldn't find it there
[21:23] <lifeless> https://launchpad.net/+apidoc/1.0.html#bugs
[21:24] <CasW> Hmm :P
[21:24] <CasW> Thanks
[22:32] <poolie> is lp repeatedly logging me out?
[22:32] <poolie> s//why is
[22:34] <lifeless> it shouldn't be
[22:35] <lifeless> the reset was a one off
[22:35] <poolie> that's 3 times this morning
[22:35] <lifeless> new tabs?
[22:38] <poolie> maybe that was it, but i thought i logged in in the first window
[22:38] <poolie> nm for now
[23:55] <Noldorin> does LP automatically mark a LP bug as fixed when you do bzr commit --fixes lp:x ?
[23:55] <TheEvilPhoenix> Noldorin:  you could test :p
[23:55] <TheEvilPhoenix> but i'll defer to the experts for thhe answeer
[23:55] <TheEvilPhoenix> bah keyboard lag, sorry
[23:56] <Noldorin> TheEvilPhoenix, it seems like the answer is no, but perhaps it's just the LP server taking its time :-P
[23:56] <TheEvilPhoenix> :P
[23:56] <Noldorin> TheEvilPhoenix, an official answer would be nice...thanks anyway :-)