Re: Unable to open an ra_local session to URL
From: Nico Kadel-Garcia <nkadel_at_comcast.net>
Date: 2006-05-17 05:39:08 CEST
Some sys-admins are very good at not knowing what might affect other things. For example, an apparently harmless update to db4x installations or user configurations could easily disable or enable a particuler library at just the moments you were doing this, as part of fixing some other issue.
this is why I like seriously package managed systems, rather than the guesswork of the "download and compile locally" operating systems. You have a chance to test the specific packages in particular setups.
Thanks for the info, but I think this may be a red herring.
For one thing, I was using svn last week without any problems, and our sysadmin assures me that nothing has been changed in any way either with svn or BDB in the past 6 months. So the difference between last week and now can't be explained by changes in the installed svn or BDB software.
To make a very long story short, I created a brand-new repository and populated it from a recent repository dump, and, once again, I was able to use subversion normally. The error messages I was getting with practically every svn command went away.
But after a couple of hours of normal svn use, I have now run into another inexplicable svn failure. I've described this in a separate post ("svn died for good mid-command...").
On 5/16/06, Ryan Schmidt <email@example.com > wrote:
> % svn co file:///home/jones/svn-repos/MyProject/trunk MyProject
Seems you or someone upgraded the BerkeleyDB libraries on your system
Once you get this sorted out you may want to consider switching from
This is an archived mail posted to the Subversion Users mailing list.