On Thu, 22 Dec 2011 22:58:44 +0100
Pierre Berthier wrote:
> Hi
>
> after upgrading a SVN server from 1.6 to 1.7.2 (r1207936), I am
> getting this error message when committing:
>
> svn: E175002: Commit failed (details follow):
> svn: E175002: Server sent unexpected return value (500 Internal Se
Pierre Berthier writes:
>
> DAV svn
> SVNParentPath /srv/svn/repos/
> SVNListParentPath on
> AuthzSVNAccessFile /etc/apache2/svnaccess.conf
> AuthzSVNAnonymous Off
> AuthzSVNAuthoritative On
> SVNPathAuthz Off
>
> AuthType Basic
> AuthNam
Hi, all :
Today i run checkout command via Windows svn client from the SVN Server,
it display these error message:
xxx
xxx
Error : REPORT of xxx: could not read chunk size: connection
Error : was closed by server .
Then i run the following command to see the error log:
root@test ~: tailf /v
Pierre Berthier wrote on Thu, Jan 05, 2012 at 10:12:56 +0100:
> I have now reduced my configuration to two variations, the following
> works fine:
>
(Thanks for the additional details, it's _much_ easier to respond
usefully given them.)
> I am now wondering if that should be considered a bug at
Not sure if this is even possible but subversion place the ".subversion"
directory based on your unix environment variable called $HOME. Well, on
one server, we have specifically specify $HOME to a location that could be
deleted in the future. If that's the case, then there goes the
".subversion"
On Jan 5, 2012, at 11:49, Phil wrote:
> Not sure if this is even possible but subversion place the ".subversion"
> directory based on your unix environment variable called $HOME. Well, on one
> server, we have specifically specify $HOME to a location that could be
> deleted in the future. If
On Thu, Jan 5, 2012 at 10:49 AM, Phil wrote:
> Not sure if this is even possible but subversion place the ".subversion"
> directory based on your unix environment variable called $HOME. Well, on
> one server, we have specifically specify $HOME to a location that could be
> deleted in the future.
Thank you Ed and Ryan. You provided me some ideas around this topic. I
appreciated it.
On Thu, Jan 5, 2012 at 3:06 PM, Ed wrote:
> On Thu, Jan 5, 2012 at 10:49 AM, Phil wrote:
> > Not sure if this is even possible but subversion place the ".subversion"
> > directory based on your unix enviro
Hi there,
I'm wondering if my desired setup is possible:
1. Using svn+ssh
2. Using pam_ldap to handle SSH access
3. Using authz-db to handle ACL (against LDAP accounts)
I'm running into a problem with #3. My current test setup is as follows:
svnserve.conf:
-
[general]
authz-
You might try this to sync your authz file to an ldap group, it will write
in the entries for you, nice way to avoid issues with syntax perhaps?
http://www.thoughtspark.org/node/26
Never used it myself, meant to try it, but I've heard good things.
-Pat
On Thu, Jan 5, 2012 at 3:07 PM, Owen Loy
10 matches
Mail list logo