Apple

Hi,

Using the Collab libraries seemed to work. There was still one last thing I had to do though in order for it to work. I had to make sure that the /usr/lib/sasl2 was a symlink/copy of /opt/subversion/lib/sasl2. That's when the commits started working, however, it's still not 100%. For example, if I browse repositories from within Xcode I can create directories but if I try and remove that same directory Xcode crashes.

I've since realized that I don't really need subversion 1.5.x support. I was only trying to get it to work because I though 1.5.x was needed in order to work with the remote repository. Turns out the issue was the fact that my code was checked out with an external 1.5.x client. When I tried to hookup SCM to that project it complained that I wasn't using the right version of Subversion (since it was checked out with a 1.5.x client). Checking the code out with Xcode instead of the external client allows me to work with my code as usual.

Thanks for all the help, at least if I ever really need 1.5.x support I'll know what to do.

Cheers,

Rom

On Wed, Sep 17, 2008 at 8:03 PM, Russell Finn <email@hidden> wrote:

On Wed, Sep 17, 2008 at 7:24 AM, Romulo Velasquez
<email@hidden> wrote:
> I'm having the same problem as some other poeple with Xcode 3.x and
> Subersion 1.5.0. ...

> I read on another site the the macports version of the subversion client had
> a problem like this as well and fixed it according to these instructions:
>
> http://pjkix.com/journal/2008/06/24/macports-subversion-15-ssh-sasl/

You might try the Collabnet universal binary builds, which as of
1.5.1-2 have SASL compiled directly in. (1.5.2 was released today.)

http://www.collab.net/downloads/community/

Disclaimer: I haven't downloaded 1.5.2 yet, and I also haven't seen
the problem you report so I don't know whether it will fix it.

-- Russell