Edward Z. Yang wrote:
> Stefan Küng wrote:
>> Please check if those repositories also have different UUIDs. If they
>> don't, you have to do a dump/reload for those: every repository must
>> have a unique ID (that's why it's called an UUID). Repositories with
>> identical UUIDs can only happen if you copy a 'default' repository
>> for every project you create.
> Thank you!
> UUIDs are the problem. :-D My situation was a little different though:
> two projects started off in the same repository, but at one point we put
> one project in another one by dumping and filtering it, so they have
> identical UUIDs. I can fix things on my end by changing one of the
> repository's UUIDs with svnadmin load.
> However, TortoiseSVN under no conditions should be segfaulting. Can it
> detect if two repositories have the same UUID but are out of sync? Also
> (and this is not a TortoiseSVN issue), the situation of identical UUID
> arose when I followed the directions in the SVN book for splitting out
> So either it's permissible for two repositories to have the same UUID
> (in which case TortoiseSVN needs to make adjustments), or the docs need
> to be adjusted.
I've reported the book issue to the svn guys. I think the book examples
Of course, TSVN should not segfault. The problem is that it's very hard
to detect corrupted log cache files.
>> Also, can you maybe try a nightly build from
>> http://nightlybuilds.tortoisesvn.net/latest/ and check if it still
> No such luck. Actually, that was the first thing I tried. At the very
> least, it didn't work with r12927.
Did it just crash or did you get the cache to get corrupted again with
that version? My change in r12927 should reduce the risk of the cache
getting corrupted a lot.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-05-17 09:08:37 CEST