=== ScottK is now known as ScottK2 === ScottK2 is now known as ScottK [03:24] anybody figured out the problem with mailing list mails not delivering to people? [04:14] mtaylor, hi, problem with mailing lists? [04:15] mtaylor, can you point me to your mailing list in question? [04:15] mtaylor, are you still at OSCON by chance? [04:41] mtaylor, I'll email our engineers about it === asac_ is now known as asac === Ursinha is now known as Ursinha-afk [05:31] yawn === RAOF_ is now known as RAOF === gnomefre1k is now known as gnomefreak === gnomefre1k is now known as gnomefreak [11:34] hello. i'm a bit confused by rosetta. back in the day, i uploaded a .pot file for mythbuntu-control-centre. now i see that there are multiple series (gutsy,hardy etc) with different stages of completion - how does that happen? the .pot file satyed the same all the time === gnomefre1k is now known as gnomefreak [11:44] also, if launchpad already has some .po files, do i need to upload these again when uploading a new .pot? [11:47] hi === gnomefre1k is now known as gnomefreak === gnomefre1k is now known as gnomefreak === gnomefre1k is now known as gnomefreak === Ursinha-afk is now known as Ursinha [14:56] is it a known bug that an upload to hardy-backports closing a bug with LP: #nnnnnn in the changelog actually closes the "nominate for hardy release" task, whereas it should only touch the hardy-backports task? [14:56] an example of this behaviour is bug #248081 [14:56] Launchpad bug 248081 in filezilla "Please update filezilla to 3.0.11.1" [Medium,Fix released] https://launchpad.net/bugs/248081 [14:57] !weekend [14:57] It's a weekend. Often on weekends, the paid developers, and a lot of the community, may not be around to answer your question. Please be patient, wait longer than you normally would, or try again during the working week. [15:00] Hobbsee: was that directed to me? [15:00] yes [15:03] well, I don't think I showed any sign of impatience, did I? or, is it now forbidden to ask questions during week-ends? :) [15:04] no, it was more just to point out that it *is* a weekend, and i've not seen any of the launchpad developers here, or talk in many hours :) [15:04] looks like the last comment was 11 hours ago. [15:10] ok, I thought maybe a launchpad user already encountered this problem and may be able to point me to a bug report. anyway, I'll re-ask on monday if I get no answer now [17:24] i wanted to add a bug watch for xmms2 according to https://wiki.ubuntu.com/Bugs/Watches . there were no project for xmms2 and so i created one. now i am hanging on the "Register project affected by this bug" site. I have to enter a bug url. i have entered http://bugs.xmms2.xmms.se/ but launchpad does does not recognize the bug tracker at this URL. what am i doing wrong? [17:37] bdrung: You may want to file the bug against the ubuntu project, using the xmms2 package. [17:39] ToyKeeper: i wanted to add a upstream bug watch to an bugreport (which is already filed against the ubuntu xmms2 package). [17:39] Ah, okay. [17:39] So you've got the preliminary steps done already. [17:41] yes. i opened the bugreport, clicked on "also affected project", then on choose (to search for an project). i did not found xmms2, so i clicked on "register it" [17:45] There is a project called "xmms" though. [17:46] I haven't used xmms in many years, so I don't know if xmms2 is the same thing. [18:02] ToyKeeper: i have created a new project for xmms2. xmms2 is written from the scratch and has an client/server approach. they are completely different. [18:03] Ah, yeah. I was just reading about it. :0 [18:03] :) even [18:44] where did the place to change the status of a branch go on edge? [18:45] Rinchen: it's the ~drizzle-discuss list... [18:45] mtaylor, next to the title you have an edit button [18:45] Rinchen: we've got several people who aren't receiving emails from the list, but are receiving them from launchpad in general [18:45] beuno: ah. the exclamation point [18:46] beuno: fwiw, that is not very self-evident to me... [18:46] mtaylor, I completely agree :) [18:46] yay! [18:46] * ScottK suggests filing bugs. [18:46] * beuno too [18:53] * mtaylor just likes to bitch on IRC [18:53] lol [18:54] * beuno files the bug [18:58] mtaylor, bug #252172 [18:58] Launchpad bug 252172 in launchpad-bazaar "Changing a branch's status/privacy isn't obvious" [Undecided,New] https://launchpad.net/bugs/252172 [19:26] Hi, on a project page like https://code.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk [19:26] warren, yeah? [19:26] I notice that it no longer shows alternate URL's like http for bzr pulling. [19:27] It seems that bzr pulling from the lp URL fails to see new changes until a bit later. [19:27] which is problematic when we have a dozen people working on the same code [19:27] warren, they are equivalent, and you can still use http or bzr+ssh (if you have write access) [19:27] I also liked pulling with http and pushing with some other menas. [19:27] lp:... is just a shortcut for the http [19:27] well, actually, that's not true [19:27] oh? [19:28] it's a smart shortcut that uses http:// or bzr+ssh:// depending [19:28] on whether you can actually log in [19:28] hm [19:28] I don't know what we're seeing then [19:28] I guess my point is more that lp: doesn't use any different protocol than you get when explicitly specifying the URL [19:29] warren, I'm a bit surprised as well. let me check one thing. [19:31] We definitely saw some kind of delay thing yesterday [19:31] I was the only one that was able to pull latest pushes instantly [19:31] I was using http:// urls while everyone else was using lp: [19:31] other than the codescanner being backlogged? [19:31] warren: heuh [19:31] that's exactly the other way around than I'd expect. [19:32] (lp: going to bzr+ssh if you have the access) [19:32] LarstiQ, if the codescanner hasn't been able to scan the branch yet, the only thing that should happen is that revisions aren't listed in launchpad, no? [19:32] Oh, I think I understand [19:32] kiko: hmm, I might have named the wrong part. Isn't there a sftp->http mirroring step? [19:32] hello here [19:32] LarstiQ, AFAIK they are served from the same physical location [19:32] IMBW, but I think they are at least [19:33] warren, I'll check for you and on monday ping you to be sure so we know the actual answer [19:33] about to check in so I'll need to log out [19:33] * kiko waves [19:33] kiko: ok [19:33] thanks [19:33] kiko: hmkay, I might have old architecture in my head [19:40] warren, actually, the http branches get mirrored, so they have a sall delay from the ssh ones [19:40] mwhudson knows more about it, but it's sunday where he lives, so he's probably enjoying his day off :) [19:55] mtaylor, we had an engineer that found something. It'll be Monday to get it resolved. Only affects certain lists. [19:56] Rinchen: awesome! I'll let folks now [19:56] know === doko_ is now known as doko [21:02] When is LP going to be able to mirror from bzr+http? [21:11] Do you have to be in beta-testers to use openid? [21:15] D'oh. [21:16] ... found some launchpad issues. I think most of them were caused by the new theme. [21:17] I can no longer edit branch details or delete branches. [21:29] I thought you guys would like to know that REVU is now using Launchpad for its login system (via OpenID) [21:30] YOu may now celebrate [21:38] cool thanks NCommander [21:39] It was my pleasure [21:39] Although we do have a bug that you need to click a continue if javascript is disabled in a browser [21:40] NCommander, re openid, yes...we're still piloting it. We need to make another change to it before it's ready [21:41] Rinchen, well, we should hopefully help you stomp out quite a few issues [21:41] http://revu.tauware.de [21:42] we were all set to deploy it but got a lot of beta tester feedback that said the 1.1 urls are not very usable so we have another proposed solution. [21:42] there's a bug about it [21:42] bbib. stranded at portland airport...need to relocate.