[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

authentication error after upgrading client to svn1.8.0-rc2 (accessing a svn1.7.8 server)

From: Klaus Welch <klaus.welch_at_advantest.com>
Date: Fri, 31 May 2013 15:09:32 +0200

Hi svn team!

since many years i'm using subversion and it's a great piece of software. Thanks for all the work!

I've tried svn1.8-rc2 and it does not work as smooth as with all the previous upgrades.

Scenario is the following:
  * server
    * apache
    * authentication: htdigest
    * mod_dav_svn
    * svn 1.7.8
    * about 10 repositories (individually configured using SVNPath)
    * authorization: path-based, one shared svn_authz-file (using [repository*:/path])
  * client
    * svn 1.7.9
    * everything working fine (especially path-based authorisation)

After upgrading the *client* to svn1.8-rc2 a simple
svn info <url> gives the following error:

$>svn info http://domain:port/path
svn: E120190: Error running context: An error occurred during authentication

Playing around with svnauthz validate (server side) says that everything is fine.

I tried the following:
  * use svn17x fetch a wc -> ok
  * print svn info -> ok
  * upgrade the wc using svn180-rc2 -> ok
  * print svn info -> ok
  * svn up -> the same error as with svn info <url>

There saw a new line in svn info output:
Relative URL: ^/path

It seems to me that the svn180-rc2 client sends an url the svn179 server does not understand and rejects.

Is this intended behavior?

If yes, how to share than an authz file between repositories?

I hope this feedback helps to make subversion a tiny little better.

With best regards,

Received on 2013-05-31 15:29:00 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.