Wednesday 2 July 2008

Subversion client too old

This is a workaround to fix a problem I had with my svn client after upgrading to Eclipse Ganymede and Subclipse plugin last week. It is based on scattered information I found on the web and that I managed to put together. Hopefully it will save someone some time (somewhere... something... somehow...).
Basically, I had ended up with an svn client 1.4 on my system (ubuntu 8.04) whereas subclipse used a somehow bundled latest version 1.5. So everything went fine, as long as I did my svn work from within eclipse. Until one day (today) I had to do an
svn up
from the shell (we use maven modules and this time I had to update from the parent pom location). Then I got this message
This client is too old to work with working copy '.'; 
please get a newer Subversion client.
This was baffling, as
apt-get install subversion
told me that I had the latest package installed. After some googling, it turned out that svn 1.5 upgrades your working (local) files in a way that it's incompatible with svn client 1.4. To cut it short, I decided to upgrade my svn client.

Here are the steps to follow:

  • At the moment, subversion 1.5 deb package is still considered experimental, so you'll need to add a line to your
    /etc/apt/sources.list
    like this:
    deb http://ftp.it.debian.org/debian experimental main
    (You can choose a different mirror here http://packages.debian.org/experimental/i386/subversion/download)

  • Then do
    apt-get update
    to update your deb repositories

  • Finally
    apt-get install subversion
    to update your svn client to version 1.5. I gladly ignored the warnings about some non authenticable packages (those coming from the experimental repository).

Now everything is working fine.

6 comments:

Anonymous said...

I had to help someone with a similar issue but they were on windows. I had to use a beta version of subversion 1.5. You have to google for it though, I had a hard time finding it.

Anonymous said...

No chance you're on a Mac is there? How about Versions?

Danno said...

Do you always get the gpg error when adding experimental sources?

W: GPG error: http://ftp.au.debian.org experimental Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A70DAF536070D3A1
W: You may want to run apt-get update to correct these problems

Federico Grilli said...

Yes, I had it too but I ignored it and proceeded to install the new svn client version with no problem at all.

TNK Design Desk said...

Thank you so much for these kinds of informative blogs.We are also a digital marketing company in gurgaon and we provide the website design services,
web development services, e-commerce development services.
best web design company in gurgaon
best website design in gurgaon
website design services in gurgaon
website design service in gurgaon
best website designing company in gurgaon
website designing services in gurgaon
web design company in gurgaon
best website designing company in india
top website designing company in india
best web design company in gurgaon
best web designing services in gurgaon
best web design services in gurgaon
website designing in gurgaon
website designing company in gurgaon
website design in gurgaon
graphic designing company in gurgaon
website company in gurgaon
website design company in gurgaon
web design services in gurgaon
best website design company in gurgaon
website company in gurgaon
Website design Company in gurgaon
best website designing services in gurgaon
best web design in gurgaon
website designing company in gurgaon
website development company in gurgaon
web development company in gurgaon
website design company
website designing services

pdusu ba 1st year result 2021 roll number wise said...

Nice Information, your blog is sharing unique information...