[01:12] <Seveas> Does launchpad provide a possibility to receive support requests per mail?
[07:18] <jsgotangco> jblack, you got pay per view?
[07:20] <jblack> jsgotangco: Why? 
[07:21] <jsgotangco> jblack, just wondering if you got to watch the fight (morales/pacquaio 2)
[07:21] <jblack> yeah. I watched it
[07:21] <jblack> Oh, no, not the second one.
[07:21] <jblack> Who won? 
[07:21] <jsgotangco> pacman
[07:21] <jsgotangco> tko 10
[07:21] <jblack> really!
[07:21] <jsgotangco> he decked morales twice
[07:23] <jblack> I think I'm going to bed. I'm not feeling well
[07:23] <Mez> jblack: ping
[07:24] <Mez> o_O
[07:26] <jsgotangco> later jblack rest well
[08:24] <Dirty_Harry> What's up? It's quiet
[08:28] <Dirty_Harry> ping
[08:36] <Dirty_Harry> /
[08:40] <Mez> hmm - LP timing out on changing an emblem
[08:40] <Mez> any idea?
[08:48] <lifeless> librarian could be down I guess
[10:35] <zyga> anyone around?
[10:35] <zyga> I'm trying to get into dapper's xchat-gnome template for polish but I cannot find any
[10:37] <jamesh> zyga: https://launchpad.net/distros/ubuntu/dapper/+source/xchat-gnome/+pots/xchat-gnome/pl/+translate
[10:38] <zyga> jamesh: thanks, why isn't it listed on the big list page for pl?
[10:38] <zyga> I thought this bug was fixed ages ago
[10:41] <jamesh> zyga: is polish selected as one of your languages on https://launchpad.net/rosetta/prefs ?
[10:41] <zyga> jamesh: checking
[10:42] <zyga> jamesh: yes it is
[10:44] <zyga> jamesh: I usually look for templates on this page: https://launchpad.net/distros/ubuntu/dapper/+lang/pl
[10:44] <zyga> it just got added after I visited the link you've sent ime
[10:45] <jamesh> zyga: I believe there is a bug open about that.
[10:45] <jamesh> zyga: you should see polish here: https://launchpad.net/distros/ubuntu/dapper/+source/xchat-gnome/+translations
[10:46] <jamesh> (if it is selected as a preferred language)
[10:46] <zyga> jamesh: it works now, it seems that visiting that link has created the template
[10:46] <zyga> I'm listed as the creator
[10:49] <zyga> jamesh: strange
[10:49] <zyga> jamesh: I wanted to fix a bug in the translation
[10:49] <zyga> jamesh: some messages seem to have  been incorrectly tagged as utf-8 while being latin-2 (comon issue)
[10:50] <zyga> jamesh: so if there are some translations, why wasn't the template page created automatically...
[10:51] <zyga> I need to find carlos :/
[10:57] <zyga> does carlos come here on weekends?
[11:26] <stgraber> Need support on #pr3dators-klan.com after Quakenet probs on #pr3dators-klan.et ... (sorry for amsg and ad)
[11:27] <stgraber> sorry, this message was for qnet only
[11:33] <zyga> any rosetta devs around?
[12:01] <sivang> howdy all
[12:07] <jb-home> 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] <Ubugtu> 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] <jb-home> Do you guys look at the support requests at all, or is it best to ask in here for things like this?
[12:08] <jamesh> jb-home: we don't have per-package milestones at the moment
[12:08] <jamesh> which is essentially what you want
[12:08] <lifeless> wheeeooo
[12:09] <lifeless> love those 1/2 hour to write emails.
[12:09] <sivang> lifeless: 1/2? that must be a long email..
[12:09] <lifeless> actually, wow. more like an hour
[12:09] <lifeless> sivang: extending the transaction api in bzr
[12:09] <jb-home> 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] <lifeless> finally figured out what had me spooked about some of the adhoc patches
[12:10] <zyga> any devs around?
[12:10] <jamesh> jb-home: there is an item in the actions portlet "target fix to releases"
[12:10] <lifeless> zyga: FSVO yes
[12:10] <zyga> I'd like to raise the issue of common problems t
[12:11] <sivang> lifeless: ah, figures then you'll probbly need more then one or two long emails , if your going to extend an api :-)
[12:11] <zyga> I'd like to raise the issue of common problems due to invalid content encoding in .po files
[12:11] <jamesh> 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] <lifeless> sivang: mainly I needed time doing nothing else to work through the issues
[12:11] <jb-home> 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] <lifeless> 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] <lifeless> we have some pretty high goals for bzr in a technical sense
[12:12] <jamesh> jb-home: okay, so you want to say "this bug occurs in 0.9-0ubuntu1"
[12:12] <jb-home> jamesh: Right.  Or at a minimum, this bug occurs in dapper.
[12:12] <zyga> 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] <jamesh> 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] <jb-home> jamesh: But it started as at a specific version, and it seems like useful metadata.
[12:12] <zyga> I'm working on a reference implementation that targets common errors in polish templates
[12:13] <sivang> lifeless: interesting. Is there anything documented online about it? (could be a nice way to learn just about more bits about bzr)
[12:13] <jb-home> jamesh: Fair enough.  Is there anything I can usefully capture in an enhancement bug report from this conversation?
[12:13] <jamesh> 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] <lifeless> sivang: well, theres the bzrlib.transactions api, theres my new email about it
[12:14] <jamesh> and be able to use that data to narrow down problems
[12:14] <jamesh> but there is no UI for that (there is just a table definition at the moment, iirc)
[12:14] <zyga> any hints on who should I contact?
[12:14] <jb-home> Ah!  I see it here as #424
[12:15] <jamesh> jb-home: so at the moment, including it as a comment is probably best
[12:17] <lifeless> lists.canonical.com
[12:17] <lifeless> bazaar-ng is the lsit
[12:20] <jb-home> jamesh: Thanks.
[12:21] <lifeless> jb-home: btw
[12:21] <lifeless> we can just about fix the versioning on the bzr packages
[12:22] <lifeless> this is a reminder to switch to ~ for 8
[12:22] <jb-home> lifeless: Thanks for the reminder.
[12:23] <lifeless> np
[12:41] <jb-home> Where's the right place to report bugs on the bugzilla migration?
[12:42] <lifeless> jamesh: 
[12:42] <jsgotangco> malone?
[12:44] <jb-home> jsgotangco: Do you know against which product?
[12:45] <jsgotangco> well you can probably file it to malone itself
[12:47] <lifeless> there is a launchpad product
[12:47] <lifeless> but jamesh is the person to chat with
[12:48] <jb-home> 'kay.  I'll wait a bit to see if he resurfaces.
[12:48] <jb-home> lifeless: I wasn't sure about the launchpad product, since it's not launchpad that has the bug.
[12:48] <jb-home> lifeless: Thanks!
[12:50] <lifeless> np
[12:52] <Mez> how often does launchpad like - see what packages are available
[12:53] <jamesh> jb-home: what is the problem?
[12:53] <Mez> lol - cause it's still showing old versions of packages and stuff
[12:53] <jb-home> jamesh: I have two things that have come up:
[12:54] <jb-home> 1) bugzilla doesn't appear to be read only, and I got a new comment filed on an existing bug.
[12:54] <jb-home> (18157)
[12:54] <jb-home> 2) Malone bug#24190 was correctly imported, but doesn't show up on my list of reported bugs.
[12:54] <jamesh> jb-home: that would be an RT request.  We can probably make the database readonly at the moment
[12:55] <jb-home> jamesh: I think it probably also means another import run. =(
[12:55] <jb-home> jamesh: I pretty much only happened to notice this one, but generally I have bugzilla mail disabled.
[12:55] <jamesh> jb-home: that's a little difficult.
[12:55] <jb-home> 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] <jamesh> jb-home: I'm guessing some existing login sessions are active (we disabled login for all existing accounts)
[12:57] <jamesh> jb-home: your (2) is https://launchpad.net/products/malone/+bug/4201
[12:57] <Ubugtu> 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
[12:58] <jb-home> jamesh: Ah, no wonder the keywords I guessed didn't give me the bug. =)
[12:59] <jb-home> Right, 4201 definetly looks like what I'm hitting here.
[01:00] <jb-home> So I only have one data loss issue, not two. =P
[01:01] <jamesh> for (1), we probably want to do a "delete from logincookies" on the bugzilla DB
[01:01] <jamesh> we don't currently have the ability to do incremental comment imports from bugzilla though.
[01:02] <jamesh> the script I wrote was for a one-off import
[01:02] <jb-home> Ugh.
[01:02] <jb-home> Is there any way to do a system-wide query to see how much data is being lost?
[01:02] <jb-home> If it's just a dozen or so, those folks can be contacted to file the data in the right place.
[01:02] <jb-home> Otherwise it might be worth developing the scripts to do it.
[01:03] <jamesh> there is a date associated with each comment.  We could probably tell how many comments have been made.
[01:04] <jb-home> jamesh: Is there anything useful I can add to this?
[01:51] <eldiablo> buonciorno
[01:51] <eldiablo> ciao
[07:39] <muadda> We cannot yet use launchpad to browse Debian bugs ?
[08:02] <zyga> hello
[08:14] <mdke> muadda, no, debian doesn't use launchpad
[08:15] <muadda> mdke, malone/launchpad cannot look bugs in the debian BTS database?
[08:16] <mdke> muadda, no
[08:17] <muadda> If a project has already a bugzilla and want to keep its bugzilla... can malone communicate with this bugzilla ?
[08:22] <mdke> muadda, I don't know, i don't think so. What do you mean by communicate?
[08:25] <muadda> 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] <muadda> and if upstream authors add some comments on their bugzilla, these comments may be available on the malone page (?)
[08:40] <mdke> 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] <muadda> mdke, ok, I understand better now. Thanks
[08:42] <mdke> muadda, np, lots of people are confused by that. Because it is confusing :)