subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Phippard <markp...@gmail.com>
Subject Re: why cannot commit via http:// but can svn://
Date Tue, 10 Feb 2015 18:44:41 GMT
On Tue, Feb 10, 2015 at 1:39 PM, James <oldyoungguy88@yahoo.com> wrote:

> I have a SVN machine in my network. I can do anything I want via svn://. I
> just setup the http:// access and it seems working until I found I cannot
> commit my new file. The error message is :
>
> $ svn add scripts
> A         scripts
> A         scripts/svnbackup.sh
> [user1@dev2 Docs]$ svn commit -m "add svnbackup.sh file"
> Authentication realm: <http://146.115.74.4:80> Subversion User
> Authentication
> Password for 'user1': ******
>
> svn: E000013: Commit failed (details follow):
> svn: E000013: Can't open file '/home/svn/Docs/db/txn-current-lock':
> Permission denied
>
> I went to the svn server and found all folders and files belong to svn
> group which the user1 is one the members. the svn group has rw permission
> there. In order to narrow down the issue, I renamed my working copy and
> checked out the same repository with svn:// connection and I found I can do
> commit without any issue.
>
> It indicates the issue is not in the svn server but the error reported is
> telling me the svn server refused the write. So I am confused.
>
>
The user you authenticate with does not matter.  This is an OS-level
permission issue. Your Apache server is probably running as an "apache" or
"httpd" user account that does not have RW access to your repository.
Either add the Group directive to Apache so that it runs with your svn
group or change your repository files so that they are writable by the
Apache process.

Likewise, the svnserve process on the server determines what it can RW.  In
your case, it is probably running with the svn group which is why it works.

-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

Mime
View raw message