[00:19] vcs-import keeps failing on sourceforge svn import [00:19] https://code.edge.launchpad.net/~vcs-imports/zquake/trunk [00:19] known bug? [00:21] I wondered if it might be related to this [00:21] https://bugs.edge.launchpad.net/launchpad-cscvs/+bug/120992 [00:21] Ubuntu bug 120992 in launchpad-cscvs "use persistent svn_ra sessions and reconnect on failure" [High,In progress] [02:03] If not already done, can a LP admin please disable this user's account, they spammed bugs (similar to what i saw a few days ago) - rutadeevacuacion [02:06] Rocket2DMn: I don't think there are any LP admins around at the moment. You should ask a question on Launchpad: https://answers.launchpad.net/launchpad/+addquestion [02:07] uhhhh [02:07] I've closed the spam bugs, we had something like this a few days ago occur, by the time i showed up to close the bugs, the user was already banned [02:09] ok. [02:10] well, my point is that if you want to be certain that an LP admin sees your request, the best thing to do is ask a question at that URL. [02:11] * jml goes away for lunch. [02:11] thanks jml , ill see if i get a response in here for now [02:11] ok. [02:15] I am getting an error when I try to change my name on launchpad because I have used my identifier... it says I can continue by hitting save again, but that just gives me the error again [02:19] jml: Argh, that account has been disabled by spm at least twice already. [02:20] And his other account which has been disabled a couple of times is back too. [02:20] Can somebody please fix LP to make account death less temporary!? [02:20] I am getting an error when I try to change my name on launchpad because I have used my identifier... it says I can continue by hitting save again, but that just gives me the error again [02:20] wgrant, are you talking to me? [02:21] Rocket2DMn: I'm referring to the account you mentioned, but was talking to jml. [02:21] ah ok, just making sure it was the same [02:21] has the account been re-banned? [02:21] Not AFAICT. [02:21] It is a weekend. [02:22] /headdesk [02:22] I fail to see how LP can be so useless at killing accounts. [02:22] does LP suport openid? or is that just the wiki? [02:22] LP is a provider, but not a consumer. [02:23] ok [02:26] wgrant any idea how to kill a 'link' from LP to a consumer of openID [02:26] it is stopping me from changing my LP name [02:26] which Rocket2DMn has suggested I do [02:26] PrivateVoid: Ah, you meant that kind of identifier. I'm not sure if you can. [02:27] PrivateVoid: Ask a question at http://answers.launchpad.net/launchpad/+addquestion [02:27] so there is no way to change the LP name? [02:27] You could do whatever you wanted with it until 3 days ago, I suspect. [02:27] Let me try on staging. [02:28] PrivateVoid, i didnt suggest it, someone else did [02:28] nhandler then... sorry Rocket2DMn [02:29] love you too PV [02:30] PrivateVoid: It works for me on staging if I click save after getting the warning. [02:30] how do I use staging? [02:31] Ah. [02:31] I just found the problem. [02:31] is that edge? [02:31] staging and edge are separate. [02:31] staging runs on a copy of the DB that is erased nightly. [02:31] So it's no good. [02:31] ok [02:31] Have you tried changing it on edge? [02:32] Oh. [02:32] Damn. [02:32] That revision has a DB patch, so it might well not even be on edge. [02:32] There's an RC fix for this bug, which should have been rolled out yesterday, but that rollout has been delayed by a couple of days... [02:32] I will wait then... [02:32] not an issue [02:32] or perhaps I will go Milton [02:33] and burn the building down [02:33] * PrivateVoid laughs [04:44] Hi, please take a look at https://bugs.launchpad.net/~rutadeevacuacion [04:44] they reported a bunch of nonsense bugs [04:45] and they just made bug 137526 private, with apparently no reason [04:45] Bug 137526 on http://launchpad.net/bugs/137526 is private [04:45] my guess is that they are testing the API, but not in a very sensible way [04:52] james_w, i reversed the private setting [04:52] Rocket2DMn: I wasn't going to do that, as I wasn't entirely sure it was wrong [04:52] that person is a spammer [04:53] apparently did stuff to some other bugs, too, ill go reverse the changes [04:53] Rocket2DMn, thanks. [04:54] apparently they are having problems keeping users banned, its not sticking [04:55] gotta go close more of his bugs, too [04:55] what a stupid thing to have to do [05:02] OK the user rutadeevacuacion@msn.com really needs to be banned, the spam bugs are coming full speed [05:04] * Hobbsee wonders if that srot of thing happens on weekends. [05:04] especially with their apparent lack of success during the week [05:05] ok, well im finished closing those stupid bugs, im going to bed [05:05] if somebody wants to check up on him, close the garbage bugs (the first 2 listsings are legit, i reversed his changes) [05:05] https://bugs.launchpad.net/~rutadeevacuacion [05:05] gotta be in bugcontrol since tho, since the bugs are private [05:06] bleh english, thats why i need to go to bed, have fun [05:10] james_w: spm has already disabled both of his accounts twice. [05:10] And it's a weekend, so it's not likely to happen again soon. [05:10] sounds like they need a more effective bug spray [05:10] Unless spm_ is bad and is sitting at his computer. [05:12] It would probably be a good idea to go through the notification logs and revert every action either of his accounts have performed over the last week... there's quite a few. [05:13] I presume they can do that themselves? [05:13] 'they' being LOSAs? I'd hope so. [05:14] yes, sorry [05:15] Although given that they can't stop dead accounts from becoming undead, I have my doubts. [05:15] I mean, what the fsck is with that? How does an account that has been doubly killed come back again!? [05:16] register a new account with the same email? [05:16] No. [05:16] The account was still there. [05:16] With the email and username. [05:16] Just deactivated. [05:17] Somehow they manage to reactivate it. [05:17] * Hobbsee expects there's a launchpad bug with reactivations. [05:18] staging doesn't do mail, does it? [05:19] spm_, herb, ^ [05:19] Hobbsee: No. [05:19] kiko_, ^ === beuno_ is now known as beuno [05:19] off to bed now! [05:19] * wgrant suspects somebody will need to use the magic of screen and a while loop. [05:19] Night beuno. [05:23] oh, i think i know what's happened. [05:24] * Hobbsee wonders if the LOSA deactivations are the same as normal deactivations [05:26] or end up behaving the same way. [05:30] Hobbsee: You mean you think somebody can just claim them? [05:30] wgrant: no, you have to get an email back to the same account to reactivate them. [05:30] but that's simple, if you own the account in question. [05:31] I'm unfortunately not too well versed in having my account banned. [05:31] launchpad supports reactivating a normal account, if you've closed it. I expect that it doesn't show up differently to a LOSA closing someone's account. [05:31] wgrant: i created a test account, then deactivated it. Then reactivated it. [05:32] if you try logging in with the credentials, it tells you to hit "forgot your password" because it's a deactivated account, to reactivate it. [05:32] Maybe they could win by removing or altering the email address on the account. But then I guess that just lets them reregister. [05:32] it sends you an email, you click the link, it says "welcome back" [05:32] etc [05:33] * Hobbsee wonders if 'banned' just means deactivated - or if it's supposed to be something else, but isn't. [05:33] I don't quite know. [05:33] i didn't think we've actually been able to deactivate our own accounts for that long [05:34] Bug #gbcw has been closed for 15 months now. [05:35] * Hobbsee notes that a buildd building a private build is not deactivated, incidently ,too. [05:35] Hobbsee: Give it a couple of days... [05:35] Oh, you're in your test account? [05:35] Aha. [05:35] yes, I thought that a little odd. [05:36] yes [05:36] i wasn't willing to try all the above with my normal account. sheesh ;) [05:36] i don't trust LP *quite* that much. [05:36] Heh. === doko_ is now known as doko [08:44] hi there, any launchpad admins online? [11:06] * Hobbsee blinks. [11:06] * Hobbsee found a bug.... [11:06] Hobbsee: a bug? In software? Never! [11:06] spiv: heh [11:07] spiv: points for making private builds private. Negative points for then making the entire history of whichever buildd that is building the private build also private. [11:09] what's weirder is that this was working earlier, even while it was building something private. [11:09] https://edge.launchpad.net/+builds/artigas/+history == now 403'd. [11:10] Hobbsee: not for me, but I'm probably part of some special team. [11:10] spiv: likely, yes [11:10] spiv: you probably have a goose or something that lets you see it. === Mario_ is now known as pygi [11:33] Hobbsee: No, it's because you're a buildd-admin. It's the same reason you can see the private builders building things. [11:33] You can see that the builds exist, but you can't see them, so you die. [11:34] us unprivileged people are actually more privileged here. [11:35] ah [12:52] Hello, I've uploaded a modified ubuntu package to my ppa, it fixes a big, how should I report that on the bug report? [12:52] A simple comment? === caesar_ is now known as devil [12:58] I guess I'll with a comment [12:59] Should I change the status of the bug report to fix commited? [13:00] "#Fix Committed is not to be used when a patch is attached to a bug " I guess not, then === bascule is now known as bascule2 === bascule2 is now known as bascule === cjwatson_ is now known as cjwatson [14:38] PPA question: If I want to provide three packages in different sections (devel, libs and libdevel), what section do I use for the source? [14:41] hm.. more like a motu question I guess [18:03] beuno: (moving the discussion here): Does that super-tracker do anything else in terms of grouping bug reports, or anything? (Not that it needs to, just wondering). I recall reading about the ability for one project to submit a bug report and share it with another, in the case of plugin software this is very helpful. I'm just curious if more things like that exist, and in any way aided by the super-project idea. [18:08] leefmc, you can link a bug to 2 different projects [18:08] and track it's status seperatly [18:08] without the need of a super-project at all [18:09] beuno: yea [18:09] beuno: But are there any more tricks like that for super-project .. projects? [18:10] well, I think super-projects are just for grouping currently [18:10] I don't think they inherit many things to their groupees [18:10] beuno: And on the same note, is there a better way to browse the super-project related projects? Ie, that list of bzr-plugins is rather long and unorganized, is there a page dedicated that lets you see activity, etc? [18:10] beuno: K [18:11] leefmc, not currently, BUT, we're actively working on improving the UI of Launchpad, so something like that will happen soon [18:11] feel encouraged to file bugs with the features that Launchpad lacks [18:11] that'll help it get implemented ;) [18:12] :) [18:12] Yea i'll be sure to do that, but for now the only thing that matters is what is there _now_, if you know what i mean hehe. [18:12] absolutely [18:13] Im happy with most of Launchpad, i just hope we use it hehe [18:13] My main problem in the past was the horribly slow servers heh [18:14] currently its nice and snappy, so i hope it stays that way. [18:14] beuno: Any idea why the servers were so slow in the past? [18:14] leefmc, it's a big project and growing fast, so "growing pains" [18:15] it should get faster as we go [18:15] beuno: Any idea what you would say is the next coming feature? Are you guys working on UI improvements first, or .. ? [18:16] leefmc, we're over 30 developers working on Launchpad, so a lot of features are coming down the pipe [18:16] there is a major focus on UI and speed improvements [18:16] which I think will be the biggest things [18:17] beuno: K, thanks for all the questions :) [18:17] well.. answers, heh [18:18] leefmc, happy to help [18:22] beuno: Hopefully i'll get word this weekend which project host were going with.. waiting is driving me nuts. (Hes been on vacation for the past week :o) [18:23] anyway, thanks again. Gatta jet for a bit, bbl [19:02] which Ubuntu releases are supported in PPAs? does building for dapper with in a PPA? [20:00] geser, all supported releases [20:00] dapper, feisty, gutsy, hardy, intrepid, and, soon, jaunty [20:01] jaunty is enabled isn't it? [20:01] at least I thought I was uploading a jaunty in my PPA earlier [20:02] james_w, maybe recently? [20:04] ah, it looks like we do [20:04] * beuno learns something new today === kiko is now known as kiko-afk [22:29] Can someone look at why the armel builders are ignoring P-a-s. i.e. https://edge.launchpad.net/ubuntu/jaunty/+source/libx86/1.1+ds1-2 [23:33] yeah, jaunty is there for ppa [23:37] ls [23:38] I'm having problems getting using bazaar