Re: Huh... BDB...?

>>>>> Mark Phippard <markphip_at_gmail.com>:

> It seems unlikely that a Debian upgrade could do this, because the
> only way to convert a repository is to dump the current repository,
> create a new one and then load the dump file.

Well, in theory a debian upgrade could have done a dump and load (and
might have done so to avoid BDB problems. Ie. dump with the old version
and load with the new version). One indication that it could have been
something like that, is that the files and directories in the top level
repo dir have the date of the sarge->etch upgrade.

However, as I said, I can not find any mention of anything like that in
the changelogs.

And besides... the svn debian package have no information of the repos
created in the file systems of the machines on which they are installed.

So I'm guessing the culprit here is me, being proactive, and dumping the
repo before the upgrade, and then creating a fresh repo, and loading
after the upgrade, and not paying attention to the type of repo that was
created... and not remembering it nearly two years afterwards.

Being proactive is so ninties!

> Try running svnadmin recover /path/to/repos

> That should fix the BDB version issue. You can then dump/load if you
> want to convert the repository.

Yep, I found out with a little more googling.

Thanx!

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1210629

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-22 20:43:45 CET