On 07.08.2015 22:44, Johan Ryberg wrote:
> Hi,
>
> I need to have rw for group svnusers for .svn/tmp to be able to let
> different users to check in and commit changes but every time cleanup
> are used only the owner has write permission.
>
> Does anyone know how to let a group to have write permis
On Mon, Aug 10, 2015 at 3:27 AM, Branko Čibej wrote:
> On 07.08.2015 22:44, Johan Ryberg wrote:
>> Hi,
>>
>> I need to have rw for group svnusers for .svn/tmp to be able to let
>> different users to check in and commit changes but every time cleanup
>> are used only the owner has write permission.
hi,
i trying to complie subversion 1.9 with mod_dav_svn support on os x 10.10 and i
get the following error message:
subversion/mod_authz_svn/mod_authz_svn.c:100:8: error: This version of httpd
has a security hole with mod_authz_svn
configure parameters for subversion:
./configure --prefix=/pat
Hi Attilla,
hi,
i trying to complie subversion 1.9 with mod_dav_svn support on os x 10.10 and i
get the following error message:
subversion/mod_authz_svn/mod_authz_svn.c:100:8: error: This version of httpd
has a security hole with mod_authz_svn
configure parameters for subversion:
./configure
>Gesendet: Montag, 10. August 2015 um 17:08 Uhr
>Von: Stefan
>An: users@subversion.apache.org
>Betreff: Re: Subersion 1.9 with httpd 2.4.19 compilation error
>> configure parameters for subversion:
>> ./configure --prefix=/path/to/my/folder/subversion \
>> --with-apxs=/path/to/my/folder/apache/bi
hi,
i saw the entry "reimplement UTF-8 fuzzy conversion using utf8proc (r1511676)"
in the changelog and hoped this would be the fix for
http://subversion.tigris.org/issues/show_bug.cgi?id=2464
but after a quick test it seems to be still broken.
is there any progress on fixig this bug?
thank you
Hi all,
I'm currently trying to implement access to my svn repos using
mod_dav_svn and all my repos have a authz file to define who can
access which paths. I would like to be able to have a listing of all
available repos without the need for any authorization, but instead
only if any path within t
Curious. You've come to the opposite conclusion from what we've deployed at
my company.
We let Subversion limit the listed repositories, and we have a separate
generated list of repositories.
That way, you're not playing with Subversion's access file to try to get it
right. Leave that alone, and
