It reports which command-line tools are installed to help you avoid working 
copy format conflicts, but AFAIK, Versions always uses its bundled version of 
the SVn tools.
 - Quinn

On Nov 27, 2009, at 6:44 PM, nalundgaard wrote:

> I think you can just get svn 1.6.6 via CollabNet binaries for OS X
> here:
> 
> http://www.open.collab.net/downloads/community/
> 
> They install into /opt/subversion/bin/, so you can delete them if you
> don't like them. It looks to me like Versions picks them up after you
> install them, but the UI does a poor job of making it clear that it's
> using them: the radio button selector for 1.4 : 1.5 : 1.6 specifically
> says 1.6.5, and then below it says "SVN 1.6.6 command-line are
> installed in '/opt/subversion/bin/svn'. Versions and your command-line
> tools are compatible." Slightly confusing, but I imagine it's using
> the 1.6.6 when you do this.
> 
> I installed them about 15 minutes ago, and so far no crashes
> (previously was doing it often), though it hasn't been long enough for
> me to say for sure.
> 
> --Nicholas
> 
> On Nov 27, 6:38 am, tim <timkna...@hotmail.com> wrote:
>> Hey Dirk,
>> thanks for the update, I'm looking forward to that update!
>> 
>> Cheers,
>> tim
>> 
>> On Nov 27, 11:53 am, Dirk Stoop <d...@madebysofa.com> wrote:
>> 
>>> Hey Tim,
>> 
>>> I just noticed that this issue has been fixed in Subversion 1.6.6.
>> 
>>> From the release notes:
>>> * fix "libsvn_ra_svn/marshal.c assertion failed (opt || cstr)" (issue
>>> #3485)
>> 
>>> Or if you're interested in more 
>>> details:http://subversion.tigris.org/issues/show_bug.cgi?id=3485
>> 
>>> We'll try to replace SVN 1.6.5 with SVN 1.6.6 in the next release of
>>> Versions, so you'll be able to use SVN 1.6 in Versions again.
>> 
>>> Cheers,
>>> - Dirk
>> 
>>> the Versions team
>> 
>>> On Nov 24, 5:31 pm, tim <timkna...@hotmail.com> wrote:
>> 
>>>> Versions is working nicely again, thanks for the help!
>> 
>>>> On Nov 24, 1:01 pm, Quinn Taylor <quinntay...@mac.com> wrote:
>> 
>>>>> Only in the sense that they will not be readable by an earlier SVN 
>>>>> client. (It won't actually modify the working copy, it's a version 
>>>>> compatibility issue.)
>>>>>  - Quinn
>> 
>>>>> On Nov 24, 2009, at 12:24 AM, tim wrote:
>> 
>>>>>> but wait... if I go back to svn 1.5.x, won't this mess with my
>>>>>> existing working copies?
>> 
>>>>>> On Nov 24, 9:17 am, tim <timkna...@hotmail.com> wrote:
>>>>>>> yep, I'm on svn 1.6.5!
>> 
>>>>>>> I'll try reverting to 1.5 and see what's happening then...
>> 
>>>>>>> thanks!
>> 
>>>>>>> On Nov 23, 1:54 pm, oltbaba <oltb...@googlemail.com> wrote:
>> 
>>>>>>>> Which Subversion Version are you using?
>>>>>>>> In our Team (3 People) two persons can use Versions (running
>>>>>>>> Subversion v1.4.x & v1.5.x)
>> 
>>>>>>>> Our new team member runs subversion v1.6.5, with this subversion the
>>>>>>>> Versions app crashes on start-up.
>>>>>>>> Anybody experiences the same problems with newer subversion version (=
>>>>>>>> 1.6.5)?
>> 
>>>>>  smime.p7s
>>>>> 4KViewDownload
> 
> --
> 
> You received this message because you are subscribed to the Google Groups 
> "Versions" group.
> To post to this group, send email to versi...@googlegroups.com.
> To unsubscribe from this group, send email to 
> versions+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/versions?hl=en.
> 
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to