Issue 1592 in reviewboard: Unable to add a new subversion repository
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 1592 by Phil.Orwig: Unable to add a new subversion repository http://code.google.com/p/reviewboard/issues/detail?id=1592 *NOTE: Do not post confidential information in this bug report.* What version are you running? 1.5 beta 1 What's the URL of the page containing the problem? /admin/db/scmtools/repository/add/ What steps will reproduce the problem? 1. Leave the hosting service as Custom 2. Select Subversion as the repository type. 3. Set the path to svn+ssh://usern...@some.valid.hostname/suffix What is the expected output? What do you see instead? Expect to see the repository added; instead see a (-2, 'Name or service not known') error (looks like a socket.gaierror. What operating system are you using? What browser? CentOS 5 in an OpenVZ container; Google Chrome on OS X for the browser. Please provide any additional information below. Doing some additional debugging, I notice that the hostname that Reviewboard attempts to resolve includes the username (i.e. usern...@some.valid.hostname). We are using pre-shared keys for repository access, if it makes any difference. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-iss...@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 1592 in reviewboard: Unable to add a new subversion repository
Comment #3 on issue 1592 by Phil.Orwig: Unable to add a new subversion repository http://code.google.com/p/reviewboard/issues/detail?id=1592 Correction -- it isn't the same error, it just doesn't find the repository. Looking at the SSH server, the username given in the configuration isn't being used to connect. Normally, I'd route around this by specifying a User entry in the .ssh/config for the Host, but I have multiple repositories accessible to different users on this host, which will prevent this from working. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-iss...@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.