Kind of.

The repository still existed, but I couldn't get there or see any files!

Dorking around with the new version of Eclipse, I installed the Subclipse plug-in to access my version control repository. I noticed while I waited for the install to finish that the version was 1.6, and curiously peeked at my server, finding it to be using 1.5. I figured since I was in a half-holding pattern for my client, that I'd quick throw the new stuff on the server.

I downloaded the new Subversion source and set about building it. There is a new dependency on "sqlite" for some internal hooey, so I added that to the server, too. After that, the build went without a hitch, and the install even went swell. I restarted my Apache server and looked at the repository.

Sadly, this is where things went awry.

I kept getting an error "200030" from the server, which is evidently having to do with the new version control databases, so I figured perhaps my repository was out of date. A quick dump (always back-up your data!) and upgrade of the repository, and nothing changed. I tried a quick downgrade, which replaced the Apache module to use the previously running version of the server, but now the repository was a version too far.

After much searching and finding nothing, and many retries and re-tweaks and restarts, I gave up and decided to return to v1.5 entirely. I did a quick delete (move, really) of the repository and re-created it, and re-imported my saved data (see...sometimes it pays). I restarted the Apache server, and the repository is there, just where I expected it to be.

Alas. No upgrade for you today, Subversion.