[00:03] * nedko is badly surprised that vcs-imports is not supporting mirroring of svn:// urls [00:04] nedko: what [00:05] mwhudson: i get "The URI scheme "svn" is not allowed. Only URIs with the following schemes may be used: bzr+ssh, ftp, http, https, sftp" [00:05] when trying to register svn branch for mirroring [00:05] That doesn't sound like you're registering a vcs-import. [00:06] right, that sounds like +addbranch [00:07] hmm [00:07] nedko: you want https://code.edge.launchpad.net/+code-imports/+new [00:08] yes it is addbranch [00:08] sorry [00:08] :S [00:11] mwhudson: should i ask here for vcs-import branches review or this should happen somehow automatically? [00:39] https://code.launchpad.net/~vcs-imports/lash/trunk is the branch pending for review [01:08] hey [01:08] Can anyone help with the CoC signature process? [01:09] I'm getting an error msg when I try to submit the signed code [01:09] "The signed text does not match the Code of Conduct. Make sure that you signed the correct text..." === DasIch_ is now known as DasIch [01:32] anybody here? [01:38] Yes [01:39] Can you pastebin what you're trying to input? [01:39] yeah. how do I pastebin? [01:40] sry. my first time [01:42] http://pastebin.ubuntu.com [01:42] k i did it [01:43] http://pastebin.ubuntu.com/44061/ [01:43] it's not showing everything that I copied though [01:47] evsthomas, try starting from scratch [01:47] I'm not sure what you mean exactly? [01:49] evsthomas, Get rid of what you have [01:49] yeah [01:49] and start from step 1? [01:49] Take a brand new copy of the text you're trying to sign [01:49] sign it [01:49] and try getting launchpad to accept it again [01:50] do I copy the text straight out of the txt file? [01:50] or do i need to do the --clearsign thing? [01:50] Download the file [01:50] and use gpg to sign it [01:50] k, just did [01:50] then copy and paste that output into the text box in launchpad [01:51] how do you use gpg to sign it? incase I'm doing that wrong [01:51] I used gpg --clearsign UbuntuCodeofConduct-1.0.1.txt [01:52] on the terminal [01:52] no [01:52] gpg --clearsign < UbuntuCodeofConduct-1.0.1.txt [01:53] ok. I copied and pasted the output and no luck [01:54] i;ll try version 1.0 real quick too [01:55] same error "The signed text does not match the Code of Conduct. Make sure that you signed the correct text (white space differences are acceptable)." [01:55] heres the pastbin of what i did [01:56] http://pastebin.ubuntu.com/44070/ [02:04] anybody else have any ideas? [05:17] wher to start [05:20] It likely depends on what you want to do. [05:24] I just want to develop plugin for learning purposes, adn two options currently, Geertjan's book and this link [05:24] http://www.antonioshome.net/kitchen/netbeans [05:25] which is also suggested by him [05:26] got to go for breakfast :last five minute, 'll be returning plz reply!!!! [05:39] wgrant : tell me, i am starting off [05:59] sorry wrong place, must be confusing intrepid interface [05:59] did not sleep whole nice sorry again [05:59] Riiight. [07:02] Hi. I'm in the process of hosting my code (bzr branch) at Launchpad, and encoundering some difficuties [07:03] following the instructions at https://help.launchpad.net/CreatingAHostedBranch [07:03] I get "[user] doesn't have a registered SSH key" [07:03] how do I register an SSH key? [07:05] adam: this page should explain it https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair [07:05] stdin: thanks. === mwhudson_ is now known as mwhudson [10:22] vcs-imports branch https://code.launchpad.net/~vcs-imports/lash/trunk is still in pending review state, can someone please review it? [10:54] nedko: it's sunday [10:56] nedko: but, done [10:56] mwhudson: thank you [10:56] mwhudson: to my original question, should i ask here for review here or i should wait... until next work day for example? [10:57] nedko: waiting one working day usually works pretty well [11:00] why is manual review needed at all? [11:06] to stop someone typing 'http://svn.debian.org/' or 'http://svn.apache.org/' [11:16] mwhudson: you mean submiting things more than once? or you mean importing large repos? [11:17] nedko: the latter [11:17] nedko: it has a history of upsetting the admins of servers hosted said repos... [11:18] so it is not about launchapd resources but about resources of pulled repo server? [11:20] right [11:21] well, a bit of both [11:21] Yeah. Checking out the root of a SVN repo that hosts many large projects with many branches and tags wastes a lot of time and bandwidth on both ends. [11:23] checking how much revisions has svn url, *once*, and making decision on this is trivial, there can be limit of max revisions to import without manual review, say 1000 [11:26] Well, many correct URLs will have more than 1000 revisions. [11:26] It's hard to find a good automatic heuristic because there are some very large projects out there. [11:27] I'm sure we could do better. [11:27] so only large projects will need review, isnt this better than current situation? [11:28] at least we stay on top of imports much better now, with the new system [11:28] I think there was a suggestion at some point that URLs that end in "/trunk" should be assumed to be sane. [11:29] unfortunately it was a bit sillier than that [11:29] urls that *didn't* contain 'trunk' were assumed to be insane [11:29] Oh, right, as in rejected outright? [11:30] yeah [11:30] Yeah, that was a bit silly. [11:30] cant only "strange" urls require human review? [11:30] I shouldn't really be making you think about work on a Sunday night, but I think it's probably worth considering if we can auto-approve URLs that end in "/trunk". [11:31] i.e strictly more relaxed than the status quo. [11:31] oh look, a bug tracker! [11:31] mwhudson: this is a feature ;) [11:31] also, no, because the svn.apache.org admins hate us enough already [11:32] (really) [11:32] Oh? [11:32] you can "blacklist" some svn servers too [11:32] So many things I'm happily ignorant of :) [11:32] nedko: many things are possible, yes [11:37] We could always just make everybody use bzr. That works [11:43] it is not possible though === abentley1 is now known as abentley [12:54] hi, we would like that all the generated bug-reports from the application go to the project's bug tracker at lP: if i understand correctly, all what is required is to send email to new@bugs.launchpad.net address and include 'affects projectname' line in the body. is it true? [13:03] gour, filing new bugs requires gpg-signed email, but I suggest you instead use the API to file a bug: https://help.launchpad.net/API [13:14] kiko-afk: huh, that's very inconvenient forcing end-user to have gpg-signed email for automatic bug-report :-/ [13:15] gour: because you'd like me to forge your email address, and send a whole lot of stuff as you, that stays there forever? [13:15] i see your point, though. [13:16] There's always the apport method, of course. [13:16] the apport method requires you complete using the web browser, though [13:16] if it's to be totally automated the API is the way to go [13:17] Hobbsee, it's annoying to require him to gpg-sign, yeah. maybe SPF would minimize the risk [13:17] Doesn't the API require a web browser to authorize the oauth token? [13:17] wgrant, only once [13:17] web is not convenient for automatic bug-report, it should be made as simple as possible for end (non-savvy) suers [13:17] Right. [13:18] * Hobbsee won't comment on non-savvy users, and bug reporting, as a general concept. [13:18] do you know if savannah's tracker has email interface? [13:19] Hobbsee: those 'bug reports' are unhandled exceptions, so end-user is just clicking 'send' to send traces to the tracker [13:19] gour: ah, right. [13:19] gour: that's probably OK then, as you probably won't require any more information form them. [13:20] i already prepared my 1st python patch by changing email address to LP and including 'affects projectname' in the body :-( [13:21] Hobbsee: still, i'm not sure how to use API to use LP tracker instead of sending to devel-list [13:21] * gour is trying to push the project more to LP and eventually to bzr (from CVS) [13:21] gour: i've not used the api, so i don't know :) [13:21] * Hobbsee tends to sign everything by default, so doesn't really have experience in what you're doing [13:21] i see [13:23] here http://lists.gnu.org/archive/html/gnumed-devel/2008-09/msg00109.html is example of automatic bug report [13:23] and here is the code which handles it http://rafb.net/p/rfMtLy78.html [13:24] How is the Launchpad web UI sufficiently difficult to be a hindrance? [13:24] wgrant: it keeps changing? [13:25] Not that part of the UI, [13:25] And I'm not sure of the relevance of that statement. [13:26] I guess "ease of learning the launchpad way" would be a better statement. [13:27] Possibly a bug tracker doesn't necessarily make for a great automatic backtrace collector. I guess it depends a bit on how the backtraces will be processed. [13:28] apport makes a right mess of Ubuntu bugs. [13:28] Dozens of duplicates. [13:28] A separate crash tracker would likely be better. [13:35] i'm thinking to add a new member to the team, e.g. crash-tracker and then forward all the bug-reports collected automatically to send to LP gpg-signed. [13:40] is it possible to tag new bug report via email by using 'tag' ? [13:40] gour: see https://help.launchpad.net/Bugs/EmailInterface [13:41] i'm looking at it, but wonder if i can use 'tag' while reporting new bug? [13:41] You can. [13:41] I don't think there are any that you can't. [13:41] * wgrant checks. [13:42] i'd think so [13:42] thanks [13:42] Looks like it. [13:43] cool, cool [13:46] anyone familiar with mailman's features...i didn't admin ml for a long time. howto filter all the incoming email with certain subject and move it gpg-signed to LP? [13:47] gour: I prefer using with_list [13:47] gour: does require python foo [13:47] withlist even [13:49] hello everyone. I just noticed that the page that shows all the changes for my project, http://bazaar.launchpad.net/~delfick/vigedit/vigedit-additions/changes/37?start_revid=37 shows all the revisions (37), whereas the main page for the project only shows up to rev 35, https://code.launchpad.net/~delfick/vigedit/vigedit-additions. And was wondering why that is? or is it just a matter of waiting a particular amount of time after bzr push [13:49] LarstiQ: that's mailman's API? [13:50] gour: basically, see withlist --help on the machine running mailman [13:50] LarstiQ: thanks [13:50] gour: I'm the position of being the owner of the machine that I run my lists on, if that is not the case I guess you don't have that option available to you [13:51] LarstiQ: hmm, the devel list is on savannah [13:51] delfick: I believe so. [13:51] LarstiQ: k then... [13:52] gour: then it requires more thought :) [13:52] huh, so many complications due to the fact that LP wants gpg-signed email for bug-reports :-/ [13:52] * LarstiQ goes outside [13:53] also, while I'm here, everytime I do a bzr push it tells me "Format for lp-140211244:///~delfick/vigedit/vigedit-additions/.bzr is deprecated - please use 'bzr upgrade' to get better performance" but when I do bzr upgrade it says "bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is already at the most recent format." [13:54] was wondering why ? :) [14:20] delfick: which branch are you upgrading, the local or the remote one? === doko_ is now known as doko [15:38] LarstiQ: given that question, I assume I'm doing the command in the wrong place, I'm not completely sure, but I believe the answer is local [15:41] delfick, ignore that error message, it's an annoyance [15:41] mwhudson, jml ^^ [15:41] delfick: try `bzr upgrade sftp://delfick@bazaar.launchpad.net/~delfick/bigedit/vigedit-additions/ [15:41] or do what kiko says [15:41] delfick: you don't _need_ to upgrade it per se [15:41] k then [15:42] though as kiko-afk says, it's an annoyance :p [15:42] and in fact, if you want to collaborate with older clients, maybe you shouldn't [15:42] delfick: yeah [15:42] what you mean by older clients? [15:43] delfick: older bazaar clients aren't able to use the newest formats. Everything since 0.92 can use 0.92-packs, but 0.90 and older can't [15:43] ok then [15:44] will it effect the ability to merge with other branches that may not have upgraded yet? [15:44] no [15:44] good :) [15:54] hmm, is it meant to take this long? [15:56] ahh, yay, it moved past "making backup of tree history" :) [16:08] yay, no more error message :) [16:08] thnx for the help [16:08] I'm off to bed now, cya === fta_ is now known as fta [19:28] hi [19:28] how can I add another affected package to a bug ? [19:29] loow: "Also affects distribution" [19:29] ookay [19:29] ookay [19:29] thanks [19:30] no problem [19:33] may I confirm a bug myself ? [19:34] (in ubuntu) ? [19:35] loow: see https://wiki.ubuntu.com/Bugs/HowToTriage#Confirming [19:35] loow: generally, you shouldn't confirm a bug that you yourself have reported [19:36] okay, that's what I suspected. [19:44] hello [19:45] is anyone here able to reassign this project? https://answers.launchpad.net/launchpad/+question/44018 [19:45] we really need this :) [19:47] patpiiii, no one around now, but tomorrow we'll have admins around [19:47] kiko-afk may pass by and look at his computer, if he does, he may be able to do so [19:49] thanks beuno, so i need to came here tomarrow? [19:49] kiko-afk: if you can do this then it would be great. Thanks in advance :) [19:49] patpiiii, tomorrow you'll have admins looking ar their computers :) [19:52] ah, i get it [19:52] ;] [19:52] thanks, i will be going now. Thanks for help === sabdf1 is now known as sabdfl_home === Ursinha changed the topic of #launchpad to: https://launchpad.net/ | Next meeting, all welcome: Thu 11 Sep 2008, 1800UTC #launchpad-meeting | Channel logs: http://irclogs.ubuntu.com