BBEdit svn: This client is too old to work with working copy

[Bill Hernandez]

When I try any operation on an existing repository, BBEdit becomes
unhappy...

I just installed SubVersion this weekend, so I am not sure why the
error message ?

Any ideas ?

### Wednesday, April 1, 2009 5:40:13 PM

Retrieving Revision Contents

svn: This client is too old to work with working copy '/Users/roscoe/
workspace/MVC_Project/local_includes/classes/form'; please get a newer
Subversion client

I pulled up the terminal, and checked the svn version

[2009.01.04](05:42PM) -> [roscoe] ~ $ svn --version
svn, version 1.6.0 (r36650)
compiled Mar 31 2009, 01:19:07

Copyright (C) 2000-2009 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.
- with Cyrus SASL authentication
- handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
- handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol
using serf.
- handles 'http' scheme
- handles 'https' scheme

[2009.01.04](05:42PM) -> [roscoe] ~ $

Bill Hernandez
Plano, Texas

[Jonathan Lundell]

On Apr 1, 2009, at 3:46 PM, Bill Hernandez wrote:

>
> When I try any operation on an existing repository, BBEdit becomes
> unhappy...
>
> I just installed SubVersion this weekend, so I am not sure why the
> error message ?
>
> Any ideas ?

I think that BBEdit is using /usr/bin/svn, and if you try /usr/bin/svn
--version you'll maybe see 1.4.4.

[Bill Hernandez]

On Apr 1, 2009, at 5:53 PM, Jonathan Lundell wrote:

> On Apr 1, 2009, at 3:46 PM, Bill Hernandez wrote:
>
>> When I try any operation on an existing repository, BBEdit becomes
>> unhappy...
>>
>> I just installed SubVersion this weekend, so I am not sure why the
>> error message ?
>>
>> Any ideas ?
>
> I think that BBEdit is using /usr/bin/svn, and if you try /usr/bin/svn
> --version you'll maybe see 1.4.4.

Jonathan ,

You were right...

[2009.01.04](06:13PM) -> [roscoe] ~ $ /usr/bin/svn --version
svn, version 1.4.4 (r25188)
compiled Sep 23 2007, 22:32:34

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

This FIXED it for me...

[2009.01.04](06:13PM) -> [roscoe] ~ $ sudo mv /usr/bin/svn /usr/bin/
svn_144
Password:

[2009.01.04](06:14PM) -> [roscoe] ~ $ which svn
/opt/local/bin/svn

[2009.01.04](06:14PM) -> [roscoe] ~ $ sudo ln -s /opt/local/bin/svn /
usr/bin/svn

[2009.01.04](06:15PM) -> [roscoe] ~ $

BBEdit is very happy now, and SVN works...

Thanks again !!!

Bill Hernandez
Plano, Texas

[Patrick Woolsey]

Bill Hernandez <m...@mac-specialist.com> sez:

>When I try any operation on an existing repository, BBEdit becomes
>unhappy...
>
>I just installed SubVersion this weekend, so I am not sure why the
>error message ?
>

[...]

Leopard includes Subversion in the default install:

pwoolsey$ which svn
/usr/bin/svn
pwoolsey$ /usr/bin/svn --version

svn, version 1.4.4 (r25188)
compiled Sep 23 2007, 22:32:34

[...]

so you've probably installed an additional, newer version elsewhere; a
'which svn' will show you which svn executables are available.

You can tell BBEdit to use a copy of the svn tool which isn't in the
default location by setting a tool path override, as described at the end
of Ch. 10 in the PDF manual (Help -> User Manual):

====
CVS/Perforce/Subversion Tool Path Override

If you need to control which cvs, p4, or svn tool BBEdit should use, you
can do so by issuing any or all of the following Terminal commands.

[...]

For Subversion:

defaults write com.barebones.bbedit Subversion:SubversionToolPathOverride
/path/to/svn/binary
====

Regards,

Patrick Woolsey
==
Bare Bones Software, Inc. <http://www.barebones.com>
P.O. Box 1048, Bedford, MA 01730-1048

[Craig Heilman]

This brings up a question for me. I've heard differing recommendations on how to tell the OS which version of an application to use. Bill outlines one method. Another method involves simply changing your path to include /usr/local/bin and/or other "preferred" directories before the standard directories. For example, I have the following in my ~/.bash_profile:

export PATH="/opt/subversion/bin:/usr/local/bin:$PATH"

Which method is "safest" in the face of OS updates and the like?

Note: I'm using the Mac OS Subversion 1.6 binaries downloaded direct from openCollabNet as I just couldn't get the source to compile correctly as in the past (openSSL issues). The default install location is /opt/subversion/bin.

Craig

On Apr 1, 2009, at 6:21 PM, Bill Hernandez wrote:

This FIXED it for me...

[2009.01.04](06:13PM) -> [roscoe] ~ $ sudo mv /usr/bin/svn /usr/bin/
svn_144
Password:

[2009.01.04](06:14PM) -> [roscoe] ~ $ which svn
/opt/local/bin/svn

[2009.01.04](06:14PM) -> [roscoe] ~ $ sudo ln -s /opt/local/bin/svn /
usr/bin/svn

[2009.01.04](06:15PM) -> [roscoe] ~ $

BBEdit is very happy now, and SVN works...

-----------------------------------------------------------------

Craig A. Heilman

Bugaboo Software - Software Engineering & Consulting

http://www.bugsoft.com/

-----------------------------------------------------------------

[Rod Buchanan]

On Apr 2, 2009, at 9:43 AM, Craig Heilman wrote:

> This brings up a question for me. I've heard differing
> recommendations on how to tell the OS which version of an
> application to use. Bill outlines one method. Another method
> involves simply changing your path to include /usr/local/bin and/or
> other "preferred" directories before the standard directories. For
> example, I have the following in my ~/.bash_profile:
>
> export PATH="/opt/subversion/bin:/usr/local/bin:$PATH"
>
> Which method is "safest" in the face of OS updates and the like?

IMO, best method is any that does not touch /bin or /usr/bin. Changes
to those directories (i.e. replacing files with others or links) are
sure to eventually break after an O/S update.

I (personally) would handle it one of two ways:

1) A mechanism in the program if supported (which it sounds like
BBEdit does);
2) Modifying PATH like your example

> On Apr 1, 2009, at 6:21 PM, Bill Hernandez wrote:
>
>> This FIXED it for me...
>>
>> [2009.01.04](06:13PM) -> [roscoe] ~ $ sudo mv /usr/bin/svn /usr/bin/
>> svn_144
>> Password:
>>
>> [2009.01.04](06:14PM) -> [roscoe] ~ $ which svn
>> /opt/local/bin/svn
>>
>> [2009.01.04](06:14PM) -> [roscoe] ~ $ sudo ln -s /opt/local/bin/svn /
>> usr/bin/svn
>>
>> [2009.01.04](06:15PM) -> [roscoe] ~ $
>>
>> BBEdit is very happy now, and SVN works...

--
Rod Buchanan
Kelly Supply / KDSI / ISCO
308 382-8764 x220

"Saying Windows 95 is equal to Macintosh is like finding a potato that
looks like Jesus and believing you've witnessed the second coming."
-- Guy Kawasaki

[Jonathan Lundell]

On Apr 2, 2009, at 7:43 AM, Craig Heilman wrote:

> This brings up a question for me. I've heard differing
> recommendations on how to tell the OS which version of an
> application to use. Bill outlines one method. Another method
> involves simply changing your path to include /usr/local/bin and/or
> other "preferred" directories before the standard directories. For
> example, I have the following in my ~/.bash_profile:
>
> export PATH="/opt/subversion/bin:/usr/local/bin:$PATH"
>
> Which method is "safest" in the face of OS updates and the like?

This depends on what you mean by "safe". If 10.5 installs svn 1.4, you
install 1.5, and 10.6 updates to 1.6, presumably you'd like to revert
to the 10.6 version.

But if 10.5 installs 1.4, you install 1.6, and 10.6 updates to 1.5,
presumably you'd like to keep using 1.6.

There are conventions for where to put updated binaries, depending on
who's going to use them. /usr/local/bin and /opt/local/bin are common
(MacPorts puts svn in the latter). ~/bin can be used if you want to
restrict the binary to your own use. But none of those will be seen by
launchd-launched apps unless you make launchd aware of the change
somehow.

>
> Note: I'm using the Mac OS Subversion 1.6 binaries downloaded direct
> from openCollabNet as I just couldn't get the source to compile
> correctly as in the past (openSSL issues). The default install
> location is /opt/subversion/bin.
>

There's an old technote that appears to still be valid: http://developer.apple.com/qa/qa2001/qa1067.html

The idea would be to set PATH in ~/.MacOSX/environment.plist. I
haven't tried it, though. PATH is tricky, because there will be
exiting entries you want to retain, and I don't know how
environment.plist interacts with that.

[Steve Kalkwarf]

On Apr 2, 2009, at 11:57 AM, Jonathan Lundell wrote:

> The idea would be to set PATH in ~/.MacOSX/environment.plist. I
> haven't tried it, though. PATH is tricky, because there will be
> exiting entries you want to retain, and I don't know how
> environment.plist interacts with that.

It doesn't, and that's the whole problem.

For reasons I never understood, the environment provided to GUI
applications is not the same environment provided to command line
processes.

You use any of the various means to add paths to $PATH for console
sessions, and you use environment.plist to add them to GUI sessions.

Steve

[Bill Hernandez]

On Apr 2, 2009, at 9:43 AM, Craig Heilman wrote:

This brings up a question for me. I've heard differing recommendations on how to tell the OS which version of an application to use. Bill outlines one method. Another method involves simply changing your path to include /usr/local/bin and/or other "preferred" directories before the standard directories. For example, I have the following in my ~/.bash_profile:

export PATH="/opt/subversion/bin:/usr/local/bin:$PATH"

Which method is "safest" in the face of OS updates and the like?

Note: I'm using the Mac OS Subversion 1.6 binaries downloaded direct from openCollabNet as I just couldn't get the source to compile correctly as in the past (openSSL issues). The default install location is /opt/subversion/bin.

Looks like my method, even though it solved my immediate problem is not a good choice.

The version in /usr/bin/svn is pretty old compared to the one I installed via MacPorts, but Rod makes a lot of sense, when he says :

"It is best to avoid messing with /bin and /usr/bin"

In my case I will probably leave it with the soft symlink pointing to /opt/local/bin/svn, and with any luck it won't break anything.

Patrick's message recommends : (I think he meant for this to be all on one line, but the wordwrap issue may have split it into two lines)

defaults write com.barebones.bbedit Subversion:SubversionToolPathOverride
/path/to/svn/binary

which for MacPorts is :

[2009.01.04](06:14PM) -> [roscoe] ~ $ which svn

/opt/local/bin/svn

I will implement Patrick Woolsey's method which is the simplest and correct way to do this.

So using Patrick's advice...

[2009.02.04](11:26AM) -> [roscoe] ~ $ defaults write com.barebones.bbedit Subversion:SubversionToolPathOverride /opt/local/bin/svn

and sure enough that's all it took...

[2009.02.04](11:26AM) -> [roscoe] ~ $ defaults read com.barebones.bbedit | grep Subversion

    "Subversion:SubversionToolPathOverride" = "/opt/local/bin/svn";

[2009.02.04](11:26AM) -> [roscoe] ~ $ 

[Lewis@Gmail]

On 2-Apr-2009, at 08:43, Craig Heilman wrote:
> Which method is "safest" in the face of OS updates and the like?

Patrick's method of telling the app the path to the subversion you
want to use is the most safe in my opinion.

I would NEVER put /opt/... first in my path chain as I don't trust
myself that much; but I know other people do.

--
Major Strasser has been shot. Round up the usual suspects.