On 2004.08.12 08:24:33 +0000, Laurent Duperval wrote:
> I use Gentoo Linux. Subversion 1.0.x where x < 4 used to work for me. I
> hadn't touched my installation for a long time, but I've periodically
> upgraded.
>
> Today, I'm trying to use it again but it doesn't work. I get an error
> saying:
>
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///mnt/share/svnrepos/mysoft/trunk'
> svn: Berkeley DB error while opening environment for filesystem
> /mnt/share/svnrepos/db:
> Resource temporarily unavailable
>
> I can telnet correctly to localhost:3690. I can do a "svn diff" and see
> correct results. But I can't do an update or a commit.
"svn diff" only compares the file in the working copy to the file in the
.svn subdirectory, rather than actually querying the server.
> Does anyone know what could be the problem? According to some messages
> on the list, this could be due to the version of db I'm using.
It could. This happened to me.
> I believe
> at the time of my original installation I was using a db 4.0.x flavour,
> but I'm not sure. I'mcurrently using 4.1.25.
It would be good to know for sure. Check /var/log/emerge.log
Or browse the Gentoo CVS tree to see when a 4.1 version was unmasked to
get an estimate, if you upgrade everything often.
> DB 4.2 isn't available yet for Gentoo.
DB 4.2 is in portage, just masked.
I'm assuming you did originally create this repository with bsddb
4.0.x, and you're now running 4.1.x, and you don't already have a
current backup in "svnadmin dump" format.
1. Backup your repository files!
2. Completely uninstall bsddb, then install bsddb 4.0.14-r3
(If you have more than one version of bsddb on the system, Subversion
will find a way to use the wrong one. :-> )
3. See if svn works now. If not, try re-emerging subversion 1.0.6
4. Once svn works, do a "svnadmin dump" so you have a version-independent
backup.
5. Either pin bsddb to 4.0.14-r3, or upgrade it to 4.2.52_p2
(See package.mask and package.keywords in the Portage manual for the
current best way to force versions of packages.)
6. If you chose to upgrade to bsddb 4.2, your version mismatch problem
will be back, so you'll need to "svnadmin load"
--
David Ripton dripton@ripton.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 12 16:09:00 2004