You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Todd A. Jacobs" <no...@codegnome.org> on 2004/02/02 01:45:32 UTC
Problem with svn+ssh
I get the following error when using the svn+ssh method of access:
svn list svn+ssh://gateway/home/subversion/test bash
svn: Couldn't find a repository
svn: No repository found in 'svn+ssh://gateway/home/subversion/test'
svn: Unsupported repository version
svn: Expected version '2' of repository; found no version at all; is
'/home/subversion/test' a valid repository path?
svn: Permission denied
svn: svn_io_file_open: can't open '/home/subversion/test/format'
All repository files are owned by the "subversion" user. The repository
is valid, and can be accessed on gateway using a path instead of a URL.
However, the remote system can't seem to gain access. What's the best
way to fix/debug this?
--
Todd's "Customer Disservice Hall of Shame" currently contains:
- Charter Communications: Mislead their customers about service
levels, block normal Internet connectivity, and exhibit excessive
downtime.
- AT&T: Honoring the "checks" they send out to entice you to switch
long-distance providers is apparently optional.
- eFax: Receive (not send) 20 pages of *unsolicited* faxes, and lose
your account.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Problem with svn+ssh
Posted by "Todd A. Jacobs" <no...@codegnome.org>.
On Sun, 1 Feb 2004, Todd A. Jacobs wrote:
> All repository files are owned by the "subversion" user. The repository
> is valid, and can be accessed on gateway using a path instead of a URL.
Actually, this only works as root. For some reason, it fails with other
users, even if they also belong to the same group as subversion. So it's
obviously a permissions problem of some kind, but I'm not sure how to fix
it.
--
Todd's "Customer Disservice Hall of Shame" currently contains:
- Charter Communications: Mislead their customers about service
levels, block normal Internet connectivity, and exhibit excessive
downtime.
- AT&T: Honoring the "checks" they send out to entice you to switch
long-distance providers is apparently optional.
- eFax: Receive (not send) 20 pages of *unsolicited* faxes, and lose
your account.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Problem with svn+ssh
Posted by "Todd A. Jacobs" <no...@codegnome.org>.
On Sun, 1 Feb 2004, Ben Collins-Sussman wrote:
> authenticated to ssh as yourself.) So unless you're authenticating to
> ssh as user 'subversion', of course your 'svnserve' process doesn't have
> read-write access to the db files.
The problem in this case turned out to be the lack of o+rx permissions on
the subversion repository. Apparently, even though I had group read/write
permissions on all the database files, I needed o+rx on the parent
directory in order to for svnserve to work properly. I'm still not 100%
sure why that is so, but it seems to have solved issue for me.
> Have you read the 'svnserve' documentation in chapter 6 of the book?
> It explains this stuff in detail.
It could use a bit more detail. Overall, the documentation is quite good,
although a few more successful recipes for non-WebDAV configurations would
be very helpful. Granted, there are some subtle interactions, but a
known-good "test" configuration with listed permissions and so forth would
have saved me quite a bit of trial and error. :)
--
Todd's "Customer Disservice Hall of Shame" currently contains:
- Charter Communications: Mislead their customers about service
levels, block normal Internet connectivity, and exhibit excessive
downtime.
- AT&T: Honoring the "checks" they send out to entice you to switch
long-distance providers is apparently optional.
- eFax: Receive (not send) 20 pages of *unsolicited* faxes, and lose
your account.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Problem with svn+ssh
Posted by Ben Collins-Sussman <su...@collab.net>.
On Sun, 2004-02-01 at 19:45, Todd A. Jacobs wrote:
> svn: Permission denied
> svn: svn_io_file_open: can't open '/home/subversion/test/format'
>
> All repository files are owned by the "subversion" user. The repository
> is valid, and can be accessed on gateway using a path instead of a URL.
> However, the remote system can't seem to gain access. What's the best
> way to fix/debug this?
By using svn+ssh://, you're launching a temporary private 'svnserve'
process on the remotehost running as *you* (assuming that you've
authenticated to ssh as yourself.) So unless you're authenticating to
ssh as user 'subversion', of course your 'svnserve' process doesn't have
read-write access to the db files.
Have you read the 'svnserve' documentation in chapter 6 of the book? It
explains this stuff in detail.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org