Crazy svn+ssh commit regression in trunk and 1.5

[Augie Fackler-3]

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  
missed.

Thanks!
Augie


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[David Glasser-4]

On Feb 7, 2008 8:21 PM, Augie Fackler <durin42@...> wrote:

> 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
> missed.

Is SASL enabled in svnserve.conf?

--dave



--
David Glasser | glasser@... | http://www.davidglasser.net/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Augie Fackler-3]

On Feb 7, 2008, at 10:25 PM, David Glasser wrote:

> On Feb 7, 2008 8:21 PM, Augie Fackler <durin42@...> wrote:
>> 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
>> missed.
>
> Is SASL enabled in svnserve.conf?

Nope - it's the default svnserve.conf in a freshly created repository.  
That said, all repositories on that machine fail with the same error.

>
>
> --dave
>
>
>
> --
> David Glasser | glasser@... | http://
> www.davidglasser.net/


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Augie Fackler-3]

On Feb 7, 2008, at 10:31 PM, Augie Fackler wrote:

>
> On Feb 7, 2008, at 10:25 PM, David Glasser wrote:
>
>> On Feb 7, 2008 8:21 PM, Augie Fackler <durin42@...> wrote:
>>> 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
>>> missed.
>>
>> Is SASL enabled in svnserve.conf?
>
> Nope - it's the default svnserve.conf in a freshly created  
> repository. That said, all repositories on that machine fail with  
> the same error.

I just did an install of FreeBSD 6.3 release into a virtual machine so  
there are no configs of mine present. I installed subversion 1.4.4  
from ports and get the same errors with 1.5/trunk, and the same lack  
of errors with 1.4. The repo was freshly created with svnadmin create  
with no changes to the configs from the defaults.
Also tested against a Dreamhost Linux server, and got the same thing.  
They are running svn 1.4.2, but other than the server version change  
and the OS change everything was the same.

I'll start digging on this soon.

Peace,
Augie


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[David Glasser-4]

On Feb 8, 2008 7:46 AM, Augie Fackler <durin42@...> wrote:

>
>
> On Feb 7, 2008, at 10:31 PM, Augie Fackler wrote:
>
> >
> > On Feb 7, 2008, at 10:25 PM, David Glasser wrote:
> >
> >> On Feb 7, 2008 8:21 PM, Augie Fackler <durin42@...> wrote:
> >>> 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
> >>> missed.
> >>
> >> Is SASL enabled in svnserve.conf?
> >
> > Nope - it's the default svnserve.conf in a freshly created
> > repository. That said, all repositories on that machine fail with
> > the same error.
>
> I just did an install of FreeBSD 6.3 release into a virtual machine so
> there are no configs of mine present. I installed subversion 1.4.4
> from ports and get the same errors with 1.5/trunk, and the same lack
> of errors with 1.4. The repo was freshly created with svnadmin create
> with no changes to the configs from the defaults.
> Also tested against a Dreamhost Linux server, and got the same thing.
> They are running svn 1.4.2, but other than the server version change
> and the OS change everything was the same.

So it seems like the client is trying to use SASL even though it's not
necessary for the server?

--dave


--
David Glasser | glasser@... | http://www.davidglasser.net/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Bernd Rinn-2]

Hi Augie,

Just gave it a shot: compiled r29250 of branch 1.5.x on MacOSX and
haven't been able to reproduce the problem.

Client: MacOSX 10.4.11
Server: openSUSE 10.3 (with svn 1.4.4)

***Server:***

~/tmp $ svn --version
svn, version 1.4.4 (r25188)
   compiled Sep 23 2007, 14:00:03

Copyright (C) 2000-2006 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).

The following repository access (RA) modules are available:

* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.
  - handles 'http' scheme
  - handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme

~/tmp $ svnadmin create repos

***Client:***

~/tmp/svn_test $ svn --version
svn, version 1.5.0 (dev build)
   compiled Feb  9 2008, 17:37:24

Copyright (C) 2000-2008 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).

The following repository access (RA) modules are available:

* ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
  - handles 'http' scheme
  - handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme

~/tmp/svn_test $ svn co svn+ssh://tux/home/bernd/tmp/repos
Checked out revision 0.
~/tmp/svn_test $ cd repos/
~/tmp/svn_test/repos $ touch test
~/tmp/svn_test/repos $ svn add test
A         test
~/tmp/svn_test/repos $ svn ci -m "commit test" test
Adding         test
Transmitting file data .
Committed revision 1.


Best,
Bernd

On 7 Feb 2008, Augie Fackler wrote:

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
missed.

Thanks!
Augie

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Mark Phippard-3]

On Feb 9, 2008 12:09 PM, Bernd Rinn <rbernd@...> wrote:
> Just gave it a shot: compiled r29250 of branch 1.5.x on MacOSX and
> haven't been able to reproduce the problem.

I am not sure how to check after the fact, but did you build the
client --with-sasl?

It seems like it might be a SASL-related problem.

--
Thanks

Mark Phippard
http://markphip.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Hyrum K. Wright-3]

Mark Phippard wrote:
> On Feb 9, 2008 12:09 PM, Bernd Rinn <rbernd@...> wrote:
>> Just gave it a shot: compiled r29250 of branch 1.5.x on MacOSX and
>> haven't been able to reproduce the problem.
>
> I am not sure how to check after the fact, but did you build the
> client --with-sasl?

Looking at config.log will show the ./configure command used.

> It seems like it might be a SASL-related problem.

[Augie Fackler-3]

On Feb 9, 2008, at 12:48 PM, Hyrum K. Wright wrote:

> Mark Phippard wrote:
>> On Feb 9, 2008 12:09 PM, Bernd Rinn <rbernd@...> wrote:
>>> Just gave it a shot: compiled r29250 of branch 1.5.x on MacOSX and
>>> haven't been able to reproduce the problem.
>>
>> I am not sure how to check after the fact, but did you build the
>> client --with-sasl?
>
> Looking at config.log will show the ./configure command used.
>
>> It seems like it might be a SASL-related problem.
>

Yeah, it does seem that way. 10.5 does ship a copy of libsasl, which I  
don't think 10.4 had. Maybe that's causing the issue?

I'd diagnose more tonight, but I'm unable to get reliable internet  
access as my new apartment doesn't get DSL until Tuesday...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Bernd Rinn-2]

Hi Augie, Mark, Hyrum,

I was configuring subversion with

./configure --with-sasl=/opt/local

In /opt/local, I have installed cyrus-sasl 2.1.21 from MacPorts for MacOS 10.4.

I don't have any MacOS 10.5 system available right now, so I won't be
able to try on 10.5.

Best,
Bernd

On Feb 11, 2008 3:59 AM, Augie Fackler <durin42@...> wrote:

>
>
> On Feb 9, 2008, at 12:48 PM, Hyrum K. Wright wrote:
>
> > Mark Phippard wrote:
> >> On Feb 9, 2008 12:09 PM, Bernd Rinn <rbernd@...> wrote:
> >>> Just gave it a shot: compiled r29250 of branch 1.5.x on MacOSX and
> >>> haven't been able to reproduce the problem.
> >>
> >> I am not sure how to check after the fact, but did you build the
> >> client --with-sasl?
> >
> > Looking at config.log will show the ./configure command used.
> >
> >> It seems like it might be a SASL-related problem.
> >
>
> Yeah, it does seem that way. 10.5 does ship a copy of libsasl, which I
> don't think 10.4 had. Maybe that's causing the issue?
>
> I'd diagnose more tonight, but I'm unable to get reliable internet
> access as my new apartment doesn't get DSL until Tuesday...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Augie Fackler-3]

On Feb 11, 2008, at 2:15 AM, Bernd Rinn wrote:

> Hi Augie, Mark, Hyrum,
>
> I was configuring subversion with
>
> ./configure --with-sasl=/opt/local
>
> In /opt/local, I have installed cyrus-sasl 2.1.21 from MacPorts for  
> MacOS 10.4.

Hm. I didn't use the --with-sasl flag. Maybe try again without sasl  
turned on?

>
>
> I don't have any MacOS 10.5 system available right now, so I won't be
> able to try on 10.5.
>
> Best,
> Bernd
>
> On Feb 11, 2008 3:59 AM, Augie Fackler <durin42@...> wrote:
>>
>>
>> On Feb 9, 2008, at 12:48 PM, Hyrum K. Wright wrote:
>>
>>> Mark Phippard wrote:
>>>> On Feb 9, 2008 12:09 PM, Bernd Rinn <rbernd@...> wrote:
>>>>> Just gave it a shot: compiled r29250 of branch 1.5.x on MacOSX and
>>>>> haven't been able to reproduce the problem.
>>>>
>>>> I am not sure how to check after the fact, but did you build the
>>>> client --with-sasl?
>>>
>>> Looking at config.log will show the ./configure command used.
>>>
>>>> It seems like it might be a SASL-related problem.
>>>
>>
>> Yeah, it does seem that way. 10.5 does ship a copy of libsasl,  
>> which I
>> don't think 10.4 had. Maybe that's causing the issue?
>>
>> I'd diagnose more tonight, but I'm unable to get reliable internet
>> access as my new apartment doesn't get DSL until Tuesday...
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Bernd Rinn-2]

Hi Augie,

Already tried this. I don't see any problems without sasl neither.

Bernd

On Feb 11, 2008 2:26 PM, Augie Fackler <durin42@...> wrote:

>
> On Feb 11, 2008, at 2:15 AM, Bernd Rinn wrote:
>
> > Hi Augie, Mark, Hyrum,
> >
> > I was configuring subversion with
> >
> > ./configure --with-sasl=/opt/local
> >
> > In /opt/local, I have installed cyrus-sasl 2.1.21 from MacPorts for
> > MacOS 10.4.
>
> Hm. I didn't use the --with-sasl flag. Maybe try again without sasl
> turned on?
>
>
> >
> >
> > I don't have any MacOS 10.5 system available right now, so I won't be
> > able to try on 10.5.
> >
> > Best,
> > Bernd
> >
> > On Feb 11, 2008 3:59 AM, Augie Fackler <durin42@...> wrote:
> >>
> >>
> >> On Feb 9, 2008, at 12:48 PM, Hyrum K. Wright wrote:
> >>
> >>> Mark Phippard wrote:
> >>>> On Feb 9, 2008 12:09 PM, Bernd Rinn <rbernd@...> wrote:
> >>>>> Just gave it a shot: compiled r29250 of branch 1.5.x on MacOSX and
> >>>>> haven't been able to reproduce the problem.
> >>>>
> >>>> I am not sure how to check after the fact, but did you build the
> >>>> client --with-sasl?
> >>>
> >>> Looking at config.log will show the ./configure command used.
> >>>
> >>>> It seems like it might be a SASL-related problem.
> >>>
> >>
> >> Yeah, it does seem that way. 10.5 does ship a copy of libsasl,
> >> which I
> >> don't think 10.4 had. Maybe that's causing the issue?
> >>
> >> I'd diagnose more tonight, but I'm unable to get reliable internet
> >> access as my new apartment doesn't get DSL until Tuesday...
> >>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Augie Fackler-3]

Ok, just tested again. Turns out it's only broken if you *don't* pass  
--without-sasl on 10.5 - maybe the OS X copy of cyrus is behaving  
poorly?

On Feb 11, 2008, at 12:14 PM, Bernd Rinn wrote:

> Hi Augie,
>
> Already tried this. I don't see any problems without sasl neither.
>
> Bernd
>
> On Feb 11, 2008 2:26 PM, Augie Fackler <durin42@...> wrote:
>>
>> On Feb 11, 2008, at 2:15 AM, Bernd Rinn wrote:
>>
>>> Hi Augie, Mark, Hyrum,
>>>
>>> I was configuring subversion with
>>>
>>> ./configure --with-sasl=/opt/local
>>>
>>> In /opt/local, I have installed cyrus-sasl 2.1.21 from MacPorts for
>>> MacOS 10.4.
>>
>> Hm. I didn't use the --with-sasl flag. Maybe try again without sasl
>> turned on?
>>
>>
>>>
>>>
>>> I don't have any MacOS 10.5 system available right now, so I won't  
>>> be
>>> able to try on 10.5.
>>>
>>> Best,
>>> Bernd
>>>
>>> On Feb 11, 2008 3:59 AM, Augie Fackler <durin42@...> wrote:
>>>>
>>>>
>>>> On Feb 9, 2008, at 12:48 PM, Hyrum K. Wright wrote:
>>>>
>>>>> Mark Phippard wrote:
>>>>>> On Feb 9, 2008 12:09 PM, Bernd Rinn <rbernd@...> wrote:
>>>>>>> Just gave it a shot: compiled r29250 of branch 1.5.x on MacOSX  
>>>>>>> and
>>>>>>> haven't been able to reproduce the problem.
>>>>>>
>>>>>> I am not sure how to check after the fact, but did you build the
>>>>>> client --with-sasl?
>>>>>
>>>>> Looking at config.log will show the ./configure command used.
>>>>>
>>>>>> It seems like it might be a SASL-related problem.
>>>>>
>>>>
>>>> Yeah, it does seem that way. 10.5 does ship a copy of libsasl,
>>>> which I
>>>> don't think 10.4 had. Maybe that's causing the issue?
>>>>
>>>> I'd diagnose more tonight, but I'm unable to get reliable internet
>>>> access as my new apartment doesn't get DSL until Tuesday...
>>>>
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...