=== mpt [n=mpt@219-89-131-42.jetstart.xtra.co.nz] has left #launchpad ["http://mpt.net.nz/"] === thierry_ [n=thierry@modemcable051.65-131-66.mc.videotron.ca] has joined #launchpad === GoRoDeK [n=gorodek@p5083E892.dip.t-dialin.net] has joined #launchpad [01:12] Does launchpad provide a possibility to receive support requests per mail? === jinty [n=jinty@G991a.g.pppool.de] has joined #launchpad === mick__ [n=mick@adsl-153-148-65.mia.bellsouth.net] has joined #launchpad === BjornT [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad === BjornT [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad === mpt [n=mpt@222-154-152-47.jetstream.xtra.co.nz] has joined #launchpad === poningru_ [n=poningru@n128-227-41-230.xlate.ufl.edu] has joined #launchpad === poningru [n=poningru@n128-227-41-230.xlate.ufl.edu] has joined #launchpad === mpt_ [n=mpt@222-154-180-231.jetstream.xtra.co.nz] has joined #launchpad === jsgotangco [n=jsg@ubuntu/member/jsgotangco] has joined #launchpad [07:18] jblack, you got pay per view? [07:20] jsgotangco: Why? [07:21] jblack, just wondering if you got to watch the fight (morales/pacquaio 2) [07:21] yeah. I watched it [07:21] Oh, no, not the second one. [07:21] Who won? [07:21] pacman [07:21] tko 10 [07:21] really! [07:21] he decked morales twice [07:23] I think I'm going to bed. I'm not feeling well [07:23] jblack: ping [07:24] o_O [07:26] later jblack rest well === GoRoDeK [n=gorodek@p5083E892.dip.t-dialin.net] has joined #launchpad === poningru [n=poningru@n128-227-13-82.xlate.ufl.edu] has joined #launchpad === mpt__ [n=mpt@219-89-150-86.jetstart.xtra.co.nz] has joined #launchpad === Dirty_Harry [i=Dirty_Ha@ACAC82E3.ipt.aol.com] has joined #launchpad [08:24] What's up? It's quiet === Dirty_Harry [i=Dirty_Ha@ACAC82E3.ipt.aol.com] has left #launchpad [] === Dirty_Harry [i=Dirty_Ha@ACAC82E3.ipt.aol.com] has joined #launchpad [08:28] ping === BjornT [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad [08:36] / === Dirty_Harry is away: I'm busy [08:40] hmm - LP timing out on changing an emblem [08:40] any idea? [08:48] librarian could be down I guess === poningru_ [n=poningru@n128-227-1-229.xlate.ufl.edu] has joined #launchpad === zyga [n=zyga@ubuntu/member/zyga] has joined #launchpad [10:35] anyone around? === kaarel [n=kaarel@ip227.cab29.mus.starman.ee] has joined #launchpad [10:35] I'm trying to get into dapper's xchat-gnome template for polish but I cannot find any [10:37] zyga: https://launchpad.net/distros/ubuntu/dapper/+source/xchat-gnome/+pots/xchat-gnome/pl/+translate [10:38] jamesh: thanks, why isn't it listed on the big list page for pl? [10:38] I thought this bug was fixed ages ago [10:41] zyga: is polish selected as one of your languages on https://launchpad.net/rosetta/prefs ? [10:41] jamesh: checking [10:42] jamesh: yes it is === GoRoDeK [n=gorodek@p5083E892.dip.t-dialin.net] has joined #launchpad [10:44] jamesh: I usually look for templates on this page: https://launchpad.net/distros/ubuntu/dapper/+lang/pl [10:44] it just got added after I visited the link you've sent ime [10:45] zyga: I believe there is a bug open about that. [10:45] zyga: you should see polish here: https://launchpad.net/distros/ubuntu/dapper/+source/xchat-gnome/+translations [10:46] (if it is selected as a preferred language) [10:46] jamesh: it works now, it seems that visiting that link has created the template [10:46] I'm listed as the creator [10:49] jamesh: strange [10:49] jamesh: I wanted to fix a bug in the translation [10:49] jamesh: some messages seem to have been incorrectly tagged as utf-8 while being latin-2 (comon issue) [10:50] jamesh: so if there are some translations, why wasn't the template page created automatically... [10:51] I need to find carlos :/ [10:57] does carlos come here on weekends? === GoRoDeK [n=gorodek@p5083E892.dip.t-dialin.net] has joined #launchpad [11:26] Need support on #pr3dators-klan.com after Quakenet probs on #pr3dators-klan.et ... (sorry for amsg and ad) [11:27] sorry, this message was for qnet only [11:33] any rosetta devs around? === jinty [n=jinty@Ga13e.g.pppool.de] has joined #launchpad === raptoid [n=raptoid@unaffiliated/raptoid] has joined #launchpad === mick__ [n=mick@adsl-11-149-32.mia.bellsouth.net] has joined #launchpad === mpt__ is now known as mpt [12:01] howdy all === jb-home [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #launchpad === zyga [n=zyga@ubuntu/member/zyga] has joined #launchpad [12:07] Looking at Bug 29290 - jamesh identifies it as an untrapped duplicate key failure. The other half of the question I guess should be a support request - how, then, do I target a bug to a particular version of software in Dapper? [12:07] Malone bug 29290: "OOPS-21D227 received while trying to target a bug" Fix req. for: launchpad (upstream), Severity: Normal, Assigned to: Nobody, Status: Unconfirmed http://launchpad.net/bugs/29290 [12:07] Do you guys look at the support requests at all, or is it best to ask in here for things like this? [12:08] jb-home: we don't have per-package milestones at the moment [12:08] which is essentially what you want [12:08] wheeeooo [12:09] love those 1/2 hour to write emails. [12:09] lifeless: 1/2? that must be a long email.. [12:09] actually, wow. more like an hour [12:09] sivang: extending the transaction api in bzr [12:09] jamesh: Ah, okay. So I've just included the text "dapper" and "0.9-0ubuntu1" in the body of the message then, and this is best practice for now? [12:10] finally figured out what had me spooked about some of the adhoc patches [12:10] any devs around? [12:10] jb-home: there is an item in the actions portlet "target fix to releases" [12:10] zyga: FSVO yes [12:10] I'd like to raise the issue of common problems t [12:11] lifeless: ah, figures then you'll probbly need more then one or two long emails , if your going to extend an api :-) [12:11] I'd like to raise the issue of common problems due to invalid content encoding in .po files [12:11] jb-home: you can target it at Dapper there, which will open another bug task (enabling you to track the bug in each of the releases it needs to be fixed int) [12:11] sivang: mainly I needed time doing nothing else to work through the issues [12:11] jamesh: I saw that, but it looked like something as the reporter I should never set (It's not up to me to say where something *must* be fixed. It's only up to me to say where it's broken.) [12:11] so that I can explain why I was going 'No, dont do that' to people, when what they wanted sounded reasonable on the surface [12:11] we have some pretty high goals for bzr in a technical sense [12:12] jb-home: okay, so you want to say "this bug occurs in 0.9-0ubuntu1" [12:12] jamesh: Right. Or at a minimum, this bug occurs in dapper. [12:12] I'd like to propose a system for rosetta that would preprocess all incoming files to determine the true encoding, if not set correctly and re-encode to unicode [12:12] jb-home: we _do_ have something in the data model to handle this (bug infestations), but we don't have any UI for it [12:12] jamesh: But it started as at a specific version, and it seems like useful metadata. [12:12] I'm working on a reference implementation that targets common errors in polish templates [12:13] lifeless: interesting. Is there anything documented online about it? (could be a nice way to learn just about more bits about bzr) [12:13] jamesh: Fair enough. Is there anything I can usefully capture in an enhancement bug report from this conversation? [12:13] jb-home: sure. The bug infestation idea is to be able to attach metadata to the bug like "occurs in version X.Y" or "does not occur in version X.Y+1" [12:13] sivang: well, theres the bzrlib.transactions api, theres my new email about it [12:14] and be able to use that data to narrow down problems [12:14] but there is no UI for that (there is just a table definition at the moment, iirc) [12:14] any hints on who should I contact? [12:14] Ah! I see it here as #424 [12:15] jb-home: so at the moment, including it as a comment is probably best === sivang searches for bzr's ml archives [12:17] lists.canonical.com [12:17] bazaar-ng is the lsit === mick__ [n=mick@adsl-153-192-12.mia.bellsouth.net] has joined #launchpad [12:20] jamesh: Thanks. [12:21] jb-home: btw [12:21] we can just about fix the versioning on the bzr packages [12:22] this is a reminder to switch to ~ for 8 [12:22] lifeless: Thanks for the reminder. [12:23] np === jb-home [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has left #launchpad ["Ex-Chat"] === sivang searches for jblack === jb-home [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #launchpad === jb-home [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has left #launchpad ["Ex-Chat"] === jb-home [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #launchpad === jsgotangco [n=jsg@ubuntu/member/jsgotangco] has joined #launchpad [12:41] Where's the right place to report bugs on the bugzilla migration? [12:42] jamesh: [12:42] malone? [12:44] jsgotangco: Do you know against which product? [12:45] well you can probably file it to malone itself [12:47] there is a launchpad product [12:47] but jamesh is the person to chat with [12:48] 'kay. I'll wait a bit to see if he resurfaces. [12:48] lifeless: I wasn't sure about the launchpad product, since it's not launchpad that has the bug. [12:48] lifeless: Thanks! [12:50] np [12:52] how often does launchpad like - see what packages are available [12:53] jb-home: what is the problem? [12:53] lol - cause it's still showing old versions of packages and stuff [12:53] jamesh: I have two things that have come up: [12:54] 1) bugzilla doesn't appear to be read only, and I got a new comment filed on an existing bug. [12:54] (18157) [12:54] 2) Malone bug#24190 was correctly imported, but doesn't show up on my list of reported bugs. [12:54] jb-home: that would be an RT request. We can probably make the database readonly at the moment [12:55] jamesh: I think it probably also means another import run. =( [12:55] jamesh: I pretty much only happened to notice this one, but generally I have bugzilla mail disabled. [12:55] jb-home: that's a little difficult. [12:55] So people could be commenting on existing bugs and I'd have no way of knowing about it, and the data won't be in malone. [12:56] jb-home: I'm guessing some existing login sessions are active (we disabled login for all existing accounts) [12:57] jb-home: your (2) is https://launchpad.net/products/malone/+bug/4201 [12:57] Malone bug 4201: "Bugs with NeedInfo status should be displayed on open bugs query." Fix req. for: malone (upstream), Severity: Normal, Assigned to: Nobody, Status: Needs Info === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad [12:58] jamesh: Ah, no wonder the keywords I guessed didn't give me the bug. =) [12:59] Right, 4201 definetly looks like what I'm hitting here. [01:00] So I only have one data loss issue, not two. =P [01:01] for (1), we probably want to do a "delete from logincookies" on the bugzilla DB [01:01] we don't currently have the ability to do incremental comment imports from bugzilla though. [01:02] the script I wrote was for a one-off import [01:02] Ugh. [01:02] Is there any way to do a system-wide query to see how much data is being lost? [01:02] If it's just a dozen or so, those folks can be contacted to file the data in the right place. [01:02] Otherwise it might be worth developing the scripts to do it. [01:03] there is a date associated with each comment. We could probably tell how many comments have been made. === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad [01:04] jamesh: Is there anything useful I can add to this? === siretart [i=siretart@ubuntu/member/siretart] has joined #launchpad === heyko [n=heyko@tor/session/x-a3e2e226b9b6e266] has joined #launchpad === jinty [n=jinty@dslb-084-059-073-001.pools.arcor-ip.net] has joined #launchpad === jb-home [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has left #launchpad ["Ex-Chat"] === jinty [n=jinty@dslb-084-059-073-001.pools.arcor-ip.net] has joined #launchpad === eldiablo [i=kvirc@host162-207.pool80104.interbusiness.it] has joined #launchpad [01:51] buonciorno [01:51] ciao === Alinux [n=Ubuntu@d83-176-75-33.cust.tele2.it] has joined #launchpad === Mez [n=Mez@ubuntu/member/mez] has joined #launchpad === AlinuxOS [n=Ubuntu@d83-176-75-33.cust.tele2.it] has joined #launchpad === heyko_ [n=heyko@onion.silicon-verl.de] has joined #launchpad === Alinux [n=Ubuntu@d83-176-13-47.cust.tele2.it] has joined #launchpad === Servantes [n=Ubuntu@d83-176-90-73.cust.tele2.it] has joined #launchpad === Sin [n=Sin@AToulouse-157-1-38-108.w86-201.abo.wanadoo.fr] has joined #launchpad === tambaqui [n=patricia@200-208-53-24-mns.cpe.vivax.com.br] has joined #launchpad === muadda [n=muadda@gar31-3-82-234-50-167.fbx.proxad.net] has joined #launchpad [07:39] We cannot yet use launchpad to browse Debian bugs ? === mpt [n=mpt@219-89-150-86.jetstart.xtra.co.nz] has joined #launchpad === mick__ [n=mick@adsl-2-49-83.mia.bellsouth.net] has joined #launchpad === zyga [n=zyga@ubuntu/member/zyga] has joined #launchpad [08:02] hello === tambaqui [n=patricia@200-208-53-24-mns.cpe.vivax.com.br] has joined #launchpad === mick__ is now known as mick_home [08:14] muadda, no, debian doesn't use launchpad [08:15] mdke, malone/launchpad cannot look bugs in the debian BTS database? [08:16] muadda, no [08:17] If a project has already a bugzilla and want to keep its bugzilla... can malone communicate with this bugzilla ? [08:22] muadda, I don't know, i don't think so. What do you mean by communicate? [08:25] I'm trying to understand the malone concept ;) If I report a bug on malone and I click on the "Request fix Upstream" link, malone may know the upstream bugzilla and automatically open the bug on the upstream bugzilla. Can malone do that ? [08:26] and if upstream authors add some comments on their bugzilla, these comments may be available on the malone page (?) === mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #launchpad [08:40] muadda, the idea is that if the upstream project uses malone too, the bug can be reported there. If it doesn't, the Request fix Upstream is pretty useless right now, afaik [08:41] mdke, ok, I understand better now. Thanks [08:42] muadda, np, lots of people are confused by that. Because it is confusing :) === mpt [n=mpt@202.53.187.9] has joined #launchpad === mick__ [n=mick@adsl-149-0-13.mia.bellsouth.net] has joined #launchpad === lfittl [n=lfittl@83-65-242-100.dynamic.xdsl-line.inode.at] has joined #launchpad === Burgundavia [n=corey@S0106000000cc07fc.gv.shawcable.net] has joined #launchpad === Nafallo_away is now known as Nafallo === mick__ [n=mick@adsl-11-54-168.mia.bellsouth.net] has joined #launchpad === mick_home [n=mick@adsl-149-1-45.mia.bellsouth.net] has joined #launchpad === interalia [n=interali@adsl-60-232.swiftdsl.com.au] has joined #launchpad === fabbione [i=fabbione@gordian.fabbione.net] has joined #launchpad