[14:55] <sasa84> hello
[14:56] <sasa84> does anyone else have a problem with one string in transmission? http://screencloud.net/v/4huQ
[15:04] <dobey> error seems pretty direct to me
[15:05] <ricotz> hi, ppa-builder https://launchpad.net/builders/chindi02 might be broken
[15:05] <cjwatson> looking
[15:05] <dobey> s/might be/is/
[15:05] <dobey> and it seems to be broken a lot and often :(
[15:06] <cjwatson> Ah, yes, Xen
[15:06] <cjwatson> I've disabled it and I'll ask for it to be rebuilt
[15:06] <ricotz> cjwatson, thx
[15:07] <cjwatson> I'll work on giving back the failures too
[15:09] <cjwatson> Sigh, been broken for a while, too
[15:10] <ricotz> none of my builds hit it until just now ;)
[15:33] <czajkowski> jamespage: ping
[15:33] <jamespage> czajkowski, hey
[15:33] <czajkowski> ello :)
[15:33] <czajkowski> free for a quick pm ?
[15:36] <czajkowski> jamespage: ^
[15:36] <jamespage> czajkowski, sure
[15:57] <cjwatson> dobey: regarding sasa84's question, the problem would appear to be that the msgstr is of basically the same form as the msgid, and yet the error says that the msgstr doesn't look like a format string unlike the msgid
[15:58] <cjwatson> I don't know a whole lot about LP Translations but it does look like a pretty weird message
[15:59] <dobey> cjwatson: well, i'm guessing LP probably doesn't validate the incoming pot file from the upstream untranslated string for msgids, but does validate when you try to submit a msgstr
[15:59] <cjwatson> Perhaps, I don't know
[15:59] <dobey> so yes, it's a problem with the upstream string.
[15:59] <cjwatson> LP also shouldn't be saying things that aren't true
[16:00] <dobey> it's not
[16:00] <dobey> the error message given is true
[16:00] <cjwatson> "'msgstr' is not a valid C format string, unlike 'msgid'"
[16:00] <cjwatson> if the part before the comma is true, then the part after the comma is untrue
[16:01] <dobey> oh, right.
[16:02] <sasa84> hi cjwatson
[16:02] <dobey> it's probably assuming that because it didn't fail to import, that it's valid. or the error is coming straight from a gettext tool
[16:04] <cjwatson> Mm, you may well be right that it's the latter; I don't see that string in the LP codebase
[16:04] <cjwatson> Somebody who actually knows about LP Translations might know more
[16:06] <dobey> regardless of any issue in lp or gettext, the upstream string is clearly broken and needs to be fixed
[16:06] <dobey> %'d is not any more valid than %&#x27d
[16:07] <cjwatson> Er, is too
[16:07] <cjwatson> "'      For decimal conversion (i, d, u, f, F, g, G) the output is to be grouped with thousands' grouping characters if the locale information indicates any."
[16:07] <cjwatson> printf(3)
[16:12] <dobey> oh. hrmm, that string is obsolete anyway
[16:12] <dobey> it doesn't seem to exist in https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/transmission/saucy/view/head:/gtk/filter.c
[16:12] <dobey> particularly not on line 898 as mentioned
[16:15] <cjwatson> dobey: You can't rely on that, since the import failed: http://package-import.ubuntu.com/status/transmission.html
[16:15] <cjwatson> Would require checking the actual source package
[16:15] <cjwatson> (And that's been failing for over a year)
[16:17] <dobey> oh
[16:18] <dobey> i wish *that* would get fixed so that the branches are always up to doate :(
[20:03] <mfisch> is there a way to export/make a patch a set of changes from one branch into another non-related branch? This includes binary files, which is the issue.
[20:03] <mfisch> I tried bzr export -r-2..-1 .. and the diff obviously doesn't include binaries
[20:13] <dobey> i don't think so, no. not easily anyway
[20:20] <dobey> you could use xdelta to build a diff instead, that must be applied with xdelta
[20:25] <mfisch> dobey: thanks, I did a patch + cp -a for the binaries
[20:26] <dobey> mfisch: are you trying to patch them into a .deb or something?
[20:27] <mfisch> dobey: we have some customizations for ubuntu-touch, the branches diverged a long time ago, but we added a new feature today that can be shared
[20:30] <bkerensa> Can someone confirm how frequently LP does translation jobs?
[20:30] <bkerensa> is it nightly or every two days?
[23:23] <wgrant> bkerensa: What kind of translation jobs? There are numerous.
[23:23] <bkerensa> wgrant: generation of templates
[23:24] <bkerensa> wgrant: right now launchpad is showing ubuntu-docs/saucy as 80% translated
[23:24] <bkerensa> but thats not accurate
[23:24] <bkerensa> since no translation work has been done on the saucy ubuntu-docs branch yet
[23:24] <wgrant> That sounds like statistics updates.
[23:24] <bkerensa> wgrant: and that takes how long?
[23:24] <wgrant> bkerensa: Translations are shared between series.
[23:24] <bkerensa> yes
[23:24] <bkerensa> so
[23:24] <bkerensa> if raring had some strings alread translated then it would show that percentage in saucy?
[23:25] <bkerensa> if minimal changes were made?
[23:25] <wgrant> If 80% of the ubuntu-docs/saucy strings are the same as ubuntu-docs/raring, saucy is 80% translated.
[23:25] <bkerensa> k
[23:25] <bkerensa> thanks for clarification on that
[23:25] <bkerensa> I will let translations team know
[23:34] <Akiva-Server> sorry for a newb question, but I had been using bazaar explorer for awhile, and the process of throwing my latest code up on launchpad was, a) Commit, then b) push. Now that I changed computers, and set up bazaar again, my push option is gone, and committing alone makes my code appear on launchpad... Did I fundamentally misunderstand something here?
[23:35] <Akiva-Server> I was under the impression that committing is like putting on the wrapping paper, and pushing was about mailing it to launchpad.
[23:39] <Akiva-Server> When I pushed, was I needlessly overwriting my old project or something?
[23:39] <wgrant> Akiva-Server: Bazaar also has the concept of checkouts (aka. "bound branches") that automatically push and pull from the remote server when you commit and update.
[23:39] <wgrant> It sounds like you've got a checkout now.
[23:40] <wgrant> They operate pretty much identically to normal branches, except that the push/pull steps are implicit.
[23:40] <Akiva-Server> Okay, so is it more like realtime code editing?
[23:41] <Akiva-Server> wgrant: And thanks for explaining that to me
[23:41] <wgrant> Akiva-Server: You still have to commit
[23:41] <wgrant> It just looks a bit more like a centralised VCS, like Subversion.
[23:41] <wgrant> Because commits always immediately go to the server.
[23:42] <Akiva-Server> wgrant: Ah. I must of pushed checkout not realizing what it did, and thus it set this all up for me?
[23:43] <wgrant> Akiva-Server: Right. You can easily convert between a checkout and a branch using 'bzr bind' and 'bzr unbind', but I'm not sure if Bazaar Explorer has a button for that.
[23:43] <Akiva-Server> wgrant: Great thanks.
[23:44] <Akiva-Server> +1
[23:44] <Akiva-Server> !cookie wgrant
[23:44] <Akiva-Server> lol, there is actually a bot here :P
[23:47] <bkerensa> wgrant: is there anyway to track changes made to a project? Like see who has changed settings?