[gitorious] Remote just hung up

2012-09-14 Thread Selva Kumar
I tried to publish my changes. but it throws this error?? is it just me experiencing this problem??? == /media/Programming/tutorials/git_tut/tutorial$ git push origin master The authenticity of host 'gitorious.org (87

Re: [gitorious] Remote just hung up

2012-09-14 Thread Marius Mårnes Mathiesen
On Fri, Sep 14, 2012 at 12:56 PM, Selva Kumar wrote: > I tried to publish my changes. but it throws this error?? is it just me > experiencing this problem??? > > > == > > /media/Programming/tutorials/git_tut/tutorial$ git push

Re: [gitorious] Remote just hung up

2012-09-14 Thread Selva Kumar
On Friday, September 14, 2012 4:36:01 PM UTC+5:30, Marius Mårnes Mathiesen wrote: > > On Fri, Sep 14, 2012 at 12:56 PM, Selva Kumar > > > wrote: > >> I tried to publish my changes. but it throws this error?? is it just me >> experiencing this problem??? >> >> >> ===

[gitorious] Re: Remote just hung up

2012-09-14 Thread Selva kumar
On Friday, September 14, 2012 4:26:48 PM UTC+5:30, Selva Kumar wrote: > > I tried to publish my changes. but it throws this error?? is it just me > experiencing this problem??? > > > == > > /media/Programming/tutorial

Re: [gitorious] Remote just hung up

2012-09-14 Thread Kevin Cox
On Sep 14, 2012 7:25 AM, "Selva Kumar" wrote: > > > yes I did. i'm able to clone the repo and fetch the repo . i just can't push > It looks like you don't have write permissions. To that repo. You can still login and clone but you can't push. Ask the project owner to add you to the committers

[gitorious] Re: Remote just hung up

2012-09-14 Thread Selva kumar
On Friday, September 14, 2012 6:31:57 PM UTC+5:30, Selva kumar wrote: > > > > On Friday, September 14, 2012 4:26:48 PM UTC+5:30, Selva Kumar wrote: >> >> I tried to publish my changes. but it throws this error?? is it just me >> experiencing this problem??? >> >> >> ==

Re: [gitorious] Gitorious LDAP error

2012-09-14 Thread Chris Reffett
Solved the problem just a bit ago--turns out that I messed up the base_dn field at some point, so it was returning that because the connection wasn't opening or some such. Putting the correct base_dn into authentication.yml fixed the issue. On Thursday, September 13, 2012 5:45:10 AM UTC-4, Mari