Normally one can simply run svnadmin recover to upgrade a Berkeley DB repository in-place. However, due to a bug in the way this command invokes the db_recover()
API, this won't work correctly when upgrading from BDB 4.0/4.1/4.2 to BDB 4.3.

Using an older svnadmin binary (that is, linked to an older BerkeleyDB):

Recover the repository: 'svnadmin recover /path/to/repository'

Make a backup of the repository.

Delete all unused log files. You can see them by running 'svnadmin list-unused-dblogs /path/to/repeository'

Delete the shared-memory files. These are files in the repository's db/ directory, of the form __db.00*

The repository is now usable by Berkeley DB 4.3.

As the instructions note, you need a copy of subversion linked with a pre-4.3
version of the Berkeley database library. Subversion uses Berkeley via the APR Library. So we need to install appropriate
verions of Berkeley, APR and Subversion.

My notes are below. Note that I installed the APR and Subversion software
into a local directory (/home/mk/proj/svn_db/local in my case). Also, my
Subversion repository is in /data/svnroot.

Tools Roundup

Tools, tools and more tools for the codemonkey! Here's a little summary of some of the tools I've been using lately.

SCM and Web Tools:

ViewCvs: We all love doing "cvs log file.C | more" and then "cvs diff -r1.12 -r1.13 file.C",
but I admit that it's really nice to be able to browse the history of your project online. Viewcvs works with cvs and subversion and
is used by no less an authority than sourceforge.net.

Enscript: I discovered this as it is used by viewcvs to syntax highlight and color code for online viewing. I tend to
use it like "encript --language=html --highlight --color=1 -t 'Logger.C' -p Logger.html Logger.C".

GraphViv defines a little language for describing graphs (DAG's and the like). There are utilities
for converting the descriptions to beautiful images. See the gallery for examples.
GraphViz is so pretty I'll be on the lookout for interesting datasets just so I can graph them.

Code Auditing Tools:

Flawfinder and Splint are static program checkers that
flag uses of "unsafe" functions (like strcpy). I wish the use of tools like this would become common during development.

http://www.daemonkitty.net/lurene/papers/Audit.pdf: OpenBSD continuously audits
its codebase, fixing bugs. When a new bug, or class of bugs is found, the entire code base gets re-audited looking for other instances of the
bug. There's wisdom in that! We all know about buffer overflows and string format bugs, but what else have the OpenBSD team been fixing?
Certainly you could review the security patches they've issued, or watch the changes to the HEAD of their CVS repo. The paper above
is a shortcut: it lists the major flaws found in OpenBSD software.