I thought I had everything setup nice and clean. I have Subversion 1.5
installed as my server, and finally got the last project converted
over to Subversion.
However, our build machine is using Subversion 1.3. It's an old SUSE
Linux installation, and we simply couldn't get a more recent revision
of Subversion to work on it. Not without updating Apache, APR, Neon,
and who knows what else. Heck, it took us a week just to get
Subversion 1.3 running, so upgrading isn't an option right now.
Now, here's the problem: Everything seemed to work our nicely. Our
build machine (running 1.3) is able via Hudson to checkout the code
and do a build. It can do labeling via Hudson. It looks good.
However, one of our developers noticed that our Server (running
Subversion 1.5) has only DB format 2 on it. He tried a "svn log -g"
and got the following error message:
svn: Querying mergeinfo requires version 3 of the FSFS filesystem
schema; filesystem '/solbright/svn_repositories/dev/db' uses only
version 2.
I can run svnadmin upgrade on the Subversion repository, and in
seconds, get it to be upgraded to db format version 3. I've tried this
on a back of our server with no problems.
The question I have are possible side effects on our build server
running Subversion 1.3. I know that this build server can't do merge
tracking, but I don't really need to worry about that. I simply want
to know if there would be any side effect upgrading our repository to
DB format version 3. All this subversion client has to do is checkout
the code, work with Hudson, and do labeling. There's no real
development that takes place on it.
From what limited testing I'm doing, it all looks okay. I just want
some confirmation that I won't be blowing everything up if I do the
upgrade.
--
David Weintraub
qazwart_at_gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-30 17:18:06 CET