[10:35] <hrw> hi
[10:37] <hrw> can someone remind me where lp: is defined?
[10:42] <hrw> found
[14:33] <jumoit> hey, here's a quick question if there is a chance to get anonymous access via bzr?
[14:34] <jpds> jumoit: Yes, you can branch over HTTP.
[14:34] <LeoNerd> If your branch is visible by HTTP, then sure
[14:35] <LeoNerd> Though I don't think "anonymous" is quite the right word here; obviously the server can still log IP addresses and whatnot.. but perhaps "unauthenticated" is a better term
[14:35] <mgz> bzr branch tor:...
[14:35] <mgz> someone want to write a plugin? :)
[14:35] <jumoit> thanks, you guys. then, i'm to try what you just told me...then, reply you.
[14:36] <jumoit> LeoNerd, yeah, that's exactly what i wanna to ask around here. thanks.
[14:38] <jumoit> actually, i wanna get source from here https://code.launchpad.net/canonical-identity-provider by the unauthenticated way. :)
[14:40] <mgz> that's no problem, just branch lp:canonical-identity-provider without a launchpad login set in your bazaar configuration
[14:43] <jumoit> mgz, when trying with unauthenticated, bzr is asking me login with ssh...
[14:44] <jpds> jumoit: Right, because you did bzr launchpad-login at some point.
[14:44] <jpds> jumoit: You'll have to edit: .bazaar/authentication.conf
[14:45] <mgz> jumoit: `bzr config --scope=bazaar --remove launchpad_username`
[14:46] <mgz> and the authentication.conf bits can then be left as-is
[14:46] <mgz> and you can rerun `bzr launchpad-login YOU` later to set it again
[14:48] <jumoit> jpds, yeah, i can follow what you just told setting up ssh with launchpad...but, you know, there are so many people not willing to set up an account when only cloning source from launchpad...so, i have to find out a good way to help people get source without setting up an account on launchpad to get it.
[14:49] <jumoit> mgz, any ideas on that?
[14:49] <mgz> if they don't want to set up ssh, they need to just not set their launchpad username
[14:50] <mgz> I agree setting up ssh is hard for people who don't use it on a daily basis anyway
[14:50] <wolfrage> Can some one please walk me through the standard steps to create a feature branch of a project in order to patch a bug?  The project is: lp:simplegc.
[14:51] <wolfrage> I also need some better understanding, so can I not patch this just on my local machine, but I have to create a branch on LaunchPad, but I keepdoing it wrong...
[14:51] <jpds> wolfrage: bzr branch lp:simplegc
[14:51] <wolfrage> Once the branch is their how do I get the code locally so that I can do the patch
[14:51] <jpds> wolfrage: Then: bzr branch simplegc feature-name
[14:52] <wolfrage> ahhh OK I am using bazaar explorer and the feature option is not a normal option, though one would think it would be in colaborate
[14:53] <wolfrage> bzr branch will create a copy of the branch in the current directory right, so If I want it to reflect right then that should be done in a directory called trunk?
[14:54] <wolfrage> by reflect right I just mean that my previous experience with feature branches seemed to just use side by side directory levels.
[14:54] <jumoit> mgz, when inputing "bzr branch lp:canonical-identity-provider" from the terminal,  some errors came up, and telling me..Permission denied (publickey).
[14:55] <wolfrage> jumoit: just went through this you need to have a proper rsa key in your .ssh directory
[14:55] <mgz> jumoit: you still haven't deleted your launchpad username from the config :)
[14:56] <mgz> really you should just go through the ssh setup and get that working though
[14:56] <jpds> wolfrage: http://doc.bazaar.canonical.com/bzr.2.5/en/tutorials/using_bazaar_with_launchpad.html
[14:56] <wolfrage> jumoit: https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair
[14:56] <mgz> right you two, help each other :)
[14:56] <wolfrage> jpds: Thanks
[15:04] <jumoit> you guys, thanks. after taking steps described in these links, i can set up ssh with launchpad. and i can get source successfully...but, other guys that only wanna get source (like git clone)  think that there is no need to set up an account on launchpad. so, all i now need is all about how to get access to projects launched on launchpad in the unauthenticated way?
[15:06] <mgz> jumoit: all they need to do is *not* run bzr launchpad-login
[15:06] <mgz> you were having issues because you'd done that, then also perhaps because it'd stored the bzr+ssh url for the branch you were looking at
[15:08]  * jelmer waves to mgz
[15:09] <mgz> hey jelmer!
[15:09] <mgz> enjoying your snow?
[15:10] <mgz> that was a nasty shock coming through london after being in sunny atlanta
[15:10] <jelmer> mgz: ah, so it's your fault!
[15:12] <jumoit> mgz, actually, i'm also new to bzr...so, seems that there is a learning curve to get bzr work like a charm. but, now, i need only one instruction to get source on launchpad anonymously.
[15:13] <jumoit> let's say, get source from https://code.launchpad.net/canonical-identity-provider by only one instruction.
[15:13] <jelmer> mgz: what were you up to in sunny Atlanta?
[15:14] <mgz> juju sprint
[15:14] <mgz> was pretty good
[15:15] <mgz> jumoit: `bzr branch lp:canonical-identity-provider`
[15:18] <mgz> though as we discovered last week `bzr branch http://launchpad.net/bzr` for instance also works, due to some funky launchpad redirecting
[15:20] <lifeless> mgz: o/
[15:20] <lifeless> mgz: thanks for your thoughtful blog post
[15:23] <mgz> hey lifeless, sorry for missing you on irc a few days earlier when you pointed me at the subunit changes :)
[15:23] <lifeless> mgz: de nada :)
[15:26] <jumoit> mgz, thanks. it works well in another user (www-data) on my workstation running ubuntu10.04 by "zr branch lp:canonical-identity-provider".. but, bzr told me that writing or accessing private data needs to set up an account on launchpad.
[15:27] <mgz> right, it very helpfully does. getting the source worked fine, and that branch can be pulled fine from there on
[15:28] <mgz> if they want to submit things back to you, they do need to either do that ssh setup or host their own branches somewhere else that you can access
[15:29] <jumoit> mgz, thank you for your suggestion. then, i will tell them  what you just told me. thanks again. :)
[15:58] <LarstiQ> mgz, jelmer: oh, if you want some more snow, we have plenty!
[16:00] <mgz> no, it's okay, you can keep it :)
[16:00] <LarstiQ> mgz: if you change your mind, I'm sure it will still be here till April
[16:15] <jelmer> LarstiQ: (-:
[16:15] <jelmer> It seems like Brits and their trains are fairly delicate creatures..
[16:24] <wolfrage> Ok so from earlier I have made my patches, now I need to upload my feature branch to LP right, then I can request a merge right?
[16:25] <jelmer> wolfrage: yep
[16:27] <wolfrage> jelmer: is it: bzr register-branch
[16:28] <wolfrage> jelmer: or do I just push?
[16:29] <jelmer> wolfrage: you can just push
[16:29] <jelmer> 'bzr register-branch' is only really useful if you are hosting your branch elsewhere
[16:30] <wolfrage> jelmer: OK
[16:34] <jumoit> mgz, still there? any ideas on this case. (under /home/user1, setting up an account on launchpad as well as ssh (both works well). but, for the sake of security, i don't want to share private key under /home/user1 with /home/user2. but, user2 still can get source on launchpad by the authenticated way. PS: user1/2 both based on the same workstation)
[16:35] <mgz> private keys are password protected and user-only readable
[16:36] <jumoit> mgz, then, i set up a file called /home/user2/.ssh/config
[16:36] <mgz> ssh will even complain if you have the wrong unix perms on your private key
[16:37] <mgz> the solution is user2 also creates a set of ssh keys
[16:38] <jumoit> but, so many ssh keys is not a good idea on the same workstation, i think. so, what would be the best for the case.?
[16:39] <mgz> it's the right solution, the .ssh directory is per-user rather than machine wide for a reason
[16:40] <jumoit> let's say, user1 is my home, while user2 is something else like www-data for apache2. user2(www-data) is used to host some sites
[16:40] <jumoit> user1(my home) used for development.
[16:43] <mgz> okay, so if both users are really you, then you're doing something else wrong :)
[16:45] <mgz> either your bot should have its own credentials, or it should use read-only access, or you should just manually do the bot steps
[16:47] <jam> jelmer: /wave
[16:47] <jelmer> hey jam :)
[16:48] <jelmer> jam: isn't this time well past your work day?
[16:48] <jam> jelmer: yeah, it is almost 9pm now, but I have my work call with my US manager (deryck), so I was around
[16:49] <jumoit> mgz, all right, all right...actually, there is some private data on launchpad required to set up account on launchpad...so, when deploying some site under /home/www-data, must set up one account as well to get access to private data.
[16:49] <jam> mgz, jumoit: if you don't want to share the ssh creds, can you just put both pub keys into the same LP account?
[16:49] <jam> I realize having a bot account would be ok, but sometimes that is clumsy (LP requires a unique email address for every user, so bots have to get yet-another address from my home domain)
[16:50] <mgz> jumoit: I don't see why the www-data needs write-access to launchpad currently
[16:50] <jam> mgz: well, he may want it to use bzr+ssh, and we never did implement unauthenticated ssh access.
[16:50] <jelmer> jam: ah :-)
[16:51] <jumoit> mgz, when deploying sso site against https://launchpad.net/canonical-identity-provider, it really needs what i just said...
[16:52] <mgz> really? I doubt that... in what manner?
[16:53] <jumoit> mgz, when setting up a virtual env by fab bootstrap, it really needs bzr
[16:53] <mgz> it needs read-only access, I can understand
[16:53] <mgz> can't see why it'd need to push changes
[16:54] <jumoit> no, it need more...
[16:54] <jumoit> http://bazaar.launchpad.net/~canonical-isd-hackers/canonical-identity-provider/trunk/view/head:/requirements/config-manager.txt
[16:54] <jumoit> http://bazaar.launchpad.net/~canonical-isd-hackers/canonical-identity-provider/trunk/view/head:/fabtasks/environment.py
[16:54] <jam> mgz: well, they hard-coded bzr+ssh urls, so thus need bzr+ssh :)
[16:54] <jam> I haven't ever seen bazaar.isd. I wonder if that is inside the canonical network.
[16:56] <jumoit> jam, i have no idea on that. but, i think, mgz could tell you more
[16:56] <jumoit> :)
[16:56] <mgz> file a bug, and then fix the branch, there's no reason you have to live with other people's broken code when you have access to the source and they take patches :)
[16:58] <jumoit> yeah, i have done that. plus, you guys in that project will promise to correct it.
[16:58] <mgz> the point is, you can fix it, then propose the fix
[16:58] <mgz> no reason to wait for someone else to get to it.
[16:59] <jumoit> no, i have no right to push...just report bugs. that's.
[16:59] <jumoit> that's all
[16:59] <mgz> you don't need push rights
[16:59] <mgz> you fix your branch. and comit
[16:59] <mgz> then push to your launchpad namespace, and do 'propose merge'
[16:59] <jumoit> yeah, good point.
[17:00] <jam> jumoit: the *easy* answer, give the bot an ssh key, and then add both ssh keys to your account. The other way, rename all the "bzr+ssh://bazaar.launchpad.net/" branches to be "lp:" and bzr will figure out where to get it.
[17:00] <jam> bazaar.isd is trickier.
[17:00] <jam> environment.py rewrites them to be from bazaar.launchpad.net, but I'm guessing the deployment process does it differently for production.
[17:02] <jumoit> jam, like you said, that will be replaced by bazaar.launchpad.net. so, i guess that you're also a python programmer, right?
[17:05] <jumoit> well, you guys, thanks for your helping around here. see ya. and have a good time. :)
[17:05] <jam> good luck jumoit
[17:05] <jumoit> well, let's hope so, jam. :)
[17:06] <jumoit> jam, you know, python is really python;-)