subversion resync can fail with duplicate key error

[wichert@…]

Doing a resync of a subversion respotitory which appears to be broken as described in #4043 can fail:

done 12400
done 12500
done 12600
done 12700
done 12800
done 12900
done 13000
Command failed: ERROR:  duplicate key violates unique constraint "revision_pkey"

I will include the DEBUG level logs when we hit this problem again.

[Christian Boos]

… when we hit this problem again.

You mean it's not systematic?

Like, you're having the above error, then another resync attempt succeeds? If so, the only possible explanation is that there are concurrent resync attempts, like when the web front-end is still enabled while working at the command line with trac-admin.

I think that the new resync code (in #4586) will handle the above situation as well.

[Christian Boos]

Please can you try to install the latest version of Trac stable, which is supposed to fix this issue as well?

See TracDownload#Tracstable.

[Christian Boos]

Assumed to be fixed in 0.10.4. If not, please reopen and document using a backtrace obtained by running trac-admin at DEBUG level, as well as an svn log -v -r XXX of the problematic changeset.

[Christian Boos]

Actually, what likely happened was that resync was performed while the Trac instance was still in use. I think that this was not really supported before, but in 0.10.4 this is definitely working.