I created /var/db/mysql/data-dir/my.cnf with this contents [mysqld] innodb_lock_wait_timeout = 300 to increase the lock wait timeout to 5 minutes.
This prevents the first flavor of the problem, but still doesn't help me with the duplicate entry issue: Resyncing repository history... Command failed: (1062, "Duplicate entry '820-Development/trunk/... (some stubified repository path) ...' for key 1") In order for me to make at least _some_ progress with this, could someone please shed some light on what is actually mapped here ? I understand 820 is the Subversion changelist number, so how can this be key 1 ? And why is the repo path stubified ? Is this just in the error message or are paths really not stored in their full length ? That would possibly explain why there is a duplicate entry, but I have a hard time believing that the database scheme was designed that short-sighted. I know 0.10.2 was just released yesterday and everyone is probably really busy updating, but I could really use some help here, because otherwise Trac will look to my company like something that might work for small test systems, but is not mature enough for production environments. TIA, CU z00m1n --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
