On Fri, Jun 21, 2013 at 10:35 AM, Camilo Sasuke Tsumanuma
> Hi Dear Subversion Users Forum,
> I compiled subversion 1.8.0 in CentOS 6.4 using
> http://comments.gmane.org/gmane.comp.version-control.subvers ion.user/113594
> as guideline.
Grab the Wandisco RPM's, or my buildable SRPM tools from
https://github.com/nkadel/subversion-1.8.x-srpm. And i've got
buildable libserf-1.2.1 SRPM tools in the adjacent repository, which
you're quite welcome to use.
> I just used my own previous Apache Server configuration of
> Digest Authentication for WebDav SVN but it failed
> like described in Discussion Topic of TortoiseSVN Users Forum
Does it fail with svn+ssh?
Also note that just runing "./comfigure" tries to deduce what is
avaialble in your local build environment, There are a lot of features
it does not mandate, which is why good SRPM's are so handy to build
from for RHEL based systems.
> I cannot update, commit or checkout a working copy because
> I cannot authenticate. The 1.8.0 SVN clients repeatdly asks for
> It seems to be related to serf library at client side and may be HTTPS
> The Server seems to be very OK.
> Because I can Digest authenticate to the 1.8.0 Server using browser like
> Firefox, IE or Chrome and also with TortoiseSVN 1.7.13.
> Can you please help me with this?
> Should I open a new issue?
> Is this a known bug?
> I could find some discussion about serf 1.2.0 blocking 1.8.0 SVN release
> of Digest Authentication. But I could not track if the used 1.2.1 serf
> library in
> 1.8.0 clients really solves the issue, and I don't know if I found a new
> I can Basic authenticate using both 1.7.13 and 1.8.0 clients to
> the same server/repository/HTTPS using alternative URL/Apache <Location>.
> Thank you in advance,
> [Sending same e-mail from e-mail address registered and tigris.org]
Received on 2013-07-03 03:51:33 CEST