On Sat, 29 Aug 2009, Rich Shepard wrote: > Date: Sat, 29 Aug 2009 14:39:15 -0700 (PDT) > From: Rich Shepard <[email protected]> > Reply-To: "General Linux/UNIX discussion and help; civil and on-topic" > <[email protected]> > To: [email protected] > Subject: Re: [PLUG] Upgrading BerkeleyDB > > On Sat, 29 Aug 2009, Jason Dagit wrote: > >> 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. > > Jason, > > I've no particular liking of BDB; I'd rather use SQLite or anything else. > But, I don't know how to direct Subversion to use a different DB. > >> 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'll try loading dbd42; that's probably what was current when I created > the 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. > > I bought Mike Mason's SVN book in 2005 and it's been helpful. Doesn't > cover this case, of course. In retrospect I'm disappointed that the SVN > developers didn't consider changes in the db back end and build in upgrades > when the application is upgraded. > > Thanks, > > Rich
This is why I still use CVS. I can go in there and reconstruct the files even in the worst case scenario. Any system that stores the data in a non-human-readable format worries me. A database backend is fine as long as it stores text, not blobs. Even subversion's file backend is binary, which will not do. Carlos _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
