On Jul 13, 2022, at 12:04, Thorsten Schöning wrote:
> Guten Tag Daniel Shahaf,
> am Mittwoch, 13. Juli 2022 um 15:25 schrieben Sie:
>
>> It'll be a lot easier to set the repository's UUID to the one expected
>> by clients. See «svnadmin setuuid».
That was going to be my suggestion as well.
>
Guten Tag Daniel Shahaf,
am Mittwoch, 13. Juli 2022 um 15:25 schrieben Sie:
> It'll be a lot easier to set the repository's UUID to the one expected
> by clients. See «svnadmin setuuid».
Which isn't possible, as the logically same repo is used by working
copies as public or private repo
Hi Nathan,
See my responses further below as [MK 2022-07-13: ].
Not sure whether my email properly has the [In-Reply-To] filled-in to end up in
https://lists.apache.org/thread/n5vo9kznz9z2gzwy7kym9nj5rl9fw8mw. As I am
forced to use Outlook, and googling doesn't tell me how to achieve
Thorsten Schöning wrote on Mon, Jul 11, 2022 at 16:06:11 +0200:
> BUT: Each working copy stores a UUID of it associated repo and those
> UUIDs are different between private and public repos. In the past, it
> wans't supported to change that, one needed to either replace them in
> config files or
