=== Keybuk [n=scott@syndicate.netsplit.com] has joined #launchpad === xenru [n=Miranda@85.192.12.132] has joined #launchpad === jordi [n=jordi@115.Red-213-96-69.staticIP.rima-tde.net] has joined #launchpad === Fujitsu [n=Fujitsu@ubuntu/member/fujitsu] has joined #launchpad [01:31] Goooooooooooooooood morning Launchpadders! [01:32] Good morning, mpt! === AlinuxOS [n=alinux@d83-176-107-91.cust.tele2.it] has joined #launchpad === j-a-meinel [n=j-a-mein@adsl-67-37-234-251.dsl.chcgil.ameritech.net] has joined #launchpad [02:41] lifeless: https://devpad.canonical.com/~jamesh/productrelease-sourcepackagerelease.txt <- results of matching product release files with source package release files on demo.launchpad.net [02:42] had to run librarian-gc before getting those results [02:42] cool. let me finish this release and I'll peek === panickedtest [n=travis@cdm-75-109-115-91.asbnva.dhcp.suddenlink.net] has joined #launchpad === panickedtest is now known as panickedthumb === Seveaz [n=seveas@ubuntu/member/seveas] has joined #launchpad === JanC [n=janc@lugwv/member/JanC] has joined #launchpad [04:30] mpt: ping? [04:35] jamesh, pong [04:36] mpt: I was working on a fix for bug 55649: adding a "Product..development_focus" field pointing at a product series, and Bjorn noted that the way I displayed it on the product page was a bit confusing [04:36] Malone bug 55649 in launchpad "Product does not record an explicit main series" [Untriaged,In progress] http://launchpad.net/bugs/55649 [04:37] mpt: at the moment I just have the text "This series is the current development focus" below the nominated series in the main content area [04:37] I was wondering if you have any better ideas [04:41] jamesh, perhaps use a pastel background to highlight the series in the list, keeping "Current focus of development" at the bottom of that highlighted section [04:42] interesting. Any particular colour or CSS class we use for this sort of thing elsewhere? [04:44] There's class="highlighted" [04:45] thanks. === stub [n=stub@ppp-58.8.9.33.revip2.asianet.co.th] has joined #launchpad [06:05] mpt: what do you think of removing the class="discreet" bit for the series listing? [06:23] jamesh, good idea === BjornT [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad [07:43] lifeless: I posted the results of the product release/source package release matching to the list. It shows up at least one bad release file pattern in our current data [07:43] thank you for examining this closley [07:44] I think we might want to adopt a slightly more complex pattern matching syntax [07:44] one that can also be used to extract version numbers from the file name like the uscan one can [07:48] yeah [07:48] I would like to just invoke uscan TBH [08:00] stub: would you be able to review the DB patch in "jamesh/launchpad/bug-55649"? === marcus_notebook [n=mholthau@johnny33.dersbach.ch] has joined #launchpad === BjornT- [n=bjorn@213.226.190.253] has joined #launchpad === BjornT- is now known as BjornT [08:39] morning [08:43] jamesh: so is it worth my reading the report yet ? [08:43] jamesh: or do you think its too broken to go forward with until a better pattern matcher is in place ? [08:43] hi SteveA [08:45] lifeless: I think the matching report gave pretty good results -- the matches we got were correct in as far as the data created by product-release-finder was correct [08:47] lifeless: the only issues were (1) the pattern for redland was too loose, so picked up tarballs for another release, and (2) the version number inferred from some tarball names was incorrect [08:48] interesting [08:48] not all that many hits [08:48] thats on demo ? [08:48] yeah [08:49] not automake matches ? [08:49] 'no' [08:49] the automake tarballs might be repacked to remove GFDL docs ... [08:49] yeah [08:49] (for the Ubuntu packages, that is) [08:49] I'm trying to get a handle on how big the damage is [08:50] there are some source packages where the debian/ dir has been merged into the .orig.tar.gz too, iirc [08:51] eww [08:51] (I think the libtool package was like that last time I looked) [08:51] mm [08:51] ok [08:52] I think we should be good to go [08:52] but we still need to fix this form : [08:52] https://demo.launchpad.net/products/bzr/bzr.dev/+source [08:52] yeah [08:52] try filling out the release details [08:52] theres a bug open on this [08:52] I think we should remove everything from that form except upstream VCS details [08:52] and have a "no VCS details registered" radio button [08:53] that works for me, as long as theres a 'edit series FTP/HTTP file location' button somewhere visible === mholthaus_ [n=mholthau@35-6.0-85.cust.bluewin.ch] has joined #launchpad [08:53] can you do a report that shows: [08:54] tarball, series name (i.e. trunk) and version (0.10) only - no cross reference to the distro side ? [08:54] I'd like to review that [08:55] didn't I include one like that earlier? [08:55] I don tthink so [08:56] maybe I missed it if it wasn't cced to me === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad [08:56] the one you put https://devpad.canonical.com/~jamesh/productrelease-sourcepackagerelease.txt has the spr - which is distro side [08:56] the mail titled "product-release-finder test results", which was CC'd to you [08:56] oops, blush [08:56] from 4 days ago [08:56] ah, middle of the pre-freeze sprint [08:59] should we special case the .orig issue ? [09:00] I'm not entirely sure whyh l-k-h is a product at all, but ... [09:00] probably should. (in hct's splitversion method, probably) [09:00] ok [09:01] publib too is affected [09:01] yep. Those were the two I identified in the email :) === carlos [n=carlos@138.Red-81-39-35.dynamicIP.rima-tde.net] has joined #launchpad [09:01] morning === BjornT_ [n=bjorn@213.226.190.253] has joined #launchpad [09:04] jamesh: emailed === BjornT-__ [n=bjorn@213.226.190.253] has joined #launchpad === BjornT__ [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad === malcc [n=malcolm@host86-138-251-144.range86-138.btcentralplus.com] has joined #launchpad === seb128 [n=seb128@ubuntu/member/seb128] has joined #launchpad === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #launchpad === Fujitsu [n=Fujitsu@ubuntu/member/fujitsu] has joined #launchpad === Spads [n=spacehob@82.211.81.249] has joined #launchpad === matthewrevell [i=synchron@outbound.silenceisdefeat.org] has joined #launchpad [10:27] jamesh: Please add a comment to comments.sql for the development_focus column, and maybe update the existing table comment on product series to say there should always be at least one per product. [10:27] jamesh: Otherwise, r=stub. patch-67-20-0.sql === danilos [n=danilo@cable-89-216-150-53.dynamic.sbb.co.yu] has joined #launchpad [10:29] stub: thanks [10:30] New bug: #61024 in malone "+packagebugs with a large number of packages approaches uselessness" [Untriaged,Unconfirmed] http://launchpad.net/bugs/61024 [10:32] carlos, danilos: so I spent most of my time last week bringing the queue up to date. [10:32] jordi: yeah, I saw it. Good work!! [10:33] Most if not all of what's in there now is dubious or waiting for some action from requesters [10:33] thx! === Ag4Ms [i=AbrAKada@202.150.115.105] has joined #launchpad [10:33] if only wordpress would get their stuff sorted out [10:34] jordi: did you talked with mvo about the 'broken' locales he's uploading ? [10:34] jordi: hi! cool, only ~120 unreviewed templates left! [10:34] jordi: ah, so they are reviewed as well, great job :) [10:34] I was tempted to approve the wordpress stuff, given they *know* about and document rosetta in their webpage [10:34] danilos: I'm talking about products :) [10:34] carlos: nope, I didn't catch him on irc during the WE [10:35] I'll do now [10:35] jordi: ok, thanks [10:35] danilos: I did the distro work ;-) [10:35] jordi: ok :) [10:35] carlos: ok :) [10:35] danilos: ok :) [10:35] so, so [10:35] jordi: what's exactly the problem with duplicate messages? [10:35] if jordi did products, and carlos did distro, WHAT DID DANILO DO [10:35] jordi: Firefox! [10:35] :-D [10:35] jordi: I slept longer, thanks to you guys :) [10:35] heh [10:36] duplicate messages? [10:36] jordi: I read something about that as the problem to import wordpress [10:36] hm, no mvo [10:36] oh [10:36] they document rosetta in their webpage as one of the ways of translating wordpress [10:36] but they also have other ways of doing translations [10:36] = mess [10:36] Hi Room..! [10:37] jordi: ok, forget what I told you.... [10:37] I see, I misunderstood that [10:38] carlos: jordi needs not forgetting, he didn't hear you the first time, he never listens :) [10:38] :-P [10:39] jordi: well, in that case, if they still want the import... we should do it, the mess is their fault... [10:39] I mean, we cannot force them to use a concrete way to handle their translations... [10:39] http://codex.wordpress.org/Translating_WordPress [10:40] yeah [10:40] That was my new POV during the weekend [10:40] want mess? all yours :) [10:40] " Note: many translators have found Rosetta to be a good starting point, but once it comes time to proofread the entire list of translations, many have opted to switch hand-editing the PO file or using a program like poEdit or KBabel, since the Rosetta UI lacks a search feature and other things that become essential when proofreading and editing. " [10:40] hrm [10:41] ok [10:41] decided, I'm accepting these [10:46] just note to them, that they could use Rosetta as the place to get back those .po files [10:47] is not a matter if they use Kbabel or poEdit, just upload them into rosetta so they don't get conflicts to solve on their side [10:51] yeah [10:51] I'll try [10:51] Ryan is not exactly responsive [10:53] accepted [10:53] to bad we've been rejecting many WP files for months. [10:54] well, we still need the .pot file and I think we got them before we got the request to import the .pot file... [10:57] we had a pot file and two translations [10:57] I renamed the template to "wordpress", too [10:57] carlos: btw, you should get rid of the "reuse" me templates soon [10:58] or you'll run out :) [10:58] only 10 left :) [10:58] jordi: ;-) [10:58] less work for us :-P [11:01] carlos: is it possible to get rid of "projects"? [11:02] wordpress the project, and wordpress, wordpress2 the products [11:02] this is a mess [11:02] and how do I change the "recommended" template? [11:02] can't remember tghis [11:03] ugh [11:03] so there's a wordpress-2 product which is deactivated but still shows up in navigation [11:03] jordi: talk with kiko and/or stub about it [11:04] k [11:04] about the navigation, I guess [11:04] jordi: kiko deactivated a lot of products recently so I guess he should know exactly what's going on there [11:04] what about the recommended template? [11:04] kiko: wake up man [11:04] jordi: URL? [11:06] jordi: mpt changed the templates to show the recomended ones... I don't know what rule he used to decide which one is the recommended one for products [11:06] http://launchpad.net/products/wordpress [11:06] mpt: ? [11:06] mpt: ping [11:06] SteveA: hey dude [11:06] In fact [11:06] jordi: https://launchpad.net/products/wordpress/+translations [11:06] that page is broken [11:07] you don't see all available templates [11:07] yeah [11:07] jordi: also, could you change the flag for wordpress to say 'It uses Rosetta' [11:07] well, I can't [11:07] I can't edit it [11:07] carlos: on a product page, product, Ubuntu package, other package [11:08] mpt: talking about products, no distro packages [11:08] I didn't change the selection, just the order [11:08] hi SteveA [11:08] mpt: I see [11:08] mpt: what happens if there are two templates for different productseries? === quail [n=quail@unaffiliated/quaillinux/x-000001] has joined #launchpad [11:09] jordi: how's that? you are a 'registry' expert/admin, aren't you? [11:09] carlos, I don't know, I didn't change anything about that [11:10] ok [11:10] I didn't change the selection, just the order. [11:11] jordi: seems like support for multiple templates in products is broken right now [11:11] so that product templates were prioritized first instead of last. [11:11] jordi: we should add a translation_focus field to Product to use the same procedure we use with distributions [11:11] jordi: to decide the productseries that should have the translation focus [11:12] jordi: anyway... are there any other release for 1.x branch? [11:12] jordi: shouldn't they use 'trunk'? [11:14] I don't know [11:14] we really should find a way to make 2.0 show up there tho :) [11:15] jordi: I guess just the first one appears.... [11:15] let me try something... === jinty [n=jinty@195.Red-83-58-178.dynamicIP.rima-tde.net] has joined #launchpad [11:15] jordi: but I still think they should use the 'trunk' standard way... [11:17] jordi: it requires code changes [11:17] (to show 2.x over 1.x) [11:23] nod [11:23] everyone loves the 2h slots :) === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #launchpad === jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad === iwj [n=ian@xenophobe.extern.relativity.greenend.org.uk] has left #launchpad [] [11:43] carlos: down to 9 files [11:43] some of them are cruft for sure :) === R3Ndy [i=AbrAKada@202.150.112.156] has joined #launchpad === doko_ [n=doko@dslb-088-073-094-184.pools.arcor-ip.net] has joined #launchpad [11:46] jordi: ;-) [11:48] You know it's going to be a bad day when: [11:48] you forget to put milk in your scrambled eggs [11:49] your coffee pot makes strange fizzling noises [11:49] there goes milk into scrambled eggs? [11:50] Yup, otherwise it's just a weird omelette. [11:50] One coffee spoon of milk per egg === mpt shudders [11:51] Though, caffeinated eggs could be interesting [11:51] uh?!? === sabdfl [n=sabdfl@ubuntu/member/pdpc.silver.sabdfl] has joined #launchpad [11:52] ddaa: a coffee spoon isn't a standard measure in most english speaking countries [11:52] jamesh: mh... in my understanding, a teaspoon is a bit smaller [11:53] ddaa: maybe you mean a table spoon? [11:53] no, that's much large [11:53] * larger [11:53] teaspoon < coffee spoon < table spoon [11:53] but maybe it's just me [11:53] dessert spoon? [11:54] nah, coffee spoon < dessert spoon < table spoon [11:54] bah, I'll call that a teaspoon [11:54] I guess it just depends whether tea or coffee was the more traditional drink in any given country, when the spoons were named === Ag4Ms [i=AbrAKada@202.150.110.64] has joined #launchpad === Keybuk [n=scott@quest.netsplit.com] has joined #launchpad [12:06] jordi, danilos: dudes... what are Evince people thinking on? [12:07] jordi, danilos: latest release uses 'Evince' instead of 'evince' as the translation domain.... === mpt [n=mpt@203-167-187-52.dsl.clear.net.nz] has joined #launchpad [12:16] sigh [12:16] carlos: "yay" for them [12:17] what should we do to reflect that fact? [12:17] because our system doesn't allow us to do it... [12:17] without changing Dapper and Breezy's translation domains too... [12:17] unless we give it a 'evince-edgy' name [12:17] hum, I have no idea; ask for a patched ubuntu package? :) === stub [n=stub@ppp-58.8.9.33.revip2.asianet.co.th] has joined #launchpad [12:18] ooh fuck, Serbian translation in Rosetta should be banned... some of these guys are not only using Latin script, but Latin script without *any* diacritics (which are separate letters in Serbian like ) [12:18] carlos: how did they change it? the .mo are named "evince.mo" [12:20] New bug: #60614 in rosetta "Wrong string in gtk20 po file" [High,In progress] http://launchpad.net/bugs/60614 [12:20] carlos: the configure has "GETTEXT_PACKAGE=evince" [12:24] danilos, send jordi in there to sort them out :-) [12:24] mpt: The Jordi of Fury, I will :) [12:25] I should probably report a bug and assign it to jordi ;) [12:25] or send them The Fury of Jordi, whatever works better :) === jordi warms his Fury Engine. [12:26] but, what seb says. [12:27] jordi: this is about Serbian "translation" in Rosetta, I'll let you handle that :P [12:27] the Fury Engine, like the Emotion Engine but cooler [12:28] oh, serbian [12:28] we should merge with croatian translations [12:30] jordi: yeah, that would work too :) [12:30] jordi: don't forget the bosnian, though ;) [12:35] carlos: ping [12:36] seb128: the .pot file is Evince.pot [12:36] seb128: if the official .mo files is evince.mo then, it's all right [12:36] carlos: [12:36] $ ls evince-0.6.0/po/*.pot [12:36] evince-0.6.0/po/evince.pot [12:36] seb128: hmmm, latest .pot file for evince that we got in Rosetta has 'po/Evince.pot' [12:37] carlos: that's a local build of the edgy package [12:37] maybe somebody did upload that template? [12:37] seb128: hmmm, sorry, it's not latest, it's from last month... [12:37] perhaps it was a bug that they already fixed.... [12:37] seb128: it came from the automatic import queue [12:38] seb128: atm only Rosetta admins are allowed to use the upload form for Ubuntu [12:38] $ find . -name "*.pot" [12:38] ./evince-0.5.5/po/Evince.pot [12:38] ./evince-0.6.0/po/evince.pot [12:38] ./evince-0.6.0/help/evince.pot [12:38] ./build/evince-0.6.0/po/evince.pot [12:38] ./build/evince-0.6.0/help/evince.pot [12:38] ah, so it's fixed [12:38] carlos: right, it was a 0.5.5 issue [12:38] seb128: I see, ok [12:38] how many packages do you have lagging behind? [12:38] you just figured glib, gtk and evince were outdated in a few min [12:39] :p [12:39] seb128: not really, just that one was lagging behind [12:39] because it changed its filename [12:39] ok [12:39] in fact, later releases are already imported [12:39] when it was fixed [12:39] cool [12:39] so you just have to drop the "Evince" variant [12:39] right [12:39] already done === seb128 hugs carlos [12:40] seb128: ;-) [12:49] reviewer meeting in 11 === jml [n=nnjml@203-217-8-89.perm.iinet.net.au] has joined #launchpad [12:52] people calling carlos "mr. carlos" :) [12:57] jordi: well.... some girls in the university told me that already when asking for the 'time', really depressing... === carlos feels old [12:57] haha [12:57] hey man [12:57] I just shaved after nearly two months [12:57] and people say I got rid of 5 years :) [12:58] review meeting in 2 [12:58] well, that was being shaved.... so you are depressing me even more.... [12:58] ;-) [01:00] reviewer meeting starts now [01:00] == Agenda == [01:00] * Roll call [01:00] * Queue status. [01:01] = Roll Call = [01:01] hi [01:01] ho [01:01] hi [01:01] its off to work we go [01:01] hi [01:02] so the queue is in good shape [01:02] its packed, but nothing is overdue [01:02] congrats all [01:02] hi [01:03] 10 items oldest is 4 days, which is 2 adjusting for the weekend. They'll be overdue tomorrow though ;) [01:03] any comments or questions arond this ? [01:03] I'll make sure to finish off BjornT's branch soon [01:03] (1 minute to say so) [01:04] thanks jamesh [01:05] I suck, as I still haven't documented the escalation process [01:05] for post-merge reviews that should not have been done [01:05] whats the general feeling about those reviews? worth doing? many abuses? few abuses? [01:05] for post-merge reviews that reveal that merge should not have been done [01:06] I think they are good [01:06] there were a few problems in some revisions I reviewed that would have been caught during review, but no huge problems [01:07] I think we should keep doing this. I'll pickup the trivials weekly and allocate them. How does that sound ? [01:08] i think post-merge reviews have been useful. they are quick to do, and there have been some remarks on [trivial] merges. [01:08] weekly sounds good. [01:09] ok [01:09] lifeless: +! [01:09] er, +1 [01:14] haha [01:14] ok, thats preserved in the log ;) [01:14] any new business? [01:14] there was an issue ddaa brought up [01:14] in the last lp devel meeting [01:14] is that like a furball ? [01:14] that I told him to add to this meeting's agenda if he wanted it discussed [01:14] apparently he didn't, and I don't remember what it was [01:14] so, that's that then :-) [01:14] is it in the transcript from the meeting ? [01:14] yes [01:14] heh [01:14] in the literal log anyway [01:14] actually, there is a proposed item from ddaa on ReviewerMeetingAgenda [01:14] oh, I read right past that [01:14] my bad [01:14] ah, so ddaa did add it [01:14] * [01:14] Pending reviews to be assigned in two working days at most (ddaa) [01:14] thanks BjornT [01:14] ddaa: your floow [01:14] *floor* [01:14] hmm [01:14] save it for next time then? [01:14] SteveA: do you know what it was about specifically? I allocate daily, so I'm not sure what it means [01:14] when I'm away I ask another reviewer to allocate [01:14] I don't know. I think ddaa needs to explain. [01:14] agreed [01:14] ddaa: please explain [01:15] I have things to do [01:15] likewise [01:15] ok, ddaa can resubmit it when he reads scrollback [01:15] or bring it up with me, as its not a team wide issue [01:16] I have one item of 'other' [01:16] jamesh: hows the pending-reviews load ? [01:16] last week there was two days when allocation did not seem to have been done [01:16] for runs when no changes have taken place, it takes about 2 minutes to run now [01:17] jamesh: excellent [01:17] wed and thu .au time [01:17] so combined with locking against parallel runs, we could probably bump the frequency up a bit [01:17] ddaa: my routine is to allocate daily. Occasionally I dont manage to usually due to being insanely busy : i.e. last minute sprint for the smart server for bzr. [01:18] we discussed once-per-day for w-i-p [01:18] and much more frequently for branches for review [01:18] this might result in a run getting missed, occasionally, but it wouldn't be as important if it is more frequent [01:18] well lets start with the higher frequency i [01:18] lifeless: ack you were busy. Maybe at this point you could have somebody do the assigning for you. [01:18] its a smaller change in terms of human effourt [01:19] *effort* [01:19] SteveA: yeah. I haven't looked at doing that bit yet [01:19] ok [01:19] jamesh: what frequency do you think is feasible ? [01:19] jamesh: 30 minutes ? [01:20] 1 hr ? [01:20] SteveA: preventing unnecessary work was a bigger win, and I'd probably have needed to do the changes anyway to reduce the frequency of w-i-p branches [01:20] lifeless: it is currently on 1 hour. 30 minutes should be doable [01:20] cool [01:20] next week I'll be asking again [01:20] I'd like to understand where we can dial up to ;) [01:20] lifeless: previously the rsync jobs for oops reports seemed to be piling up due to the IO bandwidth being saturated [01:21] it might be worth doing an in-memory merge [01:21] I don't think they're locked against multiple runs too [01:21] so we were ending up with multiple rsync runs for the same data at times [01:21] ok, this is covered for now for me [01:22] jamesh: thats filed with the sysadmins right ? [01:22] lifeless: not yet. I'll do it after the meeting === cprov [n=cprov@monga.dorianet.com.br] has joined #launchpad [01:22] jamesh: thanks [01:22] any other other business ? [01:23] ddaa: if someone else wants to take it on, I'm happy to ask them to do it with SteveA/kiko's ok. However I consider myself responsible for getting the reviews allocated, so we'd be getting into matrix-mgmt territory, which is not so hot. [01:23] hmm, we are already in some ways. [01:24] SteveA: what do you think? Daily allocations are not fundamentally interesting, and the system seems to be ticking along very well now. [01:24] lifeless: I'm just suggesting that when you get into "insanely busy" mode, you just temporarily pass the pumpkin to someone else, so reviews keeps being assigned timely. Probably the same as you would do when going on vacation. [01:25] ddaa: I do - this case I didn't realise how much lilfting we had to do [01:25] thanks for raising the issue ddaa. let's leave things as they are and see if we get any problems in this area in the future [01:25] short of having two people doing the reviews daily each, I'm not sure how to prevent occasional glitches [01:25] Then let's consider that issue closed. I just though I had to complain about the hiccup last week :) [01:26] its nowhere near the Service level issues that we had some time ago with weeks going by [01:26] so I'm not very concerned about it [01:26] SteveA: agreed. [01:26] Sure, things are going on very smoothly. I'd hate to see that degrade. [01:27] lifeless: note that is an indirect praise :) [01:27] ok meeting closed [01:27] thanks y'all [01:28] lifeless: so, talk about BatchProgress? [01:29] sure [01:29] my problem with testing that is that Progress classes provide an API for bzrlib to use, and I do not see how to fail when the API used by bzrlib somehow changes [01:29] so [01:30] On problem I had was when nested progress was introduced, it caused BatchProgress to miss most of the progress because it was based on DummyProgress [01:30] you consider it a fault when the bzr api changes? or just when it changes such that BatchProgress does not output what its meant to for the operations used in importd ? [01:31]