Thanks for the reply!
I'm using the mac os x fink binary...
> svn, version 1.0.0
> compiled Mar 16 2004, 15:55:00
Since I didn't compile the binary myself, I'm not certain what version
of Berkeley DB was used; probably at least version 4.2 judging from
the following lines of my svn_repository/db/DB_CONFIG file. Is there
an easy way of determining
> # [requires Berkeley DB 4.2]
> set_flags DB_LOG_AUTOREMOVE
Unfortunately I can't share the database yet. We're currently doing
paper work for open sourcing the code, but have some university
bureaucracy yet to go through.
Since this was our lab group's first experience with subversion, I made
some configuration mistakes early on, which was causing new log files
to be created with the wrong permissions and made it impossible to
commit to the repository even with the permissions corrected. If found
that I could still dump the entire repository, create a new repository,
and reload the dump file as a temporary work around. Doing this
resulted in a repository that was up to date, and there were no error
messages while dumping or loading the dump file, so I assumed at the
time that I had gotten away with it.
I have not yet tried using the Berkeley DB utilities to modify the guts
of the repository directly, but may try this once I get caught up on
For never was a story of more woe
Than this of Drewliet and his svn repository.
On Jun 8, 2004, at 12:06 PM, C. Michael Pilato wrote:
> Andrew Wagner <email@example.com> writes:
>> The broken repository won. I have finally given up on repairing it
>> and started from scratch, breaking all history. I'm fairly sure the
>> problem was caused by svnadmin dump silently creating a subtly
>> corrupted dump file from a corrupted repository. If anyone has the
>> time/desire to investigate this further, feel free to e-mail me; I've
>> posted everything I consider pertinent, but you may know something I
> Sorry, I've not been following your sorrowful tale. Could you rehash
> a couple of details for me:
> - What BerkeleyDB version?
> - Will you share the repository or does it contain proprietary
> - Why do you feel svnadmin dump silently created a corrupt
> - Have you tried using the Berkeley DB db_dump and db_load tools to
> replicate the repository's tables into a new repository?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Jun 9 21:22:14 2004