| Summary: | subversion: svn-over-ssh information not sufficient | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sebastian Bergmann (RETIRED) <sebastian> |
| Component: | [OLD] Development | Assignee: | Paul de Vrieze (RETIRED) <pauldv> |
| Status: | RESOLVED INVALID | ||
| Severity: | enhancement | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
What kind of error message do you get? You might want to also take a look at the documentation given at http://subversion.tigris.org. And I assume that your repository does live at /var/svn/repos/ You don't need to start the svnserve daemon as ssh is performing the network connectivity. svnserve is started in a tunnel mode for each use. Sorry for bothering, a bad known_hosts file was the reason. |
The Subversion ebuild lists - svn over ssh: 1. Fix the repository permissions: groupadd svnusers chown -R root:svnusers /var/svn/repos/ chmod -R g-w /var/svn/repos chmod -R g+rw /var/svn/repos/db chmod -R g+rw /var/svn/repos/locks 2. create an svnserve wrapper in /usr/local/bin to set the umask you want, for example: #!/bin/bash umask 002 exec /usr/bin/svnserve "$@" as the steps for setting up svn-over-ssh. I did the above and am somewhat lost, as I am not sure whether or not I need to start /etc/init.d/svnserver (I think not). In either case I cannot connect via ssh to svnserve. The use I am trying to connect with is in the svnusers group.