Db based configuration for per-directory access control

Hi all Is there any way to configure subversion to do per-directory access control via database not config file? I have googled a lot, and all found are telling how to configure apache login problem, not svn repository access control.

Re: repo structure change and external definitons

>> Von: Ryan Schmidt [mailto:subversion-20...@ryandesign.com] >> Gesendet: Wednesday, November 24, 2010 12:52 PM >> An: Schroeder, Hartmut >> Cc: users@subversion.apache.org >> Betreff: Re: repo structure change and external definitons >> >> On Nov 24, 2010, at 05:00, Schroeder, Hartmut wrote: >>

Re: Apache Subversion 1.6.15 Released

On Wed, Nov 24, 2010 at 05:36:01PM -0500, Nico Kadel-Garcia wrote: > On Wed, Nov 24, 2010 at 11:15 AM, Hyrum Wright wrote: > > I'm happy to announce Apache Subversion 1.6.15.  This release contains > > several bug fixes, including two which can cause client-initiated > > crashes on the server.  We

Re: Apache Subversion 1.6.15 Released

On Wed, Nov 24, 2010 at 11:15 AM, Hyrum Wright wrote: > I'm happy to announce Apache Subversion 1.6.15.  This release contains > several bug fixes, including two which can cause client-initiated > crashes on the server.  We encourage users to upgrade as soon as Cool. I just built it using the RPM

RE: Find file in repo

Thanks a lot, this solved my problem. Best regards > Date: Tue, 23 Nov 2010 13:06:16 +0100 > From: pi...@kabot.net > To: users@subversion.apache.org; rob_gar_...@hotmail.com > Subject: Re: Find file in repo > > On 23-11-2010 12:49, Gerardo Corro wrote: > > How can I get the path of one file in a

Re: svnsync_test.py fails: wrong version of SQLite library

The documentation on how to use the amalgamation should be clearer. After many false starts, I got it to successfully configure with: ./configure --prefix=/usr/sup/subversion-1.6.13 --with-sqlite=/tmp/sqlite-3.7.3/sqlite3.c I'm mildly surprised that it can't find sqlite3.c if you feed it a

Re: svnsync_test.py fails: wrong version of SQLite library

Michael J. Bauer wrote: I see no SVN version 1.6 RPM in RPMForge. It's the first place I looked before trying to build it by hand. Very strange: (trimmed a little) [kdeu...@lilbro ~]$ yum list |grep subversion subversion.x86_64 1.6.13-0.1.el5.rf installed [kdeu...@lilbro ~]$

Re: svnsync_test.py fails: wrong version of SQLite library

Couldn't hurt. There's no need for the whole log though, a representative sample should be enough... Does it fail in the same way under 'make check' as under './svnsync_tests.py -v'? (You can pass TESTS=subversion/tests/cmdline/svnsync_tests.py to 'make check', by the way.) Michael J. Bauer wro

Re: svnsync_test.py fails: wrong version of SQLite library

I have not tried that method; I'll try it now and report back when 'make check' finishes. MJB On 11/23/2010 9:18 PM, Hyrum K. Wright wrote: On Tue, Nov 23, 2010 at 6:16 PM, Michael J. Bauer wrote: I am attempting to build SVN on a RHEL 5.4 system. There are two versions of SQLite on the sy

Re: svnsync_test.py fails: wrong version of SQLite library

I see no SVN version 1.6 RPM in RPMForge. It's the first place I looked before trying to build it by hand. r...@sunfire60# rpm -i rpmforge-release-0.5.1-1.el5.rf.x86_64.rpm r...@sunfire60# yum list > /tmp/foo r...@sunfire60# grep -i '^svn' /tmp/foo | grep 1.6 r...@sunfire60# grep -i '^subversio

Re: svnsync_test.py fails: wrong version of SQLite library

The only test that failed out of the 71 run by 'make check' was svnsync_test.py. The only things that appeared to fail within that test were svnsync sync. I can send the test log if you like. MJB On 11/24/2010 2:45 AM, Daniel Shahaf wrote: Michael J. Bauer wrote on Tue, Nov 23, 2010 at 19:1

Apache Subversion 1.6.15 Released

I'm happy to announce Apache Subversion 1.6.15. This release contains several bug fixes, including two which can cause client-initiated crashes on the server. We encourage users to upgrade as soon as reasonable. Please note that Subversion 1.6.15 is the next release after Subversion 1.6.13. The

Merge with "--accept theirs-conflict" doesn't work as expected - the result is same as with "--accept theirs-full"

Hello, I am having a problem with "merge --accept theirs-conflict": it seems like it is working like "merge --accept theirs-full". I am trying to get changes from different branch and merge them to my working copy (running this command in my working copy directory /some/thing): "svn me

AW: repo structure change and external definitons

it would be a good idea to update the documentation, first to give a big warning if one moves or deletes an entry and second to recommend externals definitons only with peg revisions. today that is not the case. hartmut -Ursprüngliche Nachricht- Von: Ryan Schmidt [mailto:subversion-20..

Re: repo structure change and external definitons

On Nov 24, 2010, at 05:00, Schroeder, Hartmut wrote: > say, > svn list http://server/repo/trunk/a/b/c > gives: > d/ > in revision 100. > > Then: > svn del http://server/repo/trunk/a/b/c/d > (r101) > > Then, the checkout > svn co -p 100 http://server/repo/trunk/a/b/c/d > won't work, but with th

Re: Should svn allow a merge into a conflicted file?

Hi - I hate to bump this just for the sake of it, but AFAIK an email wasn't sent to the list from this post, maybe because I sent it immediately after registering. cheers, jamie JamieEchlin wrote: > > Should Subversion allow a merge on top of a file that already contains > an unresolved conflic

repo structure change and external definitons

Hi, say, svn list http://server/repo/trunk/a/b/c gives: d/ in revision 100. Then: svn del http://server/repo/trunk/a/b/c/d (r101) Then, the checkout svn co -p 100 http://server/repo/trunk/a/b/c/d won't work, but with the peg revision svn co http://server/repo/trunk/a/b/c/d...@100 it does. All