Andreas:
On Wed, Apr 30, 2025 at 5:28 PM Andreas Stieger
wrote:
> On 2025-04-30 17:07, Doug Robinson wrote:
>
> On Wed, Apr 30, 2025 at 10:25 AM Doug Robinson
> wrote:
>
>> On Wed, Apr 30, 2025 at 4:17 AM Andreas Stieger
>> wrote:
>>
>>> WANdisco is not a typical Subversion server implementati
On 2025-04-30 17:07, Doug Robinson wrote:
On Wed, Apr 30, 2025 at 10:25 AM Doug Robinson
wrote:
On Wed, Apr 30, 2025 at 4:17 AM Andreas Stieger
wrote:
WANdisco is not a typical Subversion server implementation. For
synchronous multi-site replication (as opposed to sv
Folks:
I missed replying to one more detail that should be corrected.
On Wed, Apr 30, 2025 at 10:25 AM Doug Robinson
wrote:
> On Wed, Apr 30, 2025 at 4:17 AM Andreas Stieger
> wrote:
>
>> WANdisco is not a typical Subversion server implementation. For
>> synchronous multi-site replication (as
Andreas, et. al.:
On Wed, Apr 30, 2025 at 4:17 AM Andreas Stieger
wrote:
>
> On 2025-04-29 18:53, LWChris wrote:
> > Therefore we suspect it was some kind of caching issue in the SVN
> > server (WANdisco) due to same path same UUID same commit number; after
> > restarting the SVN server, the iss
On 2025-04-29 18:53, LWChris wrote:
Therefore we suspect it was some kind of caching issue in the SVN
server (WANdisco) due to same path same UUID same commit number; after
restarting the SVN server, the issue went away. But I don't know if
WANdisco is a "typical server implementation", or if
On 2025-04-28 18:11, Andreas Stieger wrote:> 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.We noticed the issue that all had the same UUID while we were trying to figure out a problem we encountere
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 o
ng
all repos having the same UUID, just like your case.
Your solution sounds fine - as long as you are happy it.
But what to do about the existing ones? What are the implications of
> duplicate UUIDs on a server?
>
> For context, we’re talking about some thousand repositories used by some
a new repository was created. This resulted in lots of repositories having the same UUID as the template.I intend to quick fix that by calling "svnadmin setuuid" after copying the template, for future repositories.But what to do about the existing ones? What are the implications of duplicate UUIDs
