[00:03]  * Hobbsee curses launchpad
[00:04] <Hobbsee> no really, when my package has finished making the change, i really don't give a damn about whether otherp ackages have...
[00:04] <Hobbsee> what's the package i want to send it to, to stop giving me excess bugmail again?
[00:07] <rockstar> Hobbsee, I'm not quite sure what you're asking
[00:08] <Hobbsee> rockstar: https://bugs.edge.launchpad.net/ubuntu/+source/ubuntu-restricted-extras/+bug/203636/ - i get mail for u-r-e, which is marked as fix released, but i'm still getting mail for all the other changes on that bug
[00:09] <rockstar> Hobbsee, I see your name in the also notified.  Modify your subscription.
[00:11] <Hobbsee> rockstar: how?
[00:13] <rockstar> Hobbsee, there's an "Edit your subscription" action
[00:14] <Hobbsee> rockstar: where?
[00:14] <Hobbsee> rockstar: page find isn't finding it.
[00:15] <Hobbsee> and while i normally can't find things i want on launchpad in the past few months, i still expect page find to find it, if it's there.
[00:15] <rockstar> Oh, it's Unsubscribe on that page.
[00:15] <Hobbsee> oh dear.  u-u-s has been specifically subscribed to that bug.  that'll make people happy...
[00:16] <rockstar> Sorry, the code team named it "Edit your subscription"
[00:16] <Hobbsee> i don't have an unsubscrib link.  i'm subscribed to the bugs for that package.
[00:18] <rockstar> Hobbsee, I'd recommend tuning your procmail setup
[00:18] <kiko> Hobbsee, visit the package page and edit your subscription there
[00:18] <Hobbsee> rockstar: to /dev/null all launchpad bugs?  tempting.
[00:18] <kiko> so if you're looking at a bug in gdm
[00:18] <rockstar> Hobbsee, :)
[00:18] <kiko> click on overview
[00:18] <kiko> and then change the package contact
[00:19] <Hobbsee> kiko: i want the mail from all the other bugs for that package.  just not ones that i've already fixed in that package, and don't care about the other packages for.
[00:20] <Hobbsee> rockstar: i've often pondered that, as I get shedloads of bugmail.  usually, it's stuff that i actually care about, but there are implicit mails from stuff that i'm not, someitmes.
[00:20] <kiko> Hobbsee, oh.. I see, you're talking about those multiple-task bugs
[00:21] <rockstar> Yea, I understand that.  I've spent a few hours sorting out my mail filters.
[00:21] <Hobbsee> yes.
[00:21] <rockstar> kiko, maybe a bug status mail header is in order?
[00:21] <Hobbsee> rockstar: actually, i split up all my way as well.  but launchpad doesn't seem to have a "i care about this" header, and an "i don't care about this" header.
[00:21] <Hobbsee> rockstar: now there's an idea...that actually exists.
[00:22] <rockstar> Hobbsee, but we do have some pretty good headers for sorting mail.
[00:22] <Hobbsee> rockstar: indeed.
[00:22] <kiko> rockstar, there already is a header. she can already do that. :)
[00:22] <rockstar> Apparently
[00:22] <rockstar> kiko, I'm on the code team, remember?  :)
[00:22] <Hobbsee> that may actually be the answer to implicit subscriptions...or at least, a workaround.
[00:23] <kiko> rockstar, yeah, I'm not being sheepish
[00:23] <kiko> what Hobbsee would like even better, though, to which I'm sympathetic, is being able to unsubscribe to implicitly subscribed bugs.
[00:23] <rockstar> kiko, I think that there is that functionality in code.  The basic idea is that you subscribe and say "Don't send me any mail"
[00:24] <Hobbsee> X-Launchpad-Bug: distribution=ubuntu; sourcepackage=ubuntu-restricted-extras;
[00:24] <Hobbsee>         component=multiverse; status=Fix Released; importance=Undecided;
[00:24] <Hobbsee>         assignee=None;
[00:24] <Hobbsee> that would work....
[00:24] <kiko> right
[00:24] <Hobbsee> and just hard-code it for any other packages as relevant.
[00:25] <rockstar> Hobbsee, sounds like you probably don't care to hear about any bugs after Fix Committed, right?
[00:26] <Hobbsee> rockstar: depends.  if they're legitimate bugs in my package, then yes.
[00:26] <Hobbsee> rockstar: if the stuff is about *other* packages, then no.
[00:26] <rockstar> I see.
[00:26] <Hobbsee> i don't care to hear about any bugs after marking them invalid or won't fix, usually
[00:26] <Hobbsee> unless someone reopens it
[00:27] <Hobbsee> (ie, people get the wrong package, i get mail, it's not my fault, i mark as invalid, but still get mail)
[00:27]  * rockstar ponders writing a blog post about Launchpad headers
[00:27] <Hobbsee> methinks header :contains "X-Launchpad-Bug" "sourcepackage=ubuntu-restricted-extras: *status=Fix Released" might do it.
[00:29] <Hobbsee> rockstar: kiko, thanks.
[00:30] <rockstar> Hobbsee, yea, no problem
[00:34] <NCommander> Hey Hobbsee
[00:34] <Hobbsee> hey NCommander!
[00:35] <NCommander> how goes it Hobbsee
[00:36] <Hobbsee> ok.  filtering email
[00:50] <RichW> When will the mailing list for https://launchpad.net/~pygamedb be approved?
[00:50] <RichW> its taking a while...
[00:50] <RichW> is there a big backlog?
[00:53] <kiko> RichW, when was it requested?
[00:53] <kiko> barry, ^^
[00:54] <RichW> I dont remember.
[00:54] <RichW> few days ago
[00:55] <RichW> is there a lack of staff to approve them?
[01:02] <kiko> RichW, it's a bit unusual as this is quite a good process
[01:04]  * kiko looks at barry 
[01:05] <barry> approved
[01:06] <RichW> oh goodness, we in process of project renaming, seems that causes some problems.
[01:07] <RichW> since have a mailing list now.
[01:07] <RichW> il try deactivate and see if it allows me.
[01:09] <RichW> im not so sure you can truly change the name of a team or project in launchpad
[01:09] <RichW> the url stays the same
[01:09] <kiko> RichW, you can for both.
[01:10] <kiko> RichW, you can't change the name of the team if it has a mailing list yet
[01:10] <RichW> it takes time for the url to change?
[01:10] <RichW> if i rename a project
[01:11] <kiko> RichW, no, just request it via answer.launchpad.net/launchpad
[01:12] <RichW> Ah, thanks.
[01:12] <kiko> it's super-fast
[01:12] <RichW> Il just rename what i can right now.
[01:12] <RichW> and then file the request.
[01:20] <kiko> sure thingo
[02:19] <javaJake> I hate to be a bugger and a n00b. :/
[02:19] <javaJake> At the same time
[02:20] <javaJake> Anyway, my public key is getting rejected all of a sudden
[02:20] <javaJake> I just checked, and the online version matches the one I have on file.
[02:21] <javaJake> Any ideas? :/
[02:22] <mars> javaJake, it could be for the site upgrade we are running right now.
[02:22] <javaJake> mars: haha, no kidding :P
[02:22] <javaJake> I thought they ran at midnight...
[02:23]  * javaJake does some UTC conversion in his head
[02:23] <javaJake> Ah, yep
[02:23] <mars> it's 01:23 UTC atm
[02:23] <javaJake> That'd make sense
[02:23] <javaJake> Yea, yea
[02:23] <javaJake> Rats, well, I'll just commit --local for now then
[02:23]  * javaJake loves bazaar for that...
[02:39] <spm> FYI ALL: rollout complete
[02:42] <jkakar> I'm getting weird errors when trying to bzr pull or bzr update lp: branches: Permission denied (publickey).
[02:42] <jkakar> bzr: ERROR: Connection closed: please check connectivity and permissions (and try -Dhpss if further diagnosis is required)
[02:43] <jkakar> Which I guess shouldn't be happening now that the rollout is complete?
[02:44] <jml> jkakar: no, it shouldn't.
[02:45]  * jml can't log in either.
[02:45]  * jml chases up
[02:49] <mwhudson> uh oh
[02:49] <jml> yeah.
[02:53] <Hobbsee> oh dear
[02:54] <jkakar> Still happening here...
[02:54] <jml> it's being fixed right now.
[03:18] <lifeless> question 42740
[03:19] <jml> lifeless: yes?
[03:19] <jml> lifeless: what about it?
[03:19] <lifeless> just letting you know its there :P
[03:20] <jml> lifeless: I'm all over it like a tonne of bricks.
[03:24] <RAOF> Hm.  I presume the rollout didn't include a downgrade to bzr < 1.2?
[03:25] <jml> RAOF: certainly not. why do you ask?
[03:26] <RAOF> Getting the message "Server is too old for streaming pull, reconnecting.  (Upgrade the server to Bazaar 1.2 to avoid this)" when pulling from lp.
[03:26] <mwhudson> !?
[03:26] <mwhudson> which client version?
[03:27] <RAOF> Bazaar (bzr) 1.5
[03:27] <RAOF> Fresh from the Intrepid repositories.
[03:30] <mwhudson> RAOF: doesn't happen for me
[03:30] <mwhudson> RAOF: can you reproduce?
[03:30] <RAOF> It only did it for one of my branches, actually.
[03:30] <mwhudson> hmm
[03:30] <mwhudson> was it in some old format?
[03:31] <RAOF> Just checking... it's a pack-0.92 branch in a pack-0.92 repository, so no.
[03:32] <mwhudson> hmm
[03:32] <RAOF> https://code.edge.launchpad.net/~do-plugins/do-plugins/trunk is the branch that triggered the message.
[03:34] <lifeless> 1.5 uses a verb 1.6 does not support
[03:35] <mwhudson> oh
[03:35] <mwhudson> ah yes, that rings a bell actually
[03:52] <jjesse> good evening i was doing a bzr merge of kubuntu-docs and saw a note that said "Server is too old for steaming pull, reconnecting.  (Upgrade the server to Bazaar 1.2 to avoid this)
[03:54] <Ursinha> mwhudson, ^
[03:55] <jml> jjesse: which version of bzr are you using?
[03:55] <jjesse> jml: bzr 1.5 under intrepid
[03:56] <mwhudson> it's a 1.5 vs 1.6 interaction
[03:56] <jjesse> nothing i need to worry about then?
[03:58] <_steven_> are code reviews only for merge proposals?
[04:01] <jml> jjesse: nothing you need to worry about.
[04:01] <jml> _steven_: basically, yes.
[04:02] <_steven_> why can't this be applied to patches submitted in bugs as well?
[04:02] <jjesse> jml thanks
[04:29] <lifeless> _steven_: its not hooked up yet
[04:29] <lifeless> _steven_: but that sort of thing is planned yes
[04:30] <lifeless> _steven_: you would do it by attaching a branch to the bug today
[04:34] <_steven_> lifeless: cool, thanks
[04:52] <days_of_ruin> "Unsupported protocol for url"
[04:52] <days_of_ruin> why do i get that error?
[04:53] <days_of_ruin> I can't push code to my launchpad project ;_;
[04:53] <mwhudson> days_of_ruin: known problem, working right now to fix it
[04:55] <days_of_ruin> Is there a workaround?
[04:55] <days_of_ruin> Is that why launchpad went offline earlier today?
[04:56] <mwhudson> no, the downtime was for an update
[04:56] <mwhudson> the problem is with the update :/
[04:57] <days_of_ruin> So is is everyone else having the same problem since the update?
[04:57] <mwhudson> yes
[04:58] <days_of_ruin> How soon will it be working again?
[04:59] <mwhudson> a few minutes, hopefully
[05:14] <LaserJock> so did the issue not manifest itself on edge?
[05:17] <jml> LaserJock: there is no bazaar.edge.launchpad.net
[05:17] <jml> LaserJock: or at least, there's no ssh server there :)
[05:18] <jml> LaserJock: it didn't manifest itself on staging because the root cause involves network topology.
[05:19] <jml> you know, we should think about doing edge rollouts for codehosting.
[05:20] <mwhudson> yeah, would be good
[05:20] <jml> and possible, I think.
[05:20] <jml> which is always a winner :)
[05:21] <mwhudson> :)
[05:28] <LaserJock> so right no codehosting changes are just done at each production rollout?
[05:28] <LaserJock> *now
[05:31] <lifeless> LaserJock: in general, we don't change any production thing except at rollouts
[05:31] <lifeless> LaserJock: cherrypicks and other exceptions do of course occur
[05:32] <LaserJock> well, I mean for Malone, etc. stuff lands on edge first before the rollout, right?
[05:34] <jml> right.
[05:34] <jml> at the moment, there's no edge-equivalent for codehosting.
[05:34] <jml> but there is a staging server.
[05:35] <jml> LaserJock: changes to the webapp part of code make it to edge, of course.
[05:37] <LaserJock> I guess I naively thought it was more all-or-nothing
[05:38] <fitoria> hi
[05:38] <jml> fitoria: hi
[05:39] <fitoria> I have a LP branch
[05:39] <fitoria> but
[05:39] <fitoria> there is a problem
[05:39] <fitoria> https://code.launchpad.net/~sfd-reg-team/sfd-reg/main
[05:39] <fitoria> Unsupported protocol for url "lp-hosted:///~sfd-reg-team/sfd-reg/main"
[05:39] <fitoria> it stoped updating it up to revision 6 I am in revision 9 right now
[05:39] <jml> fitoria: yeah, there's a problem on Launchpad that's causing that.
[05:39] <fitoria> jml: any way to solve it?
[05:40] <jml> fitoria: we're working on it right now.
[05:40] <fitoria> ok
[05:40] <fitoria> I'll wait
[05:40] <jml> fitoria: if you hang around in the channel, we'll let you know when it should be working.
[05:41] <warren> ssh: connect to host bazaar.launchpad.net port 22: Connection refused
[05:42] <warren> known?
[05:42] <mwhudson> warren: we're rolling out new code to fix some problems we've been having
[05:42] <spm> warren: yes - fixing a rollout buglet. should be back RSN
[05:42] <warren> cool
[05:43] <LaserJock> I guess on the good side, we know people actually use bazaar.launchpad.net ;-)
[05:45] <jml> LaserJock: trust me, the launchpad-bazaar team is very conscious of that :)
[05:48] <warren> I deny using it
[05:48] <mwhudson> it should be fixed now
[08:06] <\sh> shermann@build-emt64:~/workspace$ bzr branch lp:leonov
[08:06] <\sh> Enter passphrase for key '/home/shermann/.ssh/id_rsa_launchpad':
[08:06] <\sh> Server is too old for streaming pull, reconnecting.  (Upgrade the server to Bazaar 1.2 to avoid this)
[08:06] <\sh> Enter passphrase for key '/home/shermann/.ssh/id_rsa_launchpad':
[08:06] <\sh> hmmm?
[08:10] <\sh> using bzr from hardy ... I never had this before
[08:10] <RAOF> Heh.
[08:11]  * RAOF was first! Nyah!
[08:11] <BjornT> jml, mwhudson, thumper: ^^^^
[08:11] <\sh> hah...I wasn't the first one ,-)
[08:11] <mwhudson> it's a bzr buglet
[08:11] <mwhudson> nothing too serious, fortunately
[08:11] <\sh> a wth what?
[08:11] <\sh> bzr buglet?
[08:12] <\sh> bzr help buglet -> no help could be found for 'buglet' please use "bzr help topics" ;)
[08:12] <\sh> !bablefish buglet
[08:13] <RAOF> \sh: A little bug.
[08:13] <RAOF> bug+let, the same construction for app+let, pig+let, etc :)
[08:14] <\sh> RAOF: well...
[08:56] <sadleder> hi all, i have a question regarding launchpad-cscvs and a failing code import
[08:57] <sadleder> the branch  in question is https://code.launchpad.net/~vcs-imports/mpich/trunk and it will soon fail importing the third time in a row
[08:59] <jml> \sh: it's a known issue with bazaar 1.5 and bazaar 1.6 interaction
[09:01] <\sh> jml: well, I think I use a backport of latest bzr then ;)
[09:01] <jml> \sh: I use the version in the ~bzr ppa
[09:02] <jml> (when I'm not using bzr.dev — three cheers for vcs hacking)
[09:03] <sadleder> i think that branch will need manual intervention
[09:09] <thumper> sadleder: I've marked it failing
[09:10] <sadleder> thumper: will those marked branches be processed?
[09:10] <thumper> sadleder: no, the failure it is getting I think is a bug in cscvs, or at least requires some investigation
[09:11] <thumper> sadleder: they won't spontaneously start working
[09:11] <sadleder> sadleder: sorry, i meant if someone will be looking over those
[09:12] <thumper> sadleder: we have someone looking at cscvs code at the moment
[09:13] <thumper> sadleder: I'll make sure we look at this too
[09:13] <sadleder> thumper: thank you
[09:19] <mwhudson> my guess on looking at that import was that it might have been related to keywords
[09:23] <mwhudson> hm, no it's deeper than that
[09:24] <mwhudson> it looks like the importer is missing some changes
[09:24] <mwhudson> it might be this bug: https://bugs.edge.launchpad.net/launchpad-cscvs/+bug/121569
[09:32] <sadleder> mwhudson: should i mark that bug "also affects" mpich?
[09:32] <sadleder> mwhudson: or just add a link to that branch?
[09:32] <mwhudson> sadleder: add a link, perhaps
[09:32] <mwhudson> i don't think anyone has put much effort into understanding that bug yet
[09:33] <wgrant> Or add a link using the much-wanted 'blocked by' feature.
[09:33] <mwhudson> now that it affects an import that someone clearly cares about is affected by it, we have a bit more motivation
[09:45] <sadleder> mwhudson: ;-) yes, i do care
[09:49] <persia> bigjools: About /+related-software : I see the batching, but I don't see the reduced filtering.  Is that in the pipeline somewhere?
[09:49] <bigjools> persia: can you file appropriate bugs for anything you need please
[09:51] <persia> bigjools: It's still bug #249772.  I thought it was to be closed with the last release, but on checking the bug status, I see I was mistaken.
[09:51] <persia> WIll it be next month?
[09:53] <wgrant> It seems to have regressed from that which was on dogfood.
[09:54] <bigjools> persia: ok I will un-dupe that bug, it's a different thing.  The dogfood change was just an experiment, it would take a while to do the fix "properly" but I'll schedule that change
[09:55] <persia> bigjools: Umm, bug #125987 is still present also.
[09:56] <wgrant> What changes have been made to RF?
[09:56] <bigjools> persia: that bug is a mess, I want to close it and open new ones
[09:57] <persia> bigjools: OK.  Please do so and subscribe me to them.
[09:57] <bigjools> wgrant: we've added new batched pages
[09:57] <persia> wgrant: Batching and per-class navigation is now in production.
[09:57] <wgrant> Ah.
[09:57] <bigjools> persia: 249772 is the only thing I am aware of that needs doing
[09:58] <wgrant> I was expecting links under each section.
[09:58] <bigjools> wgrant: did you see the dogfood mockup last weke?
[09:58] <bigjools> week
[09:58] <persia> bigjools: What about 125987?
[09:58] <wgrant> But I didn't complain before, so I can't complain.
[09:59] <bigjools> persia: 125987 is getting closed out today
[09:59] <persia> bigjools: On edge?  Oh, excellent.  Thanks.  For me, that just leaves 249772 then.
[09:59] <bigjools> persia: well it's released
[09:59] <persia> Which is mostly just the filtering we discussed on dogfood.
[09:59] <bigjools> right, I hope so :)
[10:00] <persia> bigjools: It's not released on LP for ~persia today.  I uploaded ubuntustudio-meta to intrepid last week, and it doesn't appear.
[10:01] <bigjools> hmm odd
[10:03] <persia> bigjools: Mind you, I'm looking at lpprod: if it's already on edge, I'm happy to wait another month.
[10:03] <bigjools> persia: it's not on edge - I don't know why that package is not showing
[10:06] <bigjools> persia: ah I see why it's not showing, someone else uploaded a newer version
[10:06] <persia> bigjools: OK.  Let's call 125987 still open then.  If you can push a patch without waiting for a release, I'll be excited, but I understand if you can't.
[10:07] <persia> Yes, but 125987 is specifically about still showing those.
[10:07] <bigjools> I can get something on edge
[10:07] <bigjools> persia: yeah, I see the problem now, it's basically still the "only showing published versions" thing
[10:07] <hyperair> are apt: urls linkified by launchpad?
[10:08] <persia> bigjools: Precisely.
[10:08] <bigjools> persia: ok, will try and fix that today
[10:08] <persia> bigjools: Thanks.  Also, bug #43020 looks solidly closed.  Thank you.
[10:08] <persia> (well, except that it's not a dup :) )
[10:09] <bigjools> yeah :)
[10:13] <bigjools> persia, wgrant: right, sorry for the confusion, I re-organised the bug dupes
[10:14] <persia> bigjools: Thank you.  I think that those are all the bugs about that section, and that we can safely say 125987 is about published versions and 249772 is about published SPRs.
[10:14] <persia> s/versions/SPPs/
[10:15] <persia> I've no idea if they have the same fix or slightly different fixes: I'll defer to your better knowledge of the code as to whether they are dupes.
[10:15] <bigjools> they are the same fix :)
[10:15] <persia> Ah, that makes it easy then :)
[10:16] <bigjools> in theory!
[10:16] <persia> Well, at least from a bug tracking perspective.  Code is entirely different :)
[10:18] <bigjools> persia: I was thinking that it might be useful for us to schedule some time at UDS to discuss your Soyuz requirements?
[10:19] <persia> bigjools: Sure.  I'd like to also invite dholbach, soren, geser, nixternal, mdz, keybuk, and sabdfl to that session, although I'm not sure if they would all attend.
[10:19] <wgrant> Hm, should I really be shown in both 'Subscribers' and 'From Duplicates'?
[10:19] <persia> I suspect wgrant and ScottK would also be interested, although they don't have the same reasons for needing the page to work.
[10:20] <wgrant> I suspect that nobody would be interested in having me there - all I do is complain and make a pest of myself.
[10:20] <persia> wgrant: I'd be interested, as I find your attention to the details of my requirements very helpful in expressing them properly :)
[10:20] <geser> wgrant: constructive complains?
[10:20] <bigjools> wgrant: as long as it's constructive complaining
[10:22] <geser> wgrant: and it's better if you start complaining during the design phase and not after it got deployed
[10:23] <wgrant> That is true.
[10:23] <wgrant> But we normally don't get to see things until it's too late.
[10:24] <persia> RIght, which is why you'd be good as part of the UDS session, to help define the set of requirements and use cases that drives the design changes.
[10:32] <wgrant> I find the fix for bug #240976 to be a bit odd.
[10:32] <wgrant> And incomplete.
[10:33] <wgrant> I now can't see on what date a SPR was initially published, and the 'Obsolete' timestamps still seem to be datepublished.
[10:36] <bigjools> wgrant: yes, that history section is borked, we're doing more fixes in 2.1.9 (bug 251478)
[10:37] <geser> does LP still cut off the reason, why a package got removed after a few words?
[10:37] <wgrant> I hope the rest of the page will be looked over while fixing that.
[10:37] <wgrant> geser: It did last month.
[10:37] <bigjools> wgrant: what do you mean?
[10:38] <wgrant> bigjools: There are other issues with showing the dates than just that affecting the date it was superseded.
[10:39] <wgrant> geser: It's particularly annoying when the comment is 'superseded by somelongpackagename', it's cut off to 'superseded by somelong...' and the package named 'somelong' exists but is something completely different.
[10:39] <bigjools> wgrant: can you comment on that bug then please and I'll see it gets looked at
[10:39] <wgrant> bigjools: Doing so, thanks.
[10:39] <bigjools> thank you
[10:40] <wgrant> Does obsolescence come under 'date superseded'?
[10:41] <bigjools> potentially
[10:41] <wgrant> I shall mention it explicitly, then.
[10:46] <wgrant> I'm very confused.
[10:46] <wgrant> What's happening with 1:0.61-1ubuntu1 on https://edge.launchpad.net/ubuntu/+source/sixpack?
[10:47] <wgrant> It seems to be showing the date removed. Not the date superseded like it should, nor the date published like your bug says it does.
[10:48] <bigjools> yeah I think the bug is just scratching the surface
[10:48] <bigjools> we reviewed the code for that page and it's rather naive so will be overhauled
[10:49] <wgrant> Heh.
[10:49] <wgrant> Good to hear.
[10:49] <wgrant> At least we can see everything on +publishinghistory now.
[10:49] <wgrant> Apart from the deletion comment.
[10:49] <bigjools> is there a bug for that?
[10:49] <wgrant> Which should very probably be on the +index as well.
[10:49] <wgrant> I was just looking.
[10:51] <bigjools> thanks
[10:53] <wgrant> Here's a great example of why that is bad:
[10:53] <wgrant> 22:17 < wgrant> `#  Deleted  on 2008-05-09  by Martin Pitt  (renamed to gadmin...) '
[10:53] <wgrant> 22:23 < geser> it got renamed to gadmin-proftpd (the comment got cut off :( )
[10:53] <wgrant> It truncated in the perfect place.
[11:29] <bigjools> wgrant: can you add an example URL to that bug please
[11:30] <wgrant> bigjools: Sure.
[11:31] <bigjools> thanks
[11:33] <wgrant> bigjools: Done.
[11:34] <bigjools> wgrant: perfecto, thanks
[11:38] <wgrant> I've just filed another bug which involves both the deletion comment and the publishing history with the misleading dates.
[11:42] <sadleder> now that there are buzilla-launchpad and trac-launchpad, is something like debbugs-launchpad already started?
[11:54] <bigjools> persia: when we show old packages in +related-software, you want to see old PPA packages too?
[11:55] <persia> bigjools: Personally, I don't care about PPA packages in the least bit.
[11:55] <bigjools> heh
[11:55] <bigjools> wgrant?
[11:55] <persia> On the other hand, in the interest of inclusiveness, it might make those who do look at their PPA uploads happy
[11:55] <bigjools> well it's consistent at least
[11:57] <wgrant> bigjools: I don't care.
[11:57] <wgrant> I'm not sure whether it's better to be consistent or more useful.
[11:57] <wgrant> As old PPA packages aren't particularly useful.
[11:57] <wgrant> I guess that if it didn't show old ones, +archive would show just the same information.
[11:58] <bigjools> right
[11:59] <bigjools> maybe add the publishing state as an extra column
[12:00] <wgrant> That would be good.
[12:20] <ignas> YAY! thank you for karma for bzr checkins!
[12:20] <ignas> ;)
[12:21] <sadleder> i registered and imported a project (pvfs) in lp and by mistake disowned it, so i cannot change the details now. can someone add me back?
[12:21]  * geser still waits on karma for uploads
[12:21] <persia> Can we have them for uploads too?
[12:24] <ignas> uploads?
[12:25] <frybye> hi - in ubuntu8.04 I did a "Analyse Hardware" and it has apparently sent the results to launchpad - I have opened an account there but don't know where to find this hardware analysis??
[12:26] <wgrant> ignas: Packages.
[12:26] <wgrant> sadleder: Ask a question at the answers URL in the topic.
[12:26] <wgrant> ... which isn't there any more. Huh.
[12:26] <wgrant> https://answers.launchpad.net/launchpad
[12:28] <ignas> wgrant: oh, so i would get credited for 140 packages in our PPA?
[12:29] <wgrant> ignas: I believe that sabdfl said that PPA uploads would count, albeit somewhat less than uploads to the primary archive.
[12:31] <frybye> try again - where at launchpad are these reports that get sent when using "system|system management|examine hardware?? <I am translating from the German lang. menus..>
[12:33] <wgrant> frybye: I found a URL to them a couple of weeks back, but it doesn't seem to be exposed in the UI
[12:33] <wgrant> (at the moment)
[12:35] <frybye> hmm.. so what is the point of this system in ubuntu if users cant access the results??
[12:35] <wgrant> I presume that they'll be available soon.
[12:36] <frybye> i c . hmmm... I was hoping to find a clue in there why my eeepc stopped being able to see the sdhc card.. hmmm
[12:41] <BjornT> frybye: you should be able to see it at https://launchpad.net/people/+me/+hwdb-submissions. at the moment we only store the raw data, though.
[12:41] <wgrant> bigjools: So we're allowed to mention those URLs?
[12:42] <wgrant> Er, BjornT ^^
[12:42] <frybye> ok thanks BjornT ..
[12:42] <persia> wgrant: They've been published in several open fora
[12:42] <wgrant> I wasn't sure that I'd seen them outside a bug or too.
[12:42] <wgrant> *two
[12:43] <BjornT> wgrant: did someone tell you otherwise? i don't see why not. and if there is a reason, it'd be better for us to protect them properly
[12:43] <wgrant> BjornT: Well, if something's not linked and hasn't been publicised, one might assume that it wasn't meant to be widely known.
[12:50] <persia> wgrant: It's also been discussed by some of the QA folk who are trying to figure out how to use it better., in IRC, mail, and the wiki.
[12:53] <\sh> I would like to see them anonymized..and not related to an lp account
[12:59] <persia> \sh: They used to be that way (and the old data remains available), but nobody did anything with it.
[13:53] <andrea-bs> Hello! I've just received a mail from the LP PQM with an error (PQMException) and the traceback, but I don't know why. I'm sure that this is a bug, but I don't know where to file it, any ideas?
[13:55] <ignas> This branch may be out of date, as Launchpad was not able to access it 19 minutes ago. (KeyboardInterrupt)
[13:55] <ignas> What?
[13:55] <wgrant> ignas: Hah, nice!
[13:55] <wgrant> I've not seen that before.
[14:04] <NCommander> bigjools, good morning
[14:06] <LarstiQ> moin
[14:12] <NCommander> morning LarstiQ
[14:15] <ignas> wgrant: cool, now it is refusing to import my branch
[14:15] <ignas> so I have a branch mirror stuck, because KeyboardInterrupt interrupted the process in some place
[14:15] <kiko-zzz> ignas, keyboardinterrupt means something timed out
[14:15] <ignas> well - time out is kind of Ok
[14:16] <ignas> but the (File exists: u'/srv/bazaar.launchpad.net/mirrors/00/00/59/11/.bzr': [Errno 17] File exists: ...)
[14:16] <ignas> after it
[14:16] <ignas> is something that kind of breaks it...
[14:33] <NCommander> cprov, good morning
[14:33] <cprov> NCommander: morning
[14:34] <NCommander> cprov, how goes it?
[14:34] <cprov> NCommander: slowly today.
[14:35] <NCommander> why slowly?
[14:38] <cprov> NCommander: I'm talking about my connection, nevermind me ;)
[15:05] <NCommander> cprov, bah, faulty internet FTL
[15:05] <NCommander> bigjools, ping
[15:09] <beuno> is it expected my karma got reduced ~40% after yesterday's rollout?
[15:10] <LaserJock> mine went up!
[15:11] <LaserJock> I can't imagine how yours  would go down, I think they added karma for bzr branch commits
[15:11] <persia> karma just tends to flail about after every rollout.  I've had everything betwen two hundred and two million, depending on the rollout.  Most of the time, the next rollout changes it more towards some average figure.
[15:11] <beuno> yeah, I was expected for mine to go through the roof  :)
[15:11] <radix> hmm, is stacked branch support in now?
[15:12] <beuno> persia, that has happened lately too?   I remember that from a year or two ago, but not recently
[15:12] <persia> beuno: Not sure.  I stopped paying attention to karma about a year ago.
[15:13]  * beuno was curious on how big the jump was going to be, so he looked before the rollout
[15:15] <beuno> radix, I don't think stacking is available yet, IIRC, we're still testing and working some quirks out
[15:21] <kiko-zzz> radix, there was a bug in the bzr client that needs fixing, unfortunately :-(
[15:21] <radix> d'oh
[15:30] <bigjools> NCommander: pong
[15:43] <Peng_> Yeah, my karma went way down too.
[15:43] <kiko> Peng_, you should stop killing kittens!!
[15:43] <Peng_> (well, vs. a week or two ago)
[15:43] <Peng_> kiko: It's only the mean ones who hiss at me!
[15:44] <kiko> heh
[16:24] <NCommander> bigjools, is there a way in Soyuz to do the equivalent of a binNMU?
[16:25] <NCommander> bigjools, we have roughly ~16 packages in the archive that got compiled with an old gnat, and now we're seeing issues when trying to link against a newer gnat
[16:27] <bigjools> NCommander: no, we don't support that
[16:27] <NCommander> Are there plans to add an equivelent feature?
[16:27] <bigjools> nothing firm, no
[16:27] <bigjools> we're mooting the idea of automating it but for now you need to re-upload and version bump
[18:40] <jelmer> This branch may be out of date, as Launchpad was not able to access it 16 minutes ago. (File exists: u'/srv/bazaar.launchpad.net/mirrors/00/00/0a/6c/.bzr': [Errno 17] File exists: ...) Launchpad will try again in 5 hours. If you have fixed the problem, please ask Launchpad to try again.
[18:54] <kiko> meeeeeeeeeeeting time?
[18:57] <stub> bed time
[18:58] <Rinchen> >> LP Weekly Meeting in #launchpad-meeting in 1 minute! Come join the fun!
[19:01] <oliver_g_> hello
[19:02] <oliver_g_> if I have a bazaar branch registered at code.launchpad.net, is there an easy way to use the PPA feature to get .debs from the code in that branch?
[19:02] <beuno> oliver_g_, not currently, no
[19:02] <oliver_g_> beuno: is there a hard way, then? :-)
[19:03] <LaserJock> build a source package and upload to PPA?
[19:03] <oliver_g_> ok then
[19:04] <LaserJock> I mean, that's what I do, but I'm a packager so that may bias it a bit
[19:07] <oliver_g_> LaserJock: I was looking for some trick to make it easier than that :-)
[19:07] <thumper> oliver_g_: we have future plans to make this easier
[19:08] <thumper> oliver_g_: but it is still some way off
[19:08] <oliver_g_> basically I have a patch for a minor bug in Hardy, and want to get a package that contains this patch and that I can install in another machine...
[19:08] <oliver_g_> well, here's another vote for that feature then :-)
[19:09] <LaserJock> oliver_g_: so you'd want to do: get current source package, apply patch, rebuild source package, upload to PPA
[19:09] <oliver_g_> LaserJock: yes...
[19:10] <LaserJock> it's somewhat difficult to imagine doing it all properly in an automated way
[19:10] <LaserJock> but I think one could certainly hack up a script to get the job done
[19:11] <oliver_g_> come to think of it, it might be cool if there were automatically-built packages for every patch in LP :-D
[19:11] <oliver_g_> maybe better ask Google for some spare CPU time, though...
[19:12] <LaserJock> well, currently we don't even know what "patch" means in all contexts so that seems like a difficult task
[19:12] <LaserJock> you could maybe troll about looking for attachments that look like a patch and try applying them
[19:13] <LaserJock> but knowing what version to apply to, etc. seems difficult
[19:13] <oliver_g_> something like that...
[19:14] <LaserJock> a great many of them would fail
[19:14] <oliver_g_> well just try to apply the maybe-patches to the latest versions for stable and development releases
[19:14] <LaserJock> you'd also have to distinguish debdiffs from plain patches
[19:15] <oliver_g_> and then add some icons to LP to the patch link: "download Hardy package; Intrepid failed to apply"
[19:15] <LaserJock> and for plain patches make up a changelog entry and bump the version correctly
[19:15] <oliver_g_> hm, true
[19:15] <LaserJock> I'd really hesitate to do that really, people are likely to really mess up their machines
[19:15] <oliver_g_> :-)
[19:22] <oliver_g_> (btw. is LP somewhat busy atm, or is that a problem with my connection?)
[19:22] <joaopinto> Hello,
[19:23] <joaopinto> where do I set the project maintainer and driver ?
[19:23] <joaopinto> I could find it 2 years ago, not anymore :P
[19:26] <kiko> joaopinto, what project?
[19:26] <joaopinto> https://launchpad.net/getdeb-web
[19:27] <mohbana_> hi
[19:28] <mohbana_> when are you going to support another vcs like mercurial?
[19:28] <kiko> joaopinto, wow. bac, mars: can you answer that?
[19:29] <bac> hi joaopinto
[19:29] <bac> click on 'change details'
[19:29] <mwhudson> mohbana_: what do you mean by support?
[19:29] <bac> then on the next page click on the tab at the top of the page marked 'people'
[19:29] <mwhudson> mohbana_: we'll probably have importing from mercurial into bazaar in a few months
[19:30] <joaopinto> bac, ok, found it, on the people tab
[19:30] <joaopinto> tks :)
[19:30] <mohbana_> mwhudson: why not support mercurial?
[19:30] <bac> joaopinto: great
[19:31] <mwhudson> mohbana_: partly because part of the value of launchpad is in uniformity, and partly because believe me first grade support for one vcs is quite enough work
[19:32] <mohbana_> that's quit absurd if you ask me, why not offer and on condition that support is not provided if you chose to use it
[19:34] <mwhudson> because offering a service badly is often worse than not offering it at all?
[19:35] <bdmurray> kiko: ping
[19:36] <kiko> bdmurray, on the phone, but..
[19:37] <bdmurray> kiko: I'm an impatient person and open a few lp tabs at the same time and ocassionally I get the "information message" on the wrong bug report
[19:37] <mohbana_> why does a bias exists towards bazaar
[19:39] <Ursinha> mohbana_, i think that is a matter of supporting well one vcs, instead of supporting miserably - or not supporting at all - many others
[19:39] <Ursinha> but i guess that's easy to figure out
[19:40] <kiko> bdmurray, indeed, indeed
[19:40] <bdmurray> kiko: okay, so its known then?
[19:40] <rockstar> mohbana_, have you used bzr?
[19:40] <kiko> bdmurray, yeeeeah. it's how our notifications our done -- mars or francis might know better
[19:41] <mohbana_> no, i want to use mercurial because it's a got an excellent eclipse plugin
[19:41] <rockstar> So does bzr
[19:42] <joaopinto> is it possible to move a bzr branch between projects ?
[19:42] <mohbana_> which is essentially a spinnoff of the hg eclipse plugin
[19:42] <mars> bdmurray, that's a known issue.  It has to do with the order that your updates reach the server, and which page the server will return those messages with.
[19:43] <bdmurray> mars: okay, thanks I won't report it then!
[19:43] <rockstar> joaopinto, yep.  What are you trying to do?
[19:43] <mohbana_> so it's definately a no for another vcs?  should i file a bug report?
[19:44] <Ursinha> mohbana_, i think this is definately not a bug
[19:44] <rockstar> mohbana_, we currently have no plans to support another vcs
[19:44] <mohbana_> feature request
[19:44] <joaopinto> rockstar, I have registered a bzr branch on the wrong project, but I already imported the source there, and now wanted to move it to the proper project
[19:44] <joaopinto> well, wrong in the sense that I am doing project reorganization :P
[19:44] <mars> bdmurray, thank you for letting us know about it
[19:45] <rockstar> joaopinto, Can you set it up on the other project?  Then ask a question in Launchpad-bazaar that's something to the effect of "Can you delete this branch?"
[19:45] <joaopinto> rockstar, that an option
[19:45] <rockstar> mohbana_, feature request != bug report
[19:45] <joaopinto> that's
[19:45] <Rinchen> updated next mtg date
[19:46] <rockstar> mohbana_, might I suggest you try out the bzr eclipse plugin?
[19:46] <mohbana_> bye, thanks for your time, and i was by no means trollign
[19:47] <mohbana_> and i don't think this is right, it defintely gives developers less freedom
[19:47] <rockstar> mohbana_, seriously, try out bzr.  You might like it.
[19:47] <thumper> joaopinto: you can just move the branch
[19:47] <thumper> joaopinto: to a different project
[19:48] <joaopinto> thekorn_, where do I do that ?
[19:48] <thumper> joaopinto: or is it an import branch?
[19:48] <mohbana_> can anyone explain why bzr performs so poorly on these tests; http://www.infoq.com/articles/dvcs-guide
[19:48] <joaopinto> I need to mv lp:~getdeb-web-developers/getdeb.net/main lp:~getdeb-web-developers/getdeb-web/main
[19:49] <thumper> mohbana_: probably better to ask that on #bzr
[19:51] <joaopinto> thumper, any instructions on how to move it ? Otherwise I will do the register new / delete old approach :)
[19:51] <kiko> mohbana_, try it out yourself -- a lot of benchmarks are skewed or irrelevant
[19:51] <thumper> joaopinto: click on the pencil image next to the title
[19:51] <thumper> joaopinto: and change the product in the +edit page
[19:52] <joaopinto> grrr. I am always missing that small icon
[19:52] <joaopinto> thumper, thanks
[20:01] <LaserJock> kiko: git still kicks bzr's butt on most speed tests. :-)
[20:02] <beuno> LaserJock, it does. And so does bzr for usability   :)
[20:02] <LaserJock> beuno: in some cases
[20:04] <kiko> LaserJock, luckily for us, bzr is fast enough
[20:04] <LaserJock> good for you ;-)
[20:04] <LaserJock> certainly hasn't been for me at times
[20:04] <LaserJock> though it's always improving
[20:04] <LaserJock> one day it might make a very fine DVCS indeed
[20:05] <kiko> err, today it does already
[20:05]  * beuno abuse^uses bzr every day, and it seems "fine" to me
[20:06] <beuno> speed, you can improve
[20:06] <LaserJock> well, I've waited hours and hours for branches before
[20:06] <LaserJock> not fun
[20:06] <beuno> now, changing things from the bottom up to fix usability problems, is quite harder
[20:07] <beuno> LaserJock, right, it's improved pretty fast. New formats and all
[20:07] <LaserJock> ugg, don't tell me about new formats ;-)
[20:08] <LaserJock> for the last year+ every time I've gone to use bzr I've ended up spending an evening in #bzr trying to figure out why either something doesn't work or it takes forever
[20:08] <LaserJock> and when you're just trying to get work done it's difficult to not get a bad impression
[20:09] <LaserJock> alternatively, I've never had to go to #git or #hg crying for help
[20:09] <LaserJock> :-)
[20:10] <ScottK> For me it's still a question of do I want to learn VCS +1 just to use in Ubuntu.
[20:11] <beuno> LaserJock, have you used pre-1.0 versions of git?
[20:11] <LaserJock> beuno: don't think so
[20:11] <beuno> LaserJock, :)
[20:12] <LaserJock> beuno: not exactly sure how that's relavent
[20:12] <LaserJock> are you saying I need to compare post-1.0 git to post-1.0 bzr?
[20:12] <beuno> I am
[20:13] <beuno> you (and most of us) went through bzr's growth, pre-1.0
[20:13] <LaserJock> well, I have been doing that since bzr 1.0 came out
[20:13] <LaserJock> right, but pre-1.0 was also pushed on us
[20:14] <beuno> the default format in 1.0 has solved the biggest performance problemas, although, I fully agree, performance is still lacking behind git/hg
[20:14] <beuno> and it's being worked on, so we should be up to speed soon
[20:14] <jcastro> doesn't stacked branches help speed in the case of hosted stuff like lp does?
[20:14] <LaserJock> it should
[20:15] <beuno> right, stacked branches are going to make a big difference
[20:15] <LaserJock> but I've gotten quite weary of all these bzr "features" to speed things up that just add complexity to everthing
[20:15] <beuno> especially for the bandwidth-impared
[20:15] <LaserJock> in that respect I think git is much more usable
[20:15] <beuno> LaserJock, what sort of features speed things up?
[20:16] <LaserJock> repos, stacked branches
[20:16] <LaserJock> it seems that repos are the answer to everything these days
[20:16] <LaserJock> which makes things a lot more complex
[20:17] <jcastro> code.l.n question: I have a friend who branched his project, and now he wants to make the branch the new trunk, if he changes the series do people have to migrate over manually or does some redirect magic happen?
[20:17] <beuno> they're not, performance is a problem, and it's being worked on. But we are at a stage where it's "good enough"
[20:17] <beuno> jcastro, as long as they use   lp:project
[20:17] <LaserJock> beuno: well, I didn't intend a DVCS fight, but "good enough" is quite subjective and my real world experience is that it's not there yet
[20:17] <beuno> it will be done magically
[20:18] <jcastro> ok, thanks beuno
[20:18] <beuno> LaserJock, right, I don't disagree with you that much.  Just the part where bzr isn't good enough, since there's hundreds of us around here using it on a daily basis for a big range of projects. Don't know how many actual users.
[20:19] <beuno> jcastro, is the new branch based off the old one, or created from scratch?
[20:19] <jcastro> based off of the old one
[20:19] <LaserJock> beuno: true, but a lot of people use it because of LP, not because it's superior
[20:19] <kiko> siretart, ping
[20:19] <beuno> jcastro, good, then it will transparent
[20:19] <LaserJock> and that's what kind of gets me about the convo about about LP only supporting bzr
[20:20] <jcastro> sweet, that's a nice feature
[20:20] <LaserJock> it very much looks like Canonical lock-in
[20:20] <ScottK> beuno: LaserJock is a distro developer.  We tend to have a different workflow and stress VCS systems in different ways.
[20:21] <beuno> LaserJock, as mwhudson said, it's hard enough to support a DCVS that you have access to the code devs
[20:21] <ScottK> The fact that it works for you for a different task is really irrelevant to our needs.
[20:21] <LaserJock> beuno: right right, I know the reasoning
[20:21] <beuno> ScottK, sure. And, as always, you're welcome to file bugs to help us cover your needs better
[20:21] <ScottK> beuno: At this point I just don't use it.
[20:22] <LaserJock> it'd be nice if we were given a better choice for hosting packaging code
[20:22] <beuno> ScottK, then you don't have a problem  :)
[20:22] <ScottK> My comment is just advice not to be too self-congratulatory.
[20:22] <nycerine> the package descriptions for ubuntu, are they gathered from the ddtp or entirely seperate from it?
[20:22] <ScottK> beuno: I don't currently, but there are people who want to take that choice away from me.
[20:22] <LaserJock> beuno: it is a problem, because he essentially gets locked out of using a DVCS for Ubuntu unless he uses bzr
[20:23] <beuno> nycerine, AFAIK, they're imported from ddtp
[20:23] <nycerine> are you certain?
[20:23] <beuno> LaserJock, as with svn for gnome, etc
[20:23] <beuno> nycerine, no. danilos?
[20:24] <LaserJock> beuno: I don't think that's quite true
[20:24] <nycerine> I am considering starting a nb_no translation for DDTP
[20:24] <ScottK> beuno: svn is at least used elsewhere.
[20:24] <nycerine> though, I prefer rosetta
[20:24] <LaserJock> there are git and bzr mirrors of Gnome
[20:24] <ScottK> And yes, I know bzr is used elsewhere, just not by anything I'm involved in.
[20:24] <kiko> hey, you guys are scrolling the hell out of my IRC backlog
[20:24] <LaserJock> and as ScottK said, svn is quite ubiqutous
[20:24] <LaserJock> kiko: sorry :/
[20:25] <kiko> LaserJock, where is siretart? I really need his feedback
[20:25] <LaserJock> probably gone for the evening, I'm not sure
[20:25] <beuno> kiko, anyone from translations around to answer nycerine?
[20:25] <nycerine> so nobody has a absolutely certain answer? mkey then. I hope someone knows (someone must), translating both would be a waste of time and energy
[20:25] <kiko> LaserJock, he said he'd get back to me with scores, but man.. it's one day to my deadline
[20:25] <kiko> nycerine, what's the problem?
[20:26] <LaserJock> kiko: ah, he's better with email I think, you might send him a reminder note
[20:26] <nycerine> kiko, are the ddtp imported into the package descriptions for ubuntu?
[20:26] <kiko> LaserJock, I have :)
[20:26] <kiko> thanks though
[20:26] <LaserJock> k
[20:26] <nycerine> as in, any work in DDTP will be imported into rosetta?
[20:26] <kiko> nycerine, hmmmm! do you mean, does ubuntu support ddtp, or does rosetta offer ddtp?
[20:26] <nycerine> if so, one wouldn't have to do double work.
[20:26] <nycerine> uuh.
[20:27] <nycerine> well, I know there's no DDTP on launchpad.
[20:27] <nycerine> as in rosetta interface
[20:27]  * ScottK wonders what ddtp is?
[20:27] <nycerine> I'm asking if the data from DDTP is imported into the data of the package desc for ubuntu?
[20:27] <kiko> ScottK, it's the debian format for translating descriptions of packages
[20:27] <ScottK> Ah.
[20:27] <ScottK> Thanks kiko.
[20:27] <LaserJock> Debian Desctiption Translation Project?
[20:27] <nycerine> yup.
[20:27] <kiko> sure thing!
[20:28] <kiko> nycerine, https://translations.launchpad.net/ddtp-ubuntu/+translations
[20:28] <nycerine> I know about that, I'm referring to it as the package desc for ubuntu.
[20:28] <nycerine> However, is it imported from ddtp?
[20:28] <kiko> nycerine, can you ask a question in answers.launchpad.net? I would want to get somebody to answer but people are mostly asleep by now
[20:28] <nycerine> and also, afaik, that data isn't shared with ddtp, so it's not going anywere
[20:29] <nycerine> sure.
[20:29] <nycerine> I'll just ask on ddtp-ubuntu, right?
[20:29] <kiko> nycerine, either that or ubuntu or launchpad -- it's really a good question you have, and I don't know the answer to it but am curious
[20:30] <nycerine> :)
[20:30] <nycerine> I'm thinking that imo rosetta is superior to the DDTP interface.
[20:30] <kiko> nycerine, I don't know whether the DDTP makes it easy to share translations back to the core project, but I assume it's just pofiles, and in that sense we do allow exports, and people can merge things in
[20:30] <nycerine> hmm. certainly.
[20:31] <nycerine> pref. it'd be better if the translations would have the biggest impact possible.
[20:31] <nycerine> that's sort of killing me when it comes to translations, there's no real "home"
[20:31] <kiko> nycerine, that's true. I do think we do use the translations, but I don't use ubuntu in pt_br myself
[20:31] <nycerine> hmm.
[20:31] <kiko> Ursinha, do you use ubuntu in portuguese?
[20:32] <Ursinha> kiko, nope
[20:32] <kiko> hmph
[20:32] <kiko> okay, afk for a quick bit
[20:32] <nycerine> (I don't use the norwegian version either, except for what comes from gnome and OOo)
[20:45] <nycerine> well, the question is out there.
[20:46] <nycerine> perhaps I didn't ask at the best location, but it is the ddtp-ubuntu project it is regarding.
[20:46] <nycerine> or rosetta?
[20:46] <beuno> nycerine, it is the right place, just wrong timezone  :)   they'll get to your question soon
[20:47] <nycerine> ah. :) ddtp-ubuntu seems sort of silent, but oh well.
[20:47] <nycerine> I suppose I'm sort of unpatient (not that I'm expecting an answer now :) )
[22:40] <Ampelbein> Hmm. The error message you get when submitting in invalid request per mail to the bugtracker refers to a non-existant page https://wiki.canonical.launchpad.com/MaloneEmailInterfaceUserDoc. Perhaps this should be corrected?
[22:53] <mthaddon> Odd_Bloke, have a sec to discuss a particular PQM issue you're working on that I'm interested in?
[22:54] <matsubara> Ampelbein, that's bug 128729
[22:56] <Ampelbein> matsubara: ok, cool.
[23:08] <komputes> Does anyone here have a Bug reported on the day Hardy was released (April 24th, 2008), I need that bug # as a delimiter for my research.
[23:18] <kiko> komputes, hmmmm, not me, but I can tell you a bunch of ids filed on that day
[23:19] <komputes> kiko: actually I may have found a solution, I google searched " bug launchpad "on 2008-04-24  (Activity log)" " and I found a few, I think starting at 221300 is a safe bet
[23:20] <komputes> kiko: by ids do you mean bug numbers? if so, please give me a few examples
[23:21] <kiko> yes
[23:22] <komputes> kiko: sure, i'll take whatever you got. pm me if you'd like
[23:25] <kiko> komputes, 221239 and up.
[23:27] <komputes> kiko: thank you for your help!
[23:30] <kiko> komputes, you're welcome. 221328 was filed one day before, for the record
[23:30] <kiko> well, just before midnight of the 23rd. ;)
[23:32] <komputes> kiko: therefore it does not exist to me, hehe. thanks for your _precise_ help
[23:34] <kiko> komputes, no problemo, always here to help