=== Edwin is now known as Guest15283 === Edwin is now known as Guest23072 === Edwin is now known as Guest40043 === Edwin is now known as Guest55748 === Edwin is now known as Guest93200 [01:36] hi folks, i am reading the help for create a mailing list for my team but i cant find the config for that [01:36] in the overview team page [01:39] ovnicraft: I see a 'Configure mailing list' link. Make sure you're an admin of the team. [01:42] wgrant, i am using pre-release code site, could be this? [01:42] ovnicraft: No -- I'm there too. [01:43] ovnicraft: Which team, and what's your username? [01:44] gnuthink, i solve stupid error :| [01:47] ovnicraft: gnuthink already has a mailing list. [01:47] yes [04:57] After my branch is merged into another one, can I delete mine? [04:59] RenatoSilva: You could, but that's not a normal thing to do. [04:59] why [04:59] RenatoSilva: Normally the branch will be marked Merged, which hides it from branch listings. [04:59] wgrant: the old one was replaced anyway :P [05:00] RenatoSilva: There is often metadata associated with the branch. [05:00] wgrant: I've lost my old branch with same name [05:00] eg. merge proposals, bug links... [05:00] Why do you want to delete it? [05:01] wgrant: because the code is in other place now, and because the work is done, and because if I create the branch again, as its status is "merged", it will be deleted to create the new branch with the same name [05:02] RenatoSilva: Why would you create a branch with the same name? [05:02] The branch has a different purpose, so it has a different name. [05:04] wgrant: encoding-fixes for example [05:05] wgrant: because I was finding one problem after other. Then it was merged, and it started again, so why change the name, see? [05:05] wgrant: I think it should not automatically delete merged branches anyway [05:06] wgrant: when you push to the same location [05:09] RenatoSilva: It doesn't ever delete branches. [05:09] You would have to explicitly overwrite them. [05:09] You could continue committing to the old branch and reset its status -- that's what some LP and bzr devs do with their recurrent branches. [05:09] wgrant: I don't know why I've got this impression, like it happened, I'm probably worng [05:10] Branch deletion was not invented for use on branches that are finished. [05:10] wgrant: I think I overwrote it, because I did not want a name like "encoding-fixes-2" [05:10] RenatoSilva: You should probably have just checked the branch out again and committed more. [05:11] wgrant: if that was what happened, maybe I thought that it would not work (like merging the old changes again) [05:12] bzr isn't quite that stupid. [05:12] ok [05:12] but see [05:16] imagine I did "encoding-fixes" and it was merged, then after a long time, I want to work on it again, but I'll need first to pull from the trunk, but it'll say that they have diverged. So I'll need to merge **trunk into encoding-fixes** (the opposite way), right?? [05:17] Yes. [05:17] Like you do normally when developing a branch. [05:18] ok I think I've got it then, thanks. === abentley1 is now known as abentley === ripps_ is now known as ripps === abentley1 is now known as abentley === micahg1 is now known as micahg [10:53] hello, I am having some trouble registering my GPG key in launchpad [10:53] as the response I get is that the key is already registered [10:55] how do I know wether the error is PEBKAC or not? [11:02] * SpyderZT taps the mic... [11:02] Is this thing on? [11:06] SpyderZT: Indeed it is. [11:07] Wewt! ^.^ (Though I've got a friend in another room that "May" be helping me.) [11:16] is there a launchpad dev around, a (translation) template in my project has the wrong name and needs to be renamed. [11:18] DaveDavenport: it's sunday for a lot of people. Have you filed an answer request on the launchpad project? [11:19] normally channel worked just fine :D [11:20] feel free to wait :P [11:22] Okay, Done! ^.^ [11:22] Signing that "Code of Conduct" was a mini Gauntlet for a Newb to Linux. O.o! [11:24] LarstiQ: I probly will, being a lazy bum [11:51] Where can I add more developers to a launchpad prjoject? I don't seem to find that magic knob to push to fill in login names [11:53] jaalto: create a team? that is how I did it [12:06] DaveDavenport: Clear. I was expecting "add developer" button at project page. [12:08] jaalto: Launchpad generally only allows one person or team to fill roles. If you want multiple people, you want a team. [12:08] DaveDavenport: Team created. How Do I attact it to a existing PROJECT and say that members have commit rights to bzr? [12:09] I made the team the maintainer of the project [12:09] jaalto: Have you read https://help.launchpad.net/Code/QuickStart? [12:09] not sure if you can fine-grain it [12:09] The maintainer of the project doesn't actually have anything to do with Bazaar branch permissions. [12:09] aah sorry [12:09] Permissions for Bazaar branches are controlled by the branch's owner. [12:09] DaveDavenport: Ia have read it, but is's quite general. Finding the knobs at LP pages is hard work. [12:09] I know I had todo that for translation upload. [12:10] Right, Translations is a little different. [12:10] wgrant: [that message was for you; I've read the page] [12:11] jaalto: That page tells you how to allow your branch to be committed to by multiple people. [12:11] Because bzr is a DVCS, it doesn't make sense to have branch permissions controlled by project owner/maintainership. It's all on a per-branch basis. [12:13] wgrant: I'll read more. It all quite complicated coming from SF [12:13] It is. [12:14] Because SF.net only handles centralised VCS schemes. [12:14] (it does support bzr, but in a somewhat centralised fashion which undermines much of the point of it) [12:16] wgrant: How do I give TEAM the existing bzr branch? The /Code contains only knob "(+) REgister a branch". I don't want to register new branch [12:17] jaalto: You go to the branch edit page. Something like https://launchpad.net/~///+edit [12:18] wgrant: Erm, behind that button there is something interesting. But the name "register a branch" sounded something else. [12:23] wgrant: https://help.launchpad.net/Code/QuickStart says "On the branch's overview page, you'll see an information box on the right-hand side of the page. Click the pencil icon next to your name in the Owner section and then select the team that you want to own the branch." I may be blind, but I don't detect "information box to the right" of my project https://launchpad.net/truecrypt-installer [12:25] jaalto: Branch overview [12:25] jaalto, you are looking to the project overview page, not the branch page: https://code.launchpad.net/~jari-aalto/truecrypt-installer/trunk [12:25] jaalto, it's the branch's page, not the project page. Click the 'Code' tab, then click the branch you want to edit. [12:25] jaalto: https://code.edge.launchpad.net/~jari-aalto/truecrypt-installer/trunk [12:27] andrea-bs, jml, LarstiQ: Ok I see it. The instructions should say "Project page > Code > Select bzr branch link to access branch's overview page" [12:28] That "pencil know" looks more like exclamation point (one more confusion) [12:29] knob [12:29] There's a long-standing bug on that one. [12:29] jaalto, thanks for your feedback, I'll try to make the wiki page more clear [12:30] andrea-bs, I've already made a change :) [12:30] andrea-bs, but please double-check it. [12:31] andrea-bs: That's excellent. could you even take a screenshot at the " branch's overview" page to make absolutely clear, and highlisgh the "Tabs" at top :-=) That'd what I would do it to my docs [12:34] REWORDING SUGGESTION: Let several people commit to the branch: "... click the pencil icon next to your name in the Owner section and then select the team that you want to own the branch." => click the pencil icon next to your name in the Owner section to enter Chnage Branc Details page. Select from drop-down menu 'Owner' the team that you want to own the branch. [12:38] DaveDavenport, wgrant, andrea-bs, jml, LarstiQ: I've now successfully added teams to branches. Thanks for all your guidance. [12:38] np [12:39] andrea-bs: Could you ack about that rewording? [12:39] jaalto, sure, will do [12:44] jaalto, https://help.launchpad.net/Code/QuickStart should be OK now. Could you confirm, please? [12:51] andrea-bs: [check] Could you make it more explicit for non-natives like me: "From your project page, select the Code tab, then... " => "Go to your projects main page (http://launcpad.net/PROJECT). Select the Code tab, then click the branch URL link you wish to edit to visit branch's overview page" [12:52] andrea-bs: other than that, good. [12:54] Hello, [12:55] I have an issue uploading my GPG to launchpad to be able to sign the code of conduct [12:55] the system tells me that my GPG key is already uploaded [12:55] after I paste the fingerprint of my key [12:55] can anyone help me here? [12:56] is there a way I can see the already uploaded keys? [12:57] jaalto, mh... I don't think that "branch URL" would be the right name (one may think https://something instead of lp:something). "Branch nick" sounds better, do you agree? [12:58] guZaHo, you can see your own GPG keys from https://launchpad.net/people/+me [12:58] andrea-bs: there are only two SSH keys there [12:58] andrea-bs: that i just uploaded [12:59] guZaHo, is it possible that your key is associated with an another Launchpad account? [13:00] andrea-bs: "Branch nick link". Sure, as long as it says "link" the reader can detect on the page [13:00] is it possible to create hidden/private project on Launchpad? [13:01] andrea-bs, good point. Is there any way I can find out? [13:02] andrea-bs, indeed [13:02] andrea-bs, I just found it [13:02] jaalto, OK, done [13:03] guZaHo, good, you can merge the two accounts if you wish [13:03] andrea-bs, ok? how? [13:03] andrea-bs: All good. Thanks to clarifying it. [13:03] beawesomeinstead, yes, read this page: https://launchpad.net/+tour/join-launchpad#commercial [13:04] jaalto, thank you for using Launchpad :) [13:04] guZaHo, https://launchpad.net/people/+requestmerge [13:04] andrea-bs, thanks a lot! [13:12] What is the time schedule to make https://edge.launchpad.net/ubuntu/+upstreamreport "stable", It's now living on edge [13:23] andrea-bs: At page https://launchpad.net/+tour/bugs section "Bugs by Email" is missing a link to the bugs email documentation page. Cold you add one e.g. to "... Launchpad Bugs email interface " (1st para after the picture). [13:26] jaalto, Will do. Unfortunately the tour is not the wiki, so you won't see the changes until the new Launchpad release. [13:27] Is there a sandbox PROJECT that I could test? I'd like to develop Emacs email-interface-to-LP to handle the bug reports and need a testing project where bugs are sent, responded and modified [13:28] andrea-bs: about tour, ok. [13:29] jaalto, you can do all your tests on staging.beeseek.org [13:29] I already have one for Emacs Debian BTS interface, so I need to modify it for LP, which needs GPG signed messages. [13:30] andrea-bs: You mean staging.launchpad.net? [13:31] wgrant, oops! [13:31] jaalto: staging is the place to do tests, as the database is overwritten nightly. However, that doesn't do mail stuff, in order to avoid spamming people with tests. [13:31] jaalto, staging.launchpad.net :D [13:31] jaalto: In this case I'd set up a local instance and try it. [13:35] andrea-bs: When I try to create account, fill in the captcha, I get "An illegal choice has been detected. Please contact the site administrator.". And I do select animals to rule them out and leave the colors :-) [13:36] jaalto, the right page is https://staging.launchpad.net . Sorry for the mistake! [13:36] wgrant: I would need live setup, where email come and can be responded to from Emacs/MUA. So staging wouldn't work? [13:38] andrea-bs: ok, using staging.launchpad.net [13:39] jaalto: staging quite delibately doesn't send email, and I don't think it receives it either. [13:39] jaalto, there's also https://dogfood.launchpad.net . It is like staging, but sends the e-mails to the users [13:39] andrea-bs: I don't believe it does. [13:40] I've never received mail from it. [13:42] andrea-bs: staging doesn't send? Ok. Dogfood does? [13:43] I'm feeling dizzy... [13:43] ... with these names [13:44] dogfood doesn't send mail. [13:44] dogfood is for testing Soyuz, which is irrelevant for this. [13:45] I would use https://dev.launchpad.net/Getting, and test it all locally. [13:45] So I'm out of options? I create a test-scratch-* project to standar LP, test with it, then delete the project? [13:46] wgrant: I'm afraid the setup would be too costly (in resources; I'm only me). [13:47] jaalto: 'too costly'? It's easy to set up -- the most costly thing is the download time. [13:48] wgrant: "Launchpad can only be built and run on Ubuntu" ... i don't have one. [13:49] jaalto: Ah. [13:49] Well, setting up a VM is fairly easy, and creating test projects on production is probably bad. But there might be an easier way. [13:50] Try tracking down a Canonical Launchpad dev during the week. [13:50] wgrant: At least not at this time when upgrades hosed all my VirtualBox setups and their VMs (that had Ubuntu). It's hefty work to have to deal with virtual networks and I's short of resources. [13:50] They might know something we don't. [13:50] I's => I'm [13:51] jaalto, You may use launchpad.net, do your tests on your projects and then move test bugs to the NULL project. It isn't a good solution, however it is a solution :) [13:53] andrea-bs: Probably better to create a scratch project leave the bugs there, and then later get the project deactivated. [13:53] andrea-bs: I think that is the practical one. I think I setup real project for this thing, separate from others so that the bug trackers won't suffer "test spamming" [13:53] But better still is wait until the working week and confirm with Canonical Launchpad people. [13:54] wgrant: What channel? [13:54] jaalto: Here. [13:55] I assumed some *-devel or *-dev :-) [13:55] There is #launchpad-dev, but they all live here too, and here is more correct. [13:56] wgrant: Ok. whom (nicks?) should I approach? [13:57] jaalto: Not sure. Asking generally in here during the European work day is probably your best bet. [13:58] wgrant: Ok. Will do. [14:02] I can't break a bzr lock - http://paste.ubuntu.com/250326/ [14:02] can anyone help with that? [14:02] how can I delete a blueprint I created? [14:02] I've tried "bzr break-lock lp-45197200" several times but no dice [14:02] mdke: Drop the -45197200 [14:03] Imperion: You can't. [14:03] Imperion: You can mark it Superseded or Obsolete, though. [14:03] wgrant: aiee [14:03] wgrant: still nothing [14:03] mdke: Try "bzr break-lock lp:ubuntu-docs/intrepid [14:04] wgrant: that's done it! thanks a lot [14:05] mdke: np [14:05] wgrant: I deleted the related branch long ago and the design has completely changed since then, now what? [14:05] Imperion: Mark the blueprint as Obsolete or Superseded. [14:06] wgrant: and the implementation status? [14:06] Since that's exactly what you want. [14:06] Imperion: Doesn't matter. [14:10] [About https://help.launchpad.net/Bugs/EmailInterface] It reads: "...use one of the email interface's commands, you need to start the line with a space." Is this *strict* requirement or can the commands be intended more than 1 space? [14:11] jaalto: more works too afaik [14:11] jaalto: so, strictyl, the _start_ needs to be a space :) [14:12] The start needs to be a space or a tab, in fact. [14:13] More precisely: Are any indended lines interpreted as a commands? That would be really bad, because many times when responding you would indent the SHELL COMMANDS, EXAMPLES, OUTPUT demonstrating what is needed. [14:13] The latter isn't documented anywhere exception the parsing function's docstring, so I wouldn't rely on it. [14:14] Bug #5395 [14:14] Launchpad bug 5395 in malone "Email commands should be forced to appear at the beginning of an email" [Medium,Triaged] https://launchpad.net/bugs/5395 [14:16] wgrant: ah, sanity :-) Debian also requires that command set at the beginning ends with word "quit|thanks" in a sepaate line. All the rest of the lines are then skipped. I might as well comment that bug. [14:19] jaalto: the LP email interface knows also "thanks" to stop processing [14:19] geser: I see code to handle 'done', but not 'thanks.' [14:20] then it was done and not thanks. that happens when I try to remember and don't look it up. but there is a command to stop processing [14:26] geser, wgrant: Ok, It seems to be listed last in page https://help.launchpad.net/Bugs/EmailInterface [14:27] jaalto: So it is. [14:27] Now, I should really disappear for the night. [14:28] Night all. [14:28] nigh wgrant [17:03] hi [17:15] hello. Do you know why vcs-imports is lazy? My latest Git trunk hasn't been imported for 3 days now, but it's scheduled to run "ASAP". [17:16] bvali: which branch is that? [17:16] joobsbox/master [17:17] https://code.launchpad.net/~vcs-imports/joobsbox/master [17:18] nothing I can see [17:18] (as a user) [17:20] I just wanted Rosetta to import the latest translation templates, that's why I was concerned. Can you point me where to ask for help? [17:20] The import machines seem to have been manually shut down recently. [17:37] bvali: launchpad.net/~vcs-imports says to file at http://answers.launchpad.net/launchpad-code [17:38] thanks === micahg1 is now known as micahg [19:35] how long does it usually take to have your team mailing list approved? [20:46] lamalex: from what I've heard, it never happens over a weekend [20:56] lamalex, I can approve [20:56] which one? [20:57] lamalex, I've approved all pending mailing lists [21:42] hi, i'm receiving a traceback (@ http://pastebin.ca/1523251) when attempting to branch lp:ubuntustudio-controls/0.4. does anyone have recommendations? [21:45] dtchen, looks like a broken branch [21:45] do you have write access to it? [21:51] beuno: yes [21:53] dtchen, to branch it, do: bzr branch http://bazaar.launchpad.net/ubuntustudio-controls/0.4 [21:53] then, delete the current branch, and re-push [21:53] that's the easy way :) [21:54] bzr: ERROR: Not a branch: "http://bazaar.launchpad.net/ubuntustudio-controls/0.4/". [21:54] er, right [21:54] one sec [21:55] dtchen, bzr branch http://bazaar.launchpad.net/~ubuntustudio-dev/ubuntustudio-controls/0.4 [21:56] i appear to need to do the same for trunk [21:56] (very similar backtrace when attempting to branch trunk0 [21:57] dtchen, same error for trunk? [21:57] hrm [21:57] lifeless, around? [21:57] :) [21:57] he can help us figure out which bug this is [21:57] sorry, trunk), not trunk0 [21:57] beuno: ? [21:58] lifeless, hi [21:58] lifeless, http://pastebin.ca/1523251 [21:58] dtchen, is having an ACF traceback [22:00] (my machine is running current karmic, if that's relevant) [22:01] it can be [22:01] anyhow, its a 1.19 format branch [22:01] so its most like the original ACF bug [22:02] https://lists.ubuntu.com/archives/bazaar-announce/2009-June/000250.html [22:02] dtchen: read that [22:03] lifeless: ok, thanks === _thumper_ is now known as thumper [22:10] morning [22:18] lifeless: ran the script from comment #50 and received Missing inventories: set([('andrew@aehunter.net-20090302170902-scklvwarvzv4b609',)]) [22:20] beuno: thanks! [22:52] dtchen: that should have fixed it then - its reporting that those inventories were missing [22:54] lifeless: still get an error branching 0.4, though, unless i'm missing a step? do i need to push? [22:58] dtchen: how did you invoke the script? [22:59] lifeless: python /home/crimsun/Desktop/fix-branch.py bzr+ssh://bazaar.launchpad.net/~ubuntustudio-dev/ubuntustudio-controls/0.4 [22:59] dtchen: ok; that should have fixed the branch. Uhm, try it again - it should report no missing inventories this time. [23:01] ok, Missing inventories: set([]) [23:02] dtchen: so, that would appear fixed. [23:03] and you're branching over bzr+ssh buts its still failing? [23:04] lifeless: yep, bzr: ERROR: bzrlib.errors.ErrorFromSmartServer: Error received from smart server: ('error', "Absent factory for ('ubuntustudiocontrols-20080120153904-2owlzz66z6d2b95w-1', 'andrew@a [23:04] ehunter.net-20080120154932-8y3kpx1wrrpalbdl')") [23:04] ah [23:04] your trunk is stacked too [23:04] ok, so fix trunk, then fix 0.4? [23:05] well [23:05] fix trunk [23:05] and upgrade your bzr client to a nightly build [23:05] ok, so 1.17 isn't new enough? [23:05] thats correct [23:05] ok, thanks much [23:06] stacked on stacked was fixed last weekish