Dear all,
I have run upgrade-all and in the process accidentally upgraded subversion
(from 1.1 (I think) to 1.2). The major problem is that 1.1 uses the
Berkeley data base 4.2 and svn 1.2 uses Berekeley data base 4.3.
This results in error messages leading with DB_VERSION_MISMATCH when
accessing the svn repository.
There are ways of upgrading your repository
(http://subversion.tigris.org/faq.html#bdb43-upgrade) data but to do that
I first need an working version of the old subversion.
Following advice in the finkinfo file for the new svn-ssl, I tried to
install the older svn-ssl-1.1.4-11. However, I run into problems as shown
below:
I carried out the following steps:
uninstall current svn-ssl via "fink remove svn-ssl"
Install the last version that uses db42 via "fink install
svn-ssl-1.1.4-11"
Then run "fink install svn-ssl-1.1.4-11"
(Good news; it is actually saying that it will install db42.)
However in the process we come along these lines:
#--------------------------------------------------------------
subversion/bindings/java/javahl/classes
mkdir subversion/bindings/java/javahl/include
mkdir subversion/bindings/swig/java/build
configure: WARNING: we have configured without BDB filesystem support
You don't seem to have Berkeley DB version 4.1.25 or newer
installed and linked to APR-UTIL. We have created Makefiles which
will build without the Berkeley DB back-end; your repositories will
use FSFS as the default back-end. You can find the latest version of
Berkeley DB here:
http://www.sleepycat.com/download/index.shtml
### force SWIG to use gcc 3.3 too
perl -pi.bak -e 's|(SWIG.*)gcc|${1}gcc-3.3|g' Makefile
#--------------------------------------------------------------
I guess the reason is that apr-ssl links to db43 (not db42) and that
therefore the subversion configure script thinks that not db is available.
(I couldn't find an older apr-ssl that links to db42.)
Because subversion compiles without support for Berkeley DB, I guess
this it won't be able to read my repositories either.
This is the first point where I got stuck.
Also, the build process stops with this error message:
#--------------------------------------------------------------
/sw/src/fink.build/root-svn-ssl-1.1.4-11/sw/lib/libsvn_fs_base-1.dylib
/sw/src/fink.build/root-svn-ssl-dev-1.1.4-11/sw/lib/
mv: rename
/sw/src/fink.build/root-svn-ssl-1.1.4-11/sw/lib/libsvn_fs_base-1.dylib to
/sw/src/fink.build/root-svn-ssl-dev-1.1.4-11/sw/lib/libsvn_fs_base-1.dylib:
No such file or directory
### execution of /bin/mv failed, exit code 1
Removing build lock...
/sw/bin/dpkg-lockwait -r fink-buildlock-svn-ssl-1.1.4-11
(Reading database ... 83017 files and directories currently installed.)
Removing fink-buildlock-svn-ssl-1.1.4-11 ...
Failed: phase installing: svn-ssl-dev-1.1.4-11 failed
Before reporting any errors, please run "fink selfupdate" and
#--------------------------------------------------------------
Again, I don't know how to proceed here.
I am happy to switch to the new file systems data base of subversion but I
need to read my data in the old format to be able to do that.
After lots of searching, I have found Martin Ott's page
http://www.codingmonkeys.de/mbo/ from which I downloaded the binary
svn-1.1.4. This installed fine (just click and go, standard Mac OS X
package) and I can now use my repositories again (!!). That's very good
news.
The plan now is to convert the repositories to get rid of the bdb
dependence, then to remove the binary installation of svn-1.1.4 (is there
any clever way for this or do I delete files from the /usr/local and /opt
directories manually?), then to install the latest svn via fink.
Any advice on how to proceed more efficiently/safely etc is welcome.
Otherwise I hope this might be useful to others.
Regards,
Hans
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 3 13:42:12 2006