On Tue, 2005-04-26 at 07:23, bruce wrote:
> hey...
>
> i just modifed some things with subversion. i'm using gforge and and i get
> the following from the ViewCVS portion...
>
> Traceback (most recent call last):
> File "/viewcvs/lib/viewcvs.py", line 3394, in main
> request.run_viewcvs()
> File "/viewcvs/lib/viewcvs.py", line 268, in run_viewcvs
> self.rootpath, rev)
> File "/viewcvs/lib/vclib/svn/__init__.py", line 342, in __init__
> self.repos = repos.svn_repos_open(rootpath, self.pool)
> SubversionException: ('Bad database version: compiled with 4.2.52, running
> against 4.3.27', 160000)
>
> does anybody have any idea as to what's the cause....?
Sounds like there are multiple Berkeley DB libraries installed on the
machine and that Subversion is picking up a different version than the
one against which it was compiled (or configured).
> also, if it is a db issue, is there a way to rectify it?
Try ldconfig -v to see if the right library is getting picked up.
I'm not sure if it's feasible to do an strace on ViewCVS. If it is,
'strace -f' will show the exact library that is being picked up. You may
also be able to do 'strace -fp <pid-of-ViewCVS>' to attach to a running
ViewCVS and then run your command in another window to see which BDB
library is getting picked up.
To point to the right library, modify /etc/ld.so.conf or add a
BerkeleyDB-specific file in ld.so.conf.d, to point to the right version.
> also, is there a way to get away from the db4, and use the
> filesystem approach for subversion...
The recipe is:
dump repository to dumpfile
mv repos aside
create repos with same name, but with --fs-type fsfs
load into repos from the dumpfile
hth
Sameer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 26 05:21:47 2005