Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 121405 - subversion: svn-over-ssh information not sufficient
Summary: subversion: svn-over-ssh information not sufficient
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Paul de Vrieze (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-03 00:56 UTC by Sebastian Bergmann (RETIRED)
Modified: 2006-02-03 01:37 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Bergmann (RETIRED) gentoo-dev 2006-02-03 00:56:05 UTC
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.
Comment 1 Paul de Vrieze (RETIRED) gentoo-dev 2006-02-03 01:24:12 UTC
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.
Comment 2 Sebastian Bergmann (RETIRED) gentoo-dev 2006-02-03 01:37:33 UTC
Sorry for bothering, a bad known_hosts file was the reason.