On 2025-04-28 17:11, LWChris wrote:
I intend to quick fix that by calling "svnadmin setuuid" after copying the template, for future repositories.
Correct. Recommended for future repositories.
But what to do about the existing ones? What are the implications of duplicate UUIDs on a server?
As you noted, changing a repository UUID breaks existing working copies and svn sync setups. So it is not recommended if you care about them.
However, I am not aware of anything breaking for the server itself, access to the on-disk repository date is purely path based unless I am mistaken.
Andreas
