any update on this?
On Saturday, September 27, 2014 4:23:29 AM UTC+5:30, neel roy wrote:
Thanks for the answer. Few points:
- I used the same creds when checking out with plain svn command line tool
and it worked perfectly fine. Why should reviewboard fail with it?
- I don't see any log
okay, figured it out. Even though svn repository does not require password,
it needs to store no password condition in some file under
.subversion/auth/svn.simple it seems. If you are doing this from command
line, it will ask whether you want to store password in unencrypted format.
If you say
In general, we've found pysvn to be somewhat more reliable than subvertpy,
so I'd suggest switching back. That error suggests to me that the
credentials listed in the repository admin were incorrect.
-David
On Fri, Sep 26, 2014 at 8:41 AM, neel roy neelsm...@rediffmail.com wrote:
Hi,
I am
Thanks for the answer. Few points:
- I used the same creds when checking out with plain svn command line tool
and it worked perfectly fine. Why should reviewboard fail with it?
- I don't see any log about what command is being launched and from where
from within the code. Is there a way to get
Yeah, so I fixed this. For anyone concerned, this was the solution:
- Instructions I had been following on an internal wiki for setting up
passwordless SSH were a bit out-of-date. They stated that copying your
public key to .ssh/authorized_keys2 on the server would be sufficient,
but this method
Note, this also fails on debian, which is supposedly your default
install. I get to the same place (once again obfuscated):
- Install apache with mod-wsgi
- Install mysql
- Install dependencies
- Install reviewboard
- Set up reviewboard
- Go to admin
- Go to repositories
- Go to Add repository
-
I haven't as yet been able to hunt this down, but it does appear to be
a SSH communications issue. I am able to access the server in question
from the console using the apache user, and the logs state that
initial attempts to authenticate are successful - there is just one
final missing step that
Additional info:
- This install is on CentOS
- using Apache
- The ssh login is failing in paramiko.
- When I attempt to save my repository info, the only error I receive
is (13, 'Permission denied').
- I traced the call into paramiko's code, at sock.connect(), but
cannot figure out exactly what's
