svn: This client is too old to work with working copy; please get a newer Subversion client

I originally found myself here while beta testing a new subversion client and inadvertently clicking “yes” I want to upgrade my working directory. But that’s another story. Here’s what I did (I’m running Mac OSX 10.5 Leopard):

1. Download and install the Subversion 1.5 binaries from OpenCollabNet (via http://subversion.tigris.org/getting.html#osx). Once you download the .dmg, simply run the installer like you’d normally do any installer. You’d imagine that this would be all but it’s not because the new subversion installs to /opt/subversion/bin rather than /usr/bin.
2. Update your path by either editing the “~/.profile” (for your individual user profile) or “/etc/profile” (for all system users). I chose to do this for my system as I used several accounts for different purposes. If the file doesn’t exist you need to create it. Then add the following line to the top of the file: 

   export PATH=/opt/subversion:$PATH

3. Finally, rename the previous svn executable. You may find that you still cannot access subversion 1.5 if the 1.4 file is still available. Navigate to your /usr/bin folder and rename the old svn located there:

   $sudo mv svn svn.old

   • Thanks much Coals [2] Newcastle for helping me with this one. 
4. Now when running svn –version you should see the 1.5 client referenced.

$ svn –version
svn, version 1.5.2 (r32768)
   compiled Sep 19 2008, 14:38:15
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/).

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.

Reason: Error reading from remote server

---

Apache/2.2.3 (Red Hat) Server at [myserver.com] Port 443

And when viewing the log files I was receiving errors like:

And this, too: (I tried these instructions too, but didn’t work.)

Additionally, I received “Operation Not Permitted” errors when trying to restart and/or stop the mongrel clusters:

Solution

I was able to resolve the issue by killing all the active Mongrel processes and then restarting manually. You can do this by:

1. Viewing all active mongrel processes:

(The second number is the process id; that is the id you’ll use to kill the process.)


2. Killing each process id

“sudo kill -9 [process id]“, For example, to kill the first process listed above:

3. Restarting your Mongrel instances

In order to get things working right I had to update the system files so everything would run:

Now running the update works.

A number of months ago ActiveReload came on the scene with a new application called “Warehouse” which makes for a really aesthetic and functional way of managing repositories in Subversion.

The app requires you to install the Ruby Subversion Bindings, and while it may seem quick in the instructions, it wasn’t like that for me installing on RHEL 5. (I’m following through the instructions listed here).

Be warned - you may want to go grab a cup of java and get comfortable, because this is a long one …

First of all I have a problem extracting and installing swig.

I don’t know why it happened and why the file couldn’t extract so instead I went straight to the main sourceforge page (http://sourceforge.net/projects/swig/), download the latest build, and uploaded it to my server. Then follow the instructions using the new filename (for me it was “swig-1.3.32-rc1.tar.gz”).

This got me through the ./configure, but during the make I received an error that pointed to a missing “g++”.

I then found out (by way of a 2 hour date with google) that by default RHEL5 doesn’t come with g++ installed. (I’m sure a much seasoned linuxologist would have figured it out quicker, but I digress.) So, using yum:

In order to get the make to pass, I then had to re-run the configure. The make, and install succeeded afterwards.

But it’s not over yet. For step 2, I ran then tried to run the “make swig-rb” and received another error regarding the Apache Portable Runtime not being installed:

As this post reveals, there is some newness between the Apache Portable Runtime (APR) and neon (don’t even ask me to explain) which make for an error in trying to install the bindings (the command “make swig-rb”). So to get by this, I followed the instructions by Josh Goebel at this pastie to get by. ***Note that on line 4 you need to omit the “tar.gz” as I’ve indicated below.

WOW!!! When it rains it pours … while running the first config for neon, the process stopped because I didn’t have an XML parser on the system. (I’d thought the folks who set it up had done so, but that wasn’t the case.) So I installed expat with:

And after continuing through the remainder of the pastie, I’ve finally got subversion bindings installed! And now for the moment of truth …

Eureka! The test passed! Now I’ve got to actually install Warehouse … but I’ll save that for tomorrow. And I won’t even tell you how long it took me to finish all this stuff.

Here’s the complete pastie with my additions (depending on how your admin set things up you may have to sudo each line):

If you’re on a Mac, you’ll need to edit your “/etc/profile” page and then type these in, so something like “$textedit /etc/profile” or “$ mate /etc/profile” (if you are using TextMate) from your Terminal window will open your system profile.

Now what’s nice is that f I want to visit “my directory”, while in the terminal I just type”$ gotoMyDir”; if I need to run a capistrano “deploy_with_migrations” script (yes, I’m using 1.4.1 until a few more 2.0 updates finalize) I just type in “$ capdm” … you get the picture.

Nice indeed, and saves the keys!

GREAT Shadow Puppetry - The funniest videos clips are here

videos,funny,youTube

1. First you’ll need to install ImageMagick $ sudo yum install ImageMagick ImageMagick-devel
2. Now configure, setup and make $ sudo mkdir /home/imins $ cd /home/imins $ sudo wget ftp://ftp.imagemagick.org/pub/ImageMagick/ImageMagick.tar.gz $ sudo tar -zxvf ImageMagick.tar.gz $ sudo cd ImageMagick* $ sudo ./configure --prefix=/usr --enable-shared=yes $ sudo make && make install

   
   Note: the last command (make & make install) will take a long while to run

3. Install the RMagick gem $ sudo gem install rmagick

Thanks to NDCHost, Cyberciti and Creativist for the help.

Blogged with Flock

Tags: rmagick, linux, imagemagick, rhel5

Embedded Video

Blogged with Flock

Tags: funny, videos