RE: Cvs2svn dies with "dbm.error: cannot add item to database"
From: Johnson, Graham <gjohnson_at_alpineaccess.com>
Date: 2003-07-01 23:30:28 CEST
On RedHat, cvs2svn is chugging along fine on my repository, currently
Assuming the repository will be portable between Linux and Solaris, I
I'm willing to provide any assistance/information needed to figure out
-- Graham Johnson gjohnson@alpineaccess.com -----Original Message----- From: kfogel@collab.net [mailto:kfogel@collab.net] Sent: Tuesday, July 01, 2003 2:20 PM To: Johnson, Graham Cc: dev@subversion.tigris.org Subject: Re: Cvs2svn dies with "dbm.error: cannot add item to database" "Johnson, Graham" <gjohnson@alpineaccess.com> writes: > Below is the version info. This is Solaris 8; I suspect the dbm > implementation isn't as good as what cvs2svn is used to. > > I tried last week to build Python using gdbm instead of ndbm, but I > don't think I did it right. It still failed, though slightly > differently (dbm_error returned 0 instead of 2). Do you know anything > about getting Python to use a different dbm implementation? Can it be > made to use Berkeley DB? I don't offhand, but maybe someone here does (or check the docs at python.org, they're very thorough.) What I'm mainly interested in is determining exactly which db is causing a problem and why, so cvs2svn.py can somehow test for it... > We do have a linux box here (RedHat 8), so I'm going to try to install > svn on that and try it there. I'll let you know how it goes. Thanks. > 1546 : ~/downloads/Unix/svn/tools/cvs2svn>grep LastChangedRevision > cvs2svn.py # $LastChangedRevision: 6360 $ A little bit behind HEAD, but not significantly so. -K --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org For additional commands, e-mail: dev-help@subversion.tigris.orgReceived on Tue Jul 1 23:31:18 2003 |
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.