> -Original Message-
> From: Andy Canfield [mailto:andy.canfi...@pimco.mobi]
> Sent: 29 July 2011 05:14
> To: users@subversion.apache.org
> Subject: SVNParent authz
>
> I am having a problem with AuthzSVNAccessFile.
>
> Consider the case where I have two repositories, R1 and R2 Some user
That's a wonderful thing about computers. Every time I come up with
something that is impossible, I figure out a way to do it.
My current test repository server is named "athol". But I can not look
at "http://athol/svn";; nobody is allowed to see that.
But, as of now, if I point my browser to
Really hard to know what to suggest with so little information.
What version of TortoiseSVN on the client?
>> Its 1.6.x "TortoiseSVN "
What version of SVN on the server? What OS on the server?
>> We are using Visual SVN Server 2.1.3 Enterprise Edition on Windows 2003
Enterprise Edition of Seve
On Jul 28, 2011, at 23:44, Ryan Schmidt wrote:
> On Jul 28, 2011, at 20:27, Andy Canfield wrote:
>> On 07/28/2011 09:48 PM, Geoff Hoffman wrote:
>>> You can then detect http protocol with a rewrite rule and redirect to https
>>> using mod_rewrite in either the vhost container or .htaccess file.
>
On Jul 28, 2011, at 20:27, Andy Canfield wrote:
> On 07/28/2011 09:48 PM, Geoff Hoffman wrote:
>> You can then detect http protocol with a rewrite rule and redirect to https
>> using mod_rewrite in either the vhost container or .htaccess file.
> Where would the .htaccess file be for svn+ssh? Ther
I am having a problem with AuthzSVNAccessFile.
Consider the case where I have two repositories, R1 and R2 Some users
are authorized to examine R1 by going to
http://example.com/svn/R1
Other users are authorized to examine R2 by going to
http://example.com/svn/R2
But everyone should be a
Thank you very much.
On 07/28/2011 09:48 PM, Geoff Hoffman wrote:
On Thu, Jul 28, 2011 at 7:29 AM, Andy Canfield
mailto:andy.canfi...@pimco.mobi>> wrote:
Hold it right there. You're providing password based
repository access
via HTTP, not HTTPS? Please rethink this u
On Thu, Jul 28, 2011 at 10:44 AM, Matthew Beals wrote:
>> That "svn" user can be set to have no valid shell, with its shell set
>> to something like "/sbin/nologin". This is actually quite common for
>> system services to have no valid shell. This is how the "apache" or
>> "www-data" user is usual
With 1.6 I sometimes had to pass the option '--with-expat=builtin' to the
subversion configuration script so the apr-util would be built with the
included expat instead of the system expat. This avoided RPATH problems
that would result in libaprutil picking up libapr from the system instead of
fro
On Jul 28, 2011, at 07:34, Waseem Bokhari wrote:
> Greetings!
>I am facing the following error on Commit in
> Tortoise SVN:-
>
> Pls Guide.
>
>
> Commit failed (details follow):
> Server sent unexpected return value (500 Internal Server Error) in response to
On 7/28/2011 9:29 AM, Andy Canfield wrote:
I was trying to get http, svn, and svn+ssh to work.
Dude. Pick one. Getting all three to play nicely together is
destablilizing.
For me, getting any of the four to work is difficult. Here is the status
of the various protocols, in order by apparent d
On Thu, Jul 28, 2011 at 7:29 AM, Andy Canfield wrote:
> Hold it right there. You're providing password based repository access
>> via HTTP, not HTTPS? Please rethink this unless you *want* the
>> passwords for this repository to be quite insecure and sniffable,
>> especially if you're using norma
> That "svn" user can be set to have no valid shell, with its shell set
> to something like "/sbin/nologin". This is actually quite common for
> system services to have no valid shell. This is how the "apache" or
> "www-data" user is usually set up.
But that would prevent login using ssh, which I d
On 07/27/2011 06:47 PM, Nico Kadel-Garcia wrote:
On Wed, Jul 27, 2011 at 12:06 AM, Andy Canfield
wrote:
I was trying to get http, svn, and svn+ssh to work.
Dude. Pick one. Getting all three to play nicely together is destablilizing.
For me, getting any of the four to work is difficult. Here
On 27/07/11 15:28, Rob Patten wrote:
Noting the Subversion 7.0 Beta2 is released we are attempting to get
ahead start on user request to have Subversion install on our IBM
servers. Our user community requested any near current version at least
but notified they will require version 7.0 for thei
Noting the Subversion 7.0 Beta2 is released we are attempting to get
ahead start on user request to have Subversion install on our IBM
servers. Our user community requested any near current version at least
but notified they will require version 7.0 for their project needs. We
have had difficulty
This appears to be a test bug that manifests itself when the tests are run
with a server and the svnlook binary being tested is not executable on the
server. This is likely to occur if the server has a different machine
architecture or operating system than the subversion code being tested, but
ce
I have had failures of this test with 1.6.15 and 1.6.17 when running "make
check BASE_URL=http://server.domain"; on a client machine that is not the
server. The server is also running the same version of subversion, but it
supports clients with multiple operating systems and I am testing a client
Greetings!
I am facing the following error on Commit in
Tortoise SVN:-
Pls Guide.
Commit failed (details follow):
Server sent unexpected return value (500 Internal Server Error) in response
to
PUT request for
'/svn/nfs-cap-alamthal/!svn/wrk/ae7ebfe8-00e4-1f4b-a
19 matches
Mail list logo
