[00:11] hi, I got this error in PPA: [00:11] http://launchpadlibrarian.net/27666579/upload_1066749_log.txt [00:12] does anyone know where the problem is? It says "Rejection during accept." and then that it couldn't find the source package in jaunty --- even though it successfully built on the buildbot. [00:17] ondrej, an upload failure often means that the build is generating a broken upload [00:17] kiko -- I see [00:21] ondrej: Which is the build that gave that log? [00:21] hi wgrant, do you want the number? [00:22] ondrej: A link is better. [00:23] wgrant: https://edge.launchpad.net/~ondrej-certik/+archive/ppa/+build/1066749 [00:26] ondrej: Had it finished a few seconds earlier, it would have probably worked. The error message means exactly what it says - the source was superseded at 00:01:10 by pytables 2.1.1-1ubuntu1ppa1, so when the build finished at 00:01:12 the source no longer existed. [00:26] So, you can ignore it. [00:26] ah [00:26] so I just uploaded the new pytables [00:26] and that made the old one stop working? [00:27] Because the build was in progress when it happened, yes. [00:27] I see, thanks [00:27] btw, pytables are unusable in ubuntu [00:27] https://bugs.edge.launchpad.net/ubuntu/+source/pytables/+bug/348983 [00:27] Launchpad bug 348983 in pytables "[jaunty] PyTables does not work for Python 2.6" [Unknown,Fix released] [00:27] That bug is closed. [00:27] oh. [00:27] No, that's the Debian task that's closed. [00:27] I don't think so. [00:28] anyways, the packages in my PPA works fine [00:28] what are the next steps? [00:28] upstream bug task, not debian one in that case [00:28] ajmitch, upstream fixed that in December I think... [00:29] that's quite awhile ago [00:29] all that is needed now is to upload the new version to debian/ubuntu [00:29] You won't be able to get 2.1.1 into Jaunty. [00:29] The minimal patch which fixes the issue needs to be isolated. [00:30] That ticket seems to give the relevant patch. [00:30] I see [00:30] I guess the fix is easy [00:30] but I'll just use my PPA version [00:31] See https://wiki.ubuntu.com/StableReleaseUpdates if you want to get the fix into Jaunty. [00:32] right [00:33] first I need to finish my NM process in Debian, then I can play with such things.. :) === asac_ is now known as asac === flacoste is now known as flacoste_afk === flacoste_afk is now known as flacoste [02:05] is there anyway to delete the noise in https://bugs.edge.launchpad.net/launchpad/+bug/383784? [02:05] Launchpad bug 383784 in launchpad "occasional corruption of signed messages" [Undecided,New] [02:10] Is there anything to do with bug comments, which instead of pertaining to the bug, are support requests on a completely unrelated issue? (Ex: asking about recovering a password under a bug about a broken link in the Kubuntu Wiki theme) [02:12] Would that constitute the ``spam'' described in Nickserv's welcome message? I don't mind answering the guy, just that I'd rather not do it in a bug report and I'd rather not end up with support requests in bug comments.... [02:14] ryanakca: no, that's not spam. my 2c would be to ask them to take it elsewhere and then let you know to respond. ie they will get the support request, but pls to follow preferred location for same. ???? [02:15] ie don't provide the support in the bug report. [02:39] spm: Lovely, thanks [02:39] spm: Any estimate about when the rest of the UBT teams will be renamed? No rush, I just would like to be able to provide the team with a status update [02:40] nhandler: Ooo. ta for the reminder! I'll try and get those done this afternoon. Got caught up with severe weirdness last week. [02:41] spm: No problem. Thanks again [02:41] On a different note, is it possible to subscribe to bugmail for all packages maintained by a specific team (the team is a Debian team that is not "really" on LP) [02:42] nhandler: hmmm. not sure. I know it can be done on a project basis - we get requests to "halp!!! stop emailing bombing me!!!" on a regular basis. But teams... dunno... [02:43] nhandler: you could have the "team"'s messages delivered to a mailing list [02:43] SamB: I can't. The team is https://edge.launchpad.net/~pkg-perl-maintainers [02:43] nhandler: oh, well, if you were an admin you could ... [02:43] * spm o/ [02:43] you could ask one of the admins to set something up [02:44] oh this is an imported team. urg. this has caused pain in the past. [02:45] oh, do those have no admins ? [02:45] perhaps not technically; they're unclaimed. so not setup. for lack of more accuracte phrasing. [02:48] so, they have no admins [02:48] and there is nobody to bug about them except you? [02:49] ha! not just me, but yes :-) [02:50] nhandler: Maintainers aren't special in Launchpad - you'd have to search for and subscribe to each package manually. [02:55] wgrant: True. the only thing a team can do is easily allow multiple people to subscribe to a set of packages' bugmail. However, someone will still need to go through and manually subscribe to all of the packages manually [04:45] how do I change the maintainer for a project? [04:45] oh, there's a people subtab [04:45] meh. [06:03] the troll is going through all my old bugs and slaughtering the descriptions with nonsense [06:03] This must stop. [06:04] ethana2: who? [06:05] ethana2: The troll? That sounds really annoying. [06:05] ethana2: can you link to a bug that was defaced? [06:05] spm: ping [06:05] RAOF: it is TERRIBLY annoying [06:05] lifeless: will do [06:05] here's one.. [06:05] * RAOF wonders whether this is related to the current wonderful ubuntu-devel-discuss monofest. [06:05] my launchpad question.. [06:05] https://answers.launchpad.net/dynazine/+question/73280 [06:06] which one are you [06:06] I fixed another one [06:06] I'm the one with a bug reporting history like two years long [06:06] help me out here [06:06] turns out there's nothing against having the same display name because they don't need to be unique. [06:06] ~ethana2 [06:06] the troll is ~ethan-anderson or something [06:07] which is my name, actually [06:07] but not my account [06:07] He has been up to this all week and its driving me nuts [06:08] ethana-anderson doesn't seem to have commented on any bugs [06:09] do you have a bug link handy they have messed up? [06:09] spm: ping! [06:09] wait [06:09] why on earth can he edit my bug descriptions? [06:09] well I guess that makes sense.. [06:09] but why my launchpad question? [06:09] please tell me you don't have 'security' based on display names [06:10] no, display names aren't used for security at all [06:10] ok good [06:10] why is he able to alter my launchpad questions? [06:11] He's pretending to ask these questions in a language.. [06:11] that I think is indigenous to the native population of Alaska [06:11] or northern Canada [06:11] if I get rid of my launchpad account to make him go away, he wins, right? [06:12] chill out a minute [06:12] just chasing up a sys admin [06:12] lifeless: alright, will do [06:13] ethana2: spm should be back soon and we'll see what we can do [06:14] clearly ethan-anderson is being a pain. [06:14] did you have a bug reference? [06:14] lifeless: it's ozzymandias [06:14] he made a dumb bug about magnets erasing hard drives [06:16] Interesting, google suggests that's bug 380738, but that bug appears to be private... [06:16] Bug 380738 on http://launchpad.net/bugs/380738 is private [06:17] holy cow [06:17] they made it private [06:17] whaaaaat, the dude sent me an email [06:17] It turns out that you actually weren't the user that I was wanting to be [06:17] trolling all along. In fact, she doesn't even use launchpad at all. [06:17] (google has a cache of that page) [06:17] I think he's lying [06:17] he knows I'm a guy. [06:18] ethana2: next time something like this happens, please ask a question at https://answers.launchpad.net/launchpad - thats guaranteed to get the LP CHR folk to look at it promptly. Asking in the bug itself is pointless as the sysadmins *don't read every bug* [06:18] there are thousands of projects in lp. [06:19] ah, k [06:19] bringing it up here is good too [06:19] however, for book keeping, I would like you to ask a question anyhow [06:19] I think I'll just come right here next time [06:19] ah, k [06:19] that will let the sysadmins have a record [06:20] include a link to https://bugs.edge.launchpad.net/ubuntu/+bug/380738, and the qeustion you linked before [06:20] Error: This bug is private [06:20] k [06:21] brb [06:42] lifeless, ethana2: https://answers.edge.launchpad.net/launchpad/+question/72394 was created about this a couple of weeks ago. [06:43] wgrant: ah, I wasn't even aware of that launchpad question [06:43] It seems to be trapped in the 'Needs Information' status, since I commented on it and Answers is old and broken. [06:44] spm: account ethana-anderson needs to be terminated with prejuidice [06:44] lifeless: That's not doable through the web UI yet? [06:44] ethana-anderson? [06:44] * ethana2 checks account [06:45] the account was ~ethan-anderson [06:45] https://edge.launchpad.net/~ethan-anderson I assume [06:45] wgrant: perhaps, but the nice thing about letting the folk responsible for foo do foo is that they log it etc correctly. [06:45] yes [06:45] lifeless: That's true. [06:45] wgrant: so I don't do other peoples foo unless its a crisis [06:45] wgrant: regardless of capability. [06:45] lifeless: Right. [06:46] ethana2: both accounts have the same email address. I suspect you've been compromised in some way. ? [06:46] spm: I really, really hope not. [06:46] spm: two accounts can't have the same email address [06:46] spm: Is that possible? [06:46] that's possible, two accounts with one email? [06:46] are you sure they are the same? [06:46] oh hang on - confusing the crap outa myself... [06:46] That's what I thought. [06:46] -ETOOMANYETHANS!!! :-) [06:46] My email can't be compromised-- my passcode is secure as heck and I never access my email from Windows machines [06:47] when I must, I change the password the moment I get onto a secure system like Ubuntu or OS X [06:47] ethana2: so it isn't "password" then? [06:47] jamesh: oh goodness gracious no [06:47] jamesh: its '"password"' [06:47] it's pseudorandom, alphanumeric chars, with some capitalization [06:47] that's a pretty long password [06:48] ..like more than 10 [06:48] jamesh: heh [06:48] I have an algorithm I use to generate my passwords.. [06:48] I'm kind of proud of it [06:48] apg is nice [06:49] but there are other ways of being compromised than password. [06:49] in any event, account is suspended. [06:49] Thanks spm. [06:49] ethana2: can you pls make sure I've zapped the troll's and not yours? :-) [06:49] spm: mine is ~ethana1 [06:49] ~ethana2, sorry [06:49] the troll is ~ethan-anderson [06:50] cool. that should be fine then. [06:50] ethana2: Whats your algorithm? [06:51] * ethana2 pm's cody-somerville [06:52] * cody-somerville can now determine ethana2's password at will. :P [06:52] only if you know the following things: [06:52] my leetscript exception [06:52] my capitalization freqency and offset [06:52] and my original phrases [06:53] I'd trust the xubuntu maintainer not to go hacking my random accounts.. [06:53] But do you trust Freenode? [06:53] Or the Internet in general? [06:53] wgrant: I generally trust freenode with pm's... [06:54] ..but I trust _no one_ with my passwords [06:54] I go too far to secure them to give them away [06:55] spm: Can you close the question? [06:56] wgrant: I can mark it resolved? yes. but anyone can reopen aiui. [06:58] spm: I speak of the question requesting the suspension of the fake account (https://answers.edge.launchpad.net/launchpad/+question/72394). Why do we care if somebody can reopen that? [06:59] oh. right. wrong question. yes. one sec. [07:00] wgrant: done. fwiw, we now can (much losa cheering is heard) suspend accounts in the UI now. [07:01] spm: Thanks again. [07:01] fwiw? [07:02] For What It's Worth [07:02] ah [07:02] http://acronyms.thefreedictionary.com/ <== useful. I have it on my personal bookmark toolbar :-) [07:03] lifeless in particular, keeps hitting me with new and amazing acronyms. ;-) [07:03] spm: what records are needed - just a question? [07:04] bsdgames' “wtf” can also be useful, although its database isn't extensive :( [07:04] in terms of suspension? we usually put a note to why in their user info field doohickey. there's a "reason for deactivation" field. [07:05] I usually add links to the question requestion suspension and/or examples as to the why in said field. [07:06] wgrant: you cmd line junkie you. ;-) [07:06] spm: That's me. [07:11] well, thank you a ton for all your help [07:11] I guess now I hope he leaves me alone, and go to bed [07:12] pretty tired.. rock on, guys [07:12] wgrant: 'wtf' thought - if you can, could update that list with a copy of http://www.xs4all.nl/~jtv/gtf/ ==> /usr/share/games/bsdgames/acronyms ?? [07:12] shall I log a ubuntu bug? :-) [07:13] spm: I recall a bug like that being rejected before. [07:14] I don't mind doing it [07:14] https://bugs.edge.launchpad.net/ubuntu/+source/bsdgames/+bug/334574 yarp. get it updated in debian instead. [07:14] Launchpad bug 334574 in bsdgames "wtf doesn't know twss" [Wishlist,Won't fix] [07:17] spm, Can you file a bug on that and subscribe me? [07:26] cody-somerville: https://bugs.edge.launchpad.net/ubuntu/+source/bsdgames/+bug/385072 and thanks! [07:26] Launchpad bug 385072 in bsdgames "Please replace the existing wtf acronyms file with the list from the GTF" [Undecided,New] [07:54] nhandler: that should be the lot done. given the number of renames, I'd appreciate if you could double check me that I got them all correct. === NCommander is now known as ApportRetracerPo === ApportRetracerPo is now known as NCommander [09:31] Hello, I need some help. [09:32] Last wednesday I uploaded a po-file for translation for my team-project (Communtu) and I would like to know how long does it take to review the uploaded file. [09:33] Hi Knut-HB, I sent an email to the project because we have a question about licensing. [09:34] Knut-HB: I sent it to Torsten. [09:34] Ah yes, we talked about that yesterday. So there will be a delay in reviewing the file until the licensing-question is solved? [09:34] henninge: ok [09:35] Knut-HB: I don't know if that was related but now that the licensing question is raised, that would definietly put it on hold. [09:35] hm ah ok [09:36] Knut-HB: but there is another problem with the import, too. [09:36] Knut-HB: it is supposed to be a template but it is not called *.pot [09:36] henninge: which one? [09:36] Knut-HB: I only see this: [09:36] https://translations.edge.launchpad.net/communtu/+imports [09:37] let me see it [09:37] Knut-HB: ah, and it uses German as a source language [09:37] Knut-HB: that's a blocker. [09:37] Knut-HB: that definitly is a stopper because our policy requires the source language to be English. [09:38] yes. we want to use launchpad to translate it from German to English. our goal is to have it translated completely until the LinuxTag [09:38] ah ok =/ [09:38] Knut-HB: we have some good reasons for requiring this, though I understand it's pretty annoying to you... [09:38] Knut-HB: Oh, not much time ... [09:40] jtv: so it could take much more time until we can translate or worse: we won't be able to use launchpad to translate? [09:40] henninge: yes =/ [09:41] Knut-HB: unfortunately, yes. We (and GNU gettext) assume English as the source language. [09:41] (AFAIK the assumption first snuck into gettext with the support for plural forms) [09:43] From English to German is fine, but we don't support going the other way. [09:43] jtv: ah ok... so we have to find some other way to translate it as a team? currently I do the work with poedit but it's just me who can work on the file [09:44] Knut-HB: afraid so. :-( [09:52] ah ok :( so i can delete the file from the importing queue? [10:44] another question concerning the po-file: if we would change it to a pot-file, would it be enough to rename the file from po to pot or is the structure of the pot-file totally different from the po-file? [10:49] Knut-HB: no, not differnet at all. === henninge_ is now known as henninge [10:50] henninge: thanks :) [10:51] Knut-HB: a template is what xgettext gives you and it looks like a po file but with all empty msgstr - just like your file. [10:51] Knut-HB: it is custom, though, to name it after the translation domain and not just "template.pot" or "message.pot". [10:52] Knut-HB: so we don't have to guess the translation domain when approving it. [10:52] henninge: what do you mean with that? [10:54] Knut-HB: the translation domain is the name of the template. [10:54] Knut-HB: It is what your translations are looked-up by at run-time. [10:55] Heya. Any problems with bazaar hosting? I can connect via ssh OK but bzr isn't able to pull/push anything? [10:57] alexharrington: Working fine for me. [10:57] What error are you getting, if any? [10:58] wgrant: alex@pca410:~$ bzr branch -r80 lp:~alexharrington/xibo/pyclient pyclient-80 [10:58] Read from remote host bazaar.launchpad.net: Connection timed out [10:58] if i do ssh alexharrington@bazaar.launchpad.net it connects fine and tells me no shells are available as I'd expect [10:58] alexharrington: thats an XMLRPC timeout [10:58] alexharrington: bzr lp-login [10:58] wgrant: not related [10:59] alexharrington: there is a bug open on this. Shortly, python's xml rpc library doesn't honour http proxy settings [10:59] lifeless: OK - it was working fine 10 minutes ago! [11:00] lifeless: Isn't XML-RPC done to an appserver? [11:00] wgrant: yes [11:00] Like xml-rpc.edge.launchpad.net? [11:00] oh good point [11:00] Which bazaar.launchpad.net isn't? [11:00] I really have to learn that after I EOD cause I'm tired, I gotta Stop. [11:00] Haha. [11:00] alexharrington: please ignore everything I said ;) [11:00] lifeless: OK - thanks anyhow [11:00] alexharrington: So, 'bzr lp-login' [11:01] alexharrington: I would try without the -r [11:01] alex@pca410:~$ bzr lp-login [11:01] alexharrington ] https < 0KB 0KB/s | [11:01] goes through fine [11:01] wgrant: note that it could still be http :) [11:01] I'm trying without the -r (although I do actually want an old revision) [11:01] lifeless: Why would it be? [11:02] seems like it's still hanging up [11:02] wgrant: because if ssh is working, and hes not logged in, then it will be using http [11:03] lifeless: Which was why I asked for bzr lp-login. [11:03] But it certainly seems like it should be using bzr+ssh, as there's a username set... [11:03] the bzr lp-login goes through fine (see above) [11:03] wgrant: :) leaving to your capable fingers [11:04] lifeless: OK. [11:04] wgrant: Same as before: alex@pca410:~$ bzr branch lp:~alexharrington/xibo/pyclient pyclient-80 [11:04] Read from remote host bazaar.launchpad.net: Connection timed out [11:04] alexharrington: So, you can SSH and auth to bazaar.launchpad.net fine, from that same host? [11:05] wgrant: alex@pca410:~$ ssh alexharrington@bazaar.launchpad.net [11:05] No shells on this server. [11:05] Connection to bazaar.launchpad.net closed. [11:05] Yep [11:05] alexharrington: What if you 'bzr branch bzr+ssh://alexharrington@bazaar.launchpad.net/~alexharrington/xibo/pyclient'? [11:07] wgrant: It's thinking. Looks like it's going to timeout again. Perhaps I should try a good old reboot? :D [11:08] wgrant: I wonder if there's a firewall that kills connections that are idle for "too long"? [11:08] spiv: Possible, I guess. [11:08] wgrant: some bzr+ssh commands can take a little while (e.g. 3 minutes) to get a response for sufficiently large branches. [11:08] spiv: Yeah. [11:08] Anyway, I need to eat dinner. [11:08] alex@pca410:~$ bzr branch bzr+ssh://alexharrington@bazaar.launchpad.net/~alexharrington/xibo/pyclient pyclient80 [11:08] Read from remote host bazaar.launchpad.net: Connection timed out [11:08] wgrant: a .bzr.log with -Dhpss info could diagnose that. [11:09] wgrant: OK - Thanks anyhow [11:09] alexharrington: ok, please repeat, but add "-Dhpss" to the command line [11:09] But spiv's suggestion (adding -Dhpss) is good. [11:09] alexharrington: then pastebin the contents of ~/.bzr.log (ideally trimmed to just the latest bzr branch invocation, but the whole thing is ok too) [11:09] spiv: okey [11:10] alexharrington: I *suspect* it's a taking a while for the server to respond to the Repository.get_stream command [11:12] spiv: http://pastebin.ubuntu.com/191545/ [11:12] spiv: I let it run until it gave me the first timeout message then ctrl-c'ed it [11:12] alexharrington: (although it's not a particularly large branch) [11:12] spiv: It's only a few MB [11:12] alexharrington: huh, that's odd [11:13] alexharrington: so it's not my first guess [11:13] alexharrington: that's just the initial "open" command, which is pretty much instantaneous [11:14] alexharrington: which suggests that actually it *is* failing to establish an SSH connection [11:14] spiv: It's normally fine. I use this most weeks to make a few commits [11:14] spiv: we already proved I can ssh directly to bazaar.launchpad.net [11:14] Right, which makes it odd. [11:15] And the log clearly shows that bzr is using OpenSSH (i.e. the 'ssh' executable) to establish the connection. [11:16] spiv: I just tried branching lp:xibo/1.0 which is our stable and it went through fine [11:16] spiv: As did the branch I wanted originally [11:16] spiv: How odd [11:16] Ok, then I have no idea what's going on! [11:17] I suspect some sort of network weirdness on your end. [11:17] spiv: Dunno. I'll be more concerned if it happens again [11:17] :D [11:17] e.g. bad MTU issues or something. [11:17] spiv: I doubt it. I expect we'd have had others here complaining if there was a general issue. There's 600 odd PCs hanging off our net connections [11:18] spiv: Wierdness with this particular PC I could believe though :D [11:18] The next step in debugging this probably involves inspecting TCP dumps, ideally on both sides of your firewall/router. [11:19] spiv: If it does it again then I'll get in to that. If it was just a one-off glitch then I'm not too fussed. I don't have the time to sink in to it right now :D [11:19] spiv: Thanks anyhow - and for all your help [11:19] or perhaps hacking bzrlib/transport/ssh.py to add "-vvv" to the ssh command line. [11:20] alexharrington: cool. I hope it keeps working :) [11:20] spiv: me too :D [11:20] * wgrant returns. [11:20] How odd! [11:21] wgrant: Yep. Very [11:29] pcabido: Here is your solution: ;-) [11:29] pcabido: remove gtg from the Gnome super project! [11:30] pcabido: that enforces stricter translation permissions than what you have for your own project. [11:31] pcabido: Then you will not be bound to their restrictions and can translate into whatever language you like. [12:17] spm: The renamed LP teams all look correct. Thanks a lot [12:18] There appears to be something broken with the kernel in jaunty-proposed. Launchpad says linux 2.6.28-13.44 was published into jaunty-proposed 7 days ago, but the actual binaries published to the Packages file are still ABI 12. [12:21] Oh, ignore me, it's not a launchpad problem, it's just me not fully appreciating how binary NEW works. [12:22] maxb: That it wasn't obvious could be a Launchpad bug, though. [12:23] Did you miss or misunderstand the 'Successfully Built (NEW)' status? [12:24] wgrant: 'NEW' does not imply the existence of 'PUBLISHED' [12:24] lifeless: Huh? [12:24] wgrant: Am I being tired again? [12:25] lifeless: Possibly - I'm not sure how existence of one string implying the existence of another is relevant here... [12:25] But I could also be tired. [12:25] more states [12:26] I'm saying, perhaps the UI should say 'Successfully Built (NEW), will be published in X minutes' [12:26] Ahh, I see. [12:26] You can't do that. [12:26] But replacing 'NEW' with something more obvious would work. [12:27] you can't? [12:27] At the moment it just shows the queue status (which would be NEW, ACCEPTED or REJECTED), which is unobvious unless you know how the queues work, which is unlikely unless you're a developer. [12:27] No - NEW requires manual pushing. === Pici is now known as ZarroBoogs === ZarroBoogs is now known as Pici [12:50] How do I link to a bug in an external bug tracker from a Launchpad bug? [12:53] wgrant: The problem was that I was looking at the SPPH page, which doesn't display queue states at all [12:55] Had I clicked through to the version page I would then have seen the NEW, but I didn't realize I needed to [12:58] maxb: Well, that's not surprising - it is the SPPH, not the BPPH. [12:59] But, SPPHs have no browser views. [12:59] Were you looking at the DSPR, or the DSSPR? [12:59] https://launchpad.net/ubuntu/+source/linux/+publishinghistory [12:59] Ah, right. [13:00] That could perhaps show the build status like Archive:+index does, but that's always awfully slow to render... [13:00] Yeah, user error on my part, never mind :-) [13:04] The thing that I don't get is. [13:04] Xmonad has a package in Ubuntu. [13:04] and a bug tracker at Google Code [13:05] and some of the bugs files for the Ubuntu package should be linked to the upstream bug tracker at Google Code [13:05] but I don't understand how that is to be done [13:05] cyberixae: Hit 'Also affects project...' on the bug, then give it the project (if it hasn't worked it out already), then give it a link to the bug. [13:06] It won't sync the status yet - that's coming soon. [13:20] wgrant: What project? [13:20] cyberixae: xmonad, presumably. [13:21] But there is no project xmonad in Launchpad [13:21] You can create one. [13:22] But I'm in no way affiliated with xmonad project [13:22] That's fine. [13:22] We do it all the time when triaging Ubuntu bugs. === mrevell is now known as mrevell-lunch === savvas_ is now known as savvas === barry changed the topic of #launchpad to: https://launchpad.net/ | Help contact: barry | Join https://launchpad.net/~launchpad-users | Channel logs: http://irclogs.ubuntu.com | Launchpad's Open Sourcing: https://dev.launchpad.net/OpenSourcing [14:06] wgrant: I got the project registered, but I could not choose the bug tracker for that peojct as it is not in the list of available bug tackers [14:07] wgrant: Where do I register a bug tracker? [14:12] cyberixae: I've got to go to bed, but there's a conveniently placed CHR person just over there. [14:12] barry: ^^ [14:12] wgrant: thanks [14:12] cyberixae: i can help you [14:13] cyberixae: which project and which bug tracker? [14:14] barry: xmonad [14:15] http://code.google.com/p/xmonad/issues/list [14:15] https://launchpad.net/xmonad [14:15] cyberixae: k thx. hang on a bit... [14:17] cyberixae: https://launchpad.net/bugs/bugtrackers/+newbugtracker [14:27] thanks [14:28]