[03:18] <prophetadam> hey need some help setting up SSH2 for launchpad and bzr explorer as my pushs arne't working, would be much appreciated.
[03:19] <prophetadam> using windows error message is: Run command: bzr push bzr+ssh://bazaar.launchpad.net/+branch/avaneya/
[03:19] <prophetadam> Connected (version 2.0, client Twisted)
[03:19] <prophetadam> bzr: ERROR: Connection error: Unable to authenticate to SSH host as
[03:19] <prophetadam>   prophetadam@bazaar.launchpad.net
[03:19] <prophetadam> supported auth types: ['publickey']
[03:21]  * KombuchaKip waves at prophetadam
[03:23] <prophetadam> hey!
[03:24]  * prophetadam says hi!
[03:24]  * prophetadam nods head
[03:35] <prophetadam> i gotta go
[03:35] <prophetadam> ill leave up.
[03:35] <prophetadam> catch ya man
[03:35] <prophetadam> woops wrong window
[03:35] <prophetadam> any help would be great cheers.
[04:42] <prophetadam> have since fixed problem, thanks anyways
[09:34] <ychaouche> Hi. Is it possible to setup a completely serverless environement in a team ?
[09:55] <hongyun> When push codes using bzr , there always shows an error:bzr: ERROR: Don't know how to handle SSH connections. Please set BZR_SSH environment variable. Can some one help?
[10:41] <hongyun>  When push codes using bzr , there always shows an error:bzr: ERROR: Don't know how to handle SSH connections. Please set BZR_SSH environment variable. Can some one help?
[10:45] <mgz> hongyun: if you run `ssh -V` what does it say?
[11:00] <LarstiQ> ychaouche: sure
[11:04] <ychaouche> LarstiQ: bbl lunch
[11:04] <ychaouche> LarstiQ: in the meantime, I'm trying to simulate this on my own machine and document it in a text file, step by step http://i.imgur.com/0cElN.png
[11:04] <ychaouche> any comments appreciated
[11:05] <ychaouche> bbl lunch
[15:41] <ychaouche> yaaay :) http://pastie.org/5520813
[15:44] <ychaouche> How it happend https://gist.github.com/raw/4277273/5869a6c717b7ee59eee77f011ec745403bed0564/bzr-tut.txt
[15:51] <ychaouche> So, how to solve the problem "cannot commit to branch X . It is bound to Y which is bound to Z" ?
[15:55] <LarstiQ> ychaouche: do you have some more context for that?
[15:56] <LarstiQ> ychaouche: one case I know of that occuring is with circular bindings
[15:56] <ychaouche> LarstiQ: I think I have an idea. I copied a checkout to antoher location and checked out that checkout to yet again another location.
[15:56] <LarstiQ> right
[15:57] <LarstiQ> ychaouche: I'd recommend only checking out from branches, not other checkouts
[15:57] <LarstiQ> while it can be done..
[15:57] <ychaouche> So what I'll do is copy the branch to a location, then checkout that branch to another location.
[15:57] <ychaouche> Right.
[15:57] <ychaouche> Let me try that.
[15:57] <LarstiQ> ychaouche: also, I'd bzr push/pull instead of using cp
[15:58] <ychaouche> LarstiQ: push/pull needs internet connection on remote machines
[15:58] <LarstiQ> ychaouche: no
[15:58] <ychaouche> hum ?
[15:58] <LarstiQ> ychaouche: you can also do it from and to a usb stick say
[15:59] <ychaouche> LarstiQ: what would you put in the usb stick, a whole branch ?
[15:59] <LarstiQ> ychaouche: yup
[15:59] <ychaouche> I want to work that way (instead of usb key, download a tarball)
[16:00] <LarstiQ> ychaouche: how do others get your work?
[16:00] <ychaouche> LarstiQ: I'd like to give them tarballs by email
[16:00] <ychaouche> the tarball contains my branch
[16:00] <LarstiQ> righty
[16:00] <ychaouche> they put in a temporary location
[16:00] <ychaouche> and then merge to their branches
[16:00] <LarstiQ> ychaouche: you might want to look at `bzr send -o`
[16:01] <LarstiQ> ychaouche: so that you do not have to mail around entire branches
[16:01] <LarstiQ> ychaouche: a bit more bookkeeping perhaps
[16:03]  * LarstiQ heads home
[16:11] <ychaouche> I think I'll learn how to use bzr send. I can't understand how to use bzr pull and bzr push yet.
[16:18] <ychaouche> Is pull the equivalent of checkout + merge ?
[16:18] <ychaouche> and push the equivalent of commit + merge ?
[16:20] <ychaouche> no it's confusing.
[16:36] <ychaouche> I don't know how to use send. It asks for a destination branch. Why is a destination branch required sincie I want to send my merges by e-mail anyway ?
[17:13] <jelmer> ychaouche: it needs the destination branch to determine which revisions to include
[17:15] <ychaouche> jelmer: then I really don't understand how to use it. I thought the context was : I'm working on a branch, a team member on a different location is working on the same branche and I want to *send* him my changes, my commits. So I'd use the send command, which would create "something" and I would send that guy that thing so that he could merge it to his own branche/checkout.
[17:16] <ychaouche> anyway I have to go, I'll ask the same question next week :;(
[17:16] <ychaouche> thanks to all who helped me today and happy week-end.
[17:16] <jelmer> ychaouche: you would generally use it to send changes against a common mainline
[22:05] <mortrca> I'm trying to run the bzr-email plugin, but I'm getting an error message "Unable to load 'bzr-email' in '/usr/lib64/python2.6/site-packages/bzrlib/plugins' as a plugin because the file path isn't a valid module name; try renaming it to 'email'."
[22:06] <mgrandi> have you tried doing that?
[22:06] <mortrca> I'm not sure what to rename to "email"
[22:06] <mortrca> I renamed the directory (which was previously bzr-email)
[22:06] <mortrca> and ran "sudo python setup.py install" again
[22:07] <mortrca> but I'm still getting the error
[22:07] <mortrca> Is there something else that I'm supposed to rename?
[22:08] <mgrandi> i think its installing it to /usr/lib64/ blah blah to bzr-email
[22:08] <mgrandi> try renaming the folder in that directory to email
[22:09] <mortrca> mgrandi: I see two directories there, bar-email and email
[22:09] <mortrca> Should I just remove the bar-email one?
[22:10] <mortrca> *bzr-email
[22:10] <mgrandi> yeah, try that
[22:10] <mgrandi> save it to desktop incase you need it
[22:11] <mortrca> mgrandi: Now I'm getting "Key 'upload_auto' already registered"
[22:12] <mgrandi> so you are on linux, right, what os?
[22:12] <mortrca> CentOS
[22:12] <mgrandi> is there not a bzr email package?
[22:12] <mgrandi> hmmm
[22:12] <mgrandi> one sec
[22:12] <mortrca> I don't believe so.
[22:13] <mortrca> Do you know what that means?
[22:13] <mgrandi> figuring it out
[22:14] <mortrca> I don't know if that means it isn't working or if its just trying to be polite by informing me that "Key 'upload_auto' already registered"
[22:17] <mortrca> mgrandi: I know now, it isn't working.
[22:17] <mgrandi> one seccc
[22:19] <mgrandi> so the ubuntu package seems to install it to
[22:19] <mgrandi> drwxr-xr-x root/root         0 2012-05-29 01:55 ./usr/share/pyshared/bzrlib/plugins/email/
[22:19] <mgrandi> so its supposed to be in 'email'
[22:19] <mgrandi> can you paste the entire stack trace?
[22:19] <mortrca> Sorry, you'll have to give me directions.
[22:20] <mgrandi> so how are you getting the error?
[22:20] <mgrandi> you install and it gives you that error?
[22:20] <mortrca> "bzr plugins" returns an entry "email"
[22:20] <mortrca> No, installation doesn't return any errors
[22:20] <mgrandi> ok
[22:20] <mgrandi> so where do you get key is already registered?
[22:21] <mortrca> It only returns that message when it is doing something that should result in an email getting sent.
[22:21] <mgrandi> ok, can oyu paste your bzr.log to somewhere? its in ~/.bzr.log
[22:23] <mgrandi> like bpaste.net
[22:25] <mortrca> mgrandi: hold on
[22:27] <mortrca> mgrandi: http://bpaste.net/show/64267/
[22:27] <mortrca> I don't know why it is trying to load "upload"
[22:28] <mgrandi> yeah, thats a completely different plugin...
[22:28] <mgrandi> apt says: bzr-upload - Bazaar plugin for uploading to web servers
[22:28] <mortrca> I don't have or want that plugin
[22:29] <mortrca> there isn't a directory in /usr/lib64/python2.6/site-packages/bzrlib/plugins called bzr_upload
[22:29] <mgrandi> "/usr/lib64/python2.6/site-packages/bzrlib/plugins/bzr_upload/__init__.py
[22:29] <mgrandi> does that exist?
[22:29] <mgrandi> it says it does..
[22:29] <jelmer> mortrca: the upload plugin needs to be in a directory called "upload", not "bzr_upload"
[22:30] <mgrandi> why did it get installed to that directory then?
[22:31] <mortrca> I figured it out.
[22:32] <mortrca> I removed the stray bzr_upload plugin
[22:32] <mgrandi> or just rename ot to be upload
[22:32] <mgrandi> to*
[22:32] <mortrca> and after renaming bzr-email to email again (running "setup.py install" changed it back) it isn't throwing any errors.
[22:32] <mgrandi> yay!
[22:32] <mgrandi> how did bzr get installed? why is it naming plugins wrong
[22:33] <mortrca> I installed it from source
[22:34] <mgrandi> well why is the source naming it wrong o.o
[22:35] <mortrca> Is that a rhetorical question?
[22:36] <mgrandi> well, no, i mean it installed the plugins worng and then it didn't work, you think it wouldn't do that
[22:36] <mgrandi> haha
[22:36] <mgrandi> but anyway glad you got it working
[22:36] <mortrca> mgrandi:
[22:36] <mortrca> oops
[22:37] <mortrca> It isn't working
[22:37] <mgrandi> what isnt?
[22:39] <mortrca> mgrandi: I'm getting errors now
[22:39] <mgrandi> what errors
[22:39] <mortrca> I had "post_commit_sender = user@example.com" in branch.conf
[22:40] <mortrca> (with a real address)
[22:41] <mortrca> But when I tried to commit I got: "From: user@example.com: No such file or directoryanch - Stage:Fetching revisio..
[22:41] <mortrca> bzr: ERROR: Server sent an unexpected error: ('error', 'BzrError', 'Failed to send email: exit status 1')"
[22:42] <mgrandi> post the bzr log again, it gives more specific errors =P
[22:42] <mgrandi> thx~
[22:44] <mortrca> mgrandi: http://bpaste.net/show/64271/
[22:47] <mgrandi>         result = self.config.get_user_option('post_commit_mailer')
[22:47] <mgrandi> i think its failing cause you dont have a 'mailer' set up
[22:47] <mgrandi> so its defaulting to 'mail'
[22:49] <mgrandi> so set the program you want to use to mail in the conf file under post_commit_mailer
[22:53] <mortrca> mgrandi: Why wouldn't 'mail' work?
[22:53] <mgrandi> do you have mail installed?
[22:53] <mortrca> Yes
[22:54] <mortrca> and I have successfully sent emails with it
[22:55] <mortrca> mgrandi: I need to go, but if you have any ideas I'll read them when I get back.
[22:57] <mgrandi> i would try seing if invoiking mail manually does it
[22:57] <mgrandi> mail -s "subject" -a "from: john doe" then typing it into stdin
[23:01] <mgrandi> or try setting post_commit_mailer to smtplib
[23:24] <mortrca> mgrandi: What do you mean by "typing it into stdin"?
[23:24] <mgrandi> I would just try setting it to be smtplib, its built into python
[23:24] <mgrandi> The reason its not working is that mail is returning a status code of "1", so its not completing correctly..
[23:26] <mortrca> mgrandi: It worked.
[23:27] <mortrca> I didn't get an error message
[23:27] <mortrca> and I did get an email.
[23:27] <mgrandi> by changing it to use stmplib?
[23:27] <mgrandi> smtplib*
[23:27] <mortrca> yes
[23:27] <mgrandi> yay =)
[23:27] <mortrca> Thank you so much
[23:27] <mgrandi> yeah, i dunno much about mail, but it wasn't working i guess
[23:27] <mortrca> You've been very patient.
[23:27] <mgrandi> happy bzr-ing! =)
[23:27] <mortrca> Thanks