On Sat, Aug 29, 2009 at 12:56 PM, Rich Shepard<[email protected]> wrote: > My Subversion repository was created with the BerkeleyDB version included > in an earlier Slackware than is currently running. When I try to commit > changes the attempt fails due to BDB errors.
Rich, It's unfortunate that you're using BDB with your svn repo. The file system db is more robust across versions. I would recommend getting away from BDB in the future. > A Google search turned up an equivalent situation using LDAP, but the > solution is specific to that application and not applicable to Subversion. > Another Google search on "upgrading BerkeleyDB" produced a page that leads > to other pages, but the commands (e.g., DB->upgrade, or DB_ENV-*) cannot be > executed because the shell doesn't find them. The Web pages probably make > sense to those who know BerkeleyDB inside and out, but not to a naive user > like me who's stuck with an application that uses it as the back end. > > Does anyone here know how to upgrade BDB? I have the following versions > installed: > > db1-1.85-i386-1 > db3-3.3.11-i486-4 > db44-4.4.20-i486-2 > > I suspect the Subversion repository database was created with db4.2. I would try getting the old version of db on their so you can work with the data. Then, I think you need an svn specific tool. I would recommend exporting your repository, creating one that uses the file system db and reimporting your repository. I recommend the svn red bean book for reference purposes: http://svnbook.red-bean.com/en/1.0/ch05s03.html The section I just linked should contain all the information you need to export your repository and reimport it once you can access it again. Good luck! Jason PS darcs is even easier than svn, so just switch to that :) (Yes, I'm biased.) _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
