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

Crazy svn+ssh commit regression in trunk and 1.5

From: Augie Fackler <durin42_at_gmail.com>
Date: Thu, 7 Feb 2008 22:21:02 -0600

Howdy all,

I noticed recently that I can't commit to my FreeBSD server (passwd
authentication for the users, can log in fine via ssh) with svn 1.5 or
1.6, but 1.4 would work just fine, even from the same working copies
(if the WC was downgraded, naturally). After a lot of downgrading and
testing, I've determined the regression was introduced in r21109. What
happens is this:

r21109 client:
[imladris:~/test-repo/trunk] durin% /opt/experimental/bin/svn ci -m
'Checking to see if commit is fixed.'
svn: Commit failed (details follow):
svn: SASL(-1): generic failure: Unable to find a callback: 16385
[imladris:~/test-repo/trunk] durin%
[02/07/08 10:04PM] 1

trunk HEAD client:
[imladris:~/test-repo/trunk] durin% svn ci -m 'Checking to see if
commit is fixed.' svn: Commit failed (details follow):
svn: Cannot negotiate authentication mechanism
[imladris:~/test-repo/trunk] durin%
[02/07/08 10:09PM] 1

But with OS X's stock 1.4 client (10.5.11, svn, version 1.4.4
(r25188)) the commit works.

I haven't gone diving into the code to figure out what is going on in
the code, that's on the agenda for later. Checkouts and updates work
no matter what version of the svn client is used.

The server is running FreeBSD, and svnserve is 1.4.4 from ports. I
control the server, so I can install random versions of svn on it for
testing if needed.

Can anyone try to reproduce this (1.4 server, 1.5/1.6 client, svn+ssh)
to make sure it's not a bug in my setup somewhere? I'm suspicious it's
my setup, since this doesn't seem like the kind of thing that'd be


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-02-08 05:21:15 CET

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

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