Make sure you install the server and client, not just the client. After that you should have the svnadmin tool and be good to go.

If you are still having problems, check with whoever originally installed your Subversion server. It sounds like you might be confused between doing a client upgrade and doing a server upgrade.

We need to upgrade our SVN from version 1.4.4 to version 1.6

I thought we could use command line: svnadmin upgrade

But it does not exist in our version.

SVN is running on a Windows Server environment

what should we do?

Subversion should work just like any other Solaris software. It’s a while since I used Solaris and I haven’t used 10 with its containers. The Subversion site lists two packaging schemes for Subversion, the CollabNet package and the Sunfreeware package. I’ve had luck with Sunfreeware in the past, it might be familiar to you.

CollabNet Subversion for Solaris: http://www.collab.net/downloads/subversion/solaris.html

Sunfreeware Subversion for Solaris: http://www.sunfreeware.com/programlistintel10.html#subversion (Note: this is Subversion 1.4.5, not 1.5.x, but the 1.4 client will work with a 1.5 server).

Good luck!

I hope this message finds you well.

I am in desperate need of assistance and have been trying for some time now with no luck. And it seems you are the only person that maybe able to assist. Every avenue i try, i seem to be hitting brick walls. Please, can you assist.

We currently have a Solaris v10 setup where we have a server and multiple containers .. Now when we normally install any client s/w, we will install it on the global server and then it will filter through the various containers.

I need to know if subversion client supports this? If I’d install the client on the main global server, will it prompt me to filter down to the various containers? Will it ask me which containers i’d want to filter down to ?

We tried to install Subversion client on one of the individual container’s but it refused for us to write to /usr/bin directory due to our setup.

The containers are sparse.

Your help will be greatly appreciated.

Ps. If you could reply as soon as possible I would be very grateful …

And apologies for any inconvenience caused.

Thanks Kindly
Naren

It sounds like your pre-commit hook is running svnlook from 1.4 and it doesn’t work with the new 1.5 format. Make sure all the binaries on the server are 1.5, not a mixture of 1.4 and 1.5. For example, you might have upgraded your “subversion server” package to 1.5 but not upgraded the “subversion client” package. Exact package names will depend on what Linux you’re running.

svn: Commit blocked by pre-commit hook (exit code 1) with output:
svnlook: Expected FS format ‘2′; found format ‘3′

Is there any way to roll back the update, so we can at least keep working without branching? I’ve been googling all around, and there seems to be no mention of undoing an upgrade…