[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: identical repository uuid

From: Branko Čibej <brane_at_wandisco.com>
Date: Wed, 08 Aug 2012 22:01:45 +0200

On 08.08.2012 21:46, Stefan Küng wrote:
> On 08.08.2012 21:45, Mark Phippard wrote:
>> On Wed, Aug 8, 2012 at 3:40 PM, Stefan Küng <tortoisesvn_at_gmail.com>
>> wrote:
>>> Just stumbled upon something that shouldn't happen:
>>> both neon and serf repositories have the very same repository uuid:
>>> 61a7d7f5-40b7-0310-9c16-bb0ea8cb1845
>>> you can check yourself with
>>> svn info http://serf.googlecode.com/svn
>>> and
>>> svn info http://svn.webdav.org/repos/projects
>>> Since the uuids are created by Subversion, maybe there's not enough
>>> randomness in the code? Or is this just a freaky coincidence?
>>> Or do all DAV libraries get the same uuid? :)
>> Looks like Serf lived here once:
>> http://svn.webdav.org/repos/projects/serf/trunk/
>> I am guessing that the Googlecode repository was created from a dump
>> of the project from this repository and they did not use --ignore-uuid
>> when they loaded the dump file?
>> Or something like that :)
> Ah, that explains it.
> I guess I better use the repository root url then to distinguish
> between repositories, not the uuid.

That would be wrong. We /know/ that different URLs can point to the same
repository. IMO whoever is administrating the Serf repo should just
change the UUID and handle the consequences. UUIDs are supposed to be
unique (in general) and also unique repository identifiers (in
Subversion's case), and the fact that the Serf repo was created with an
existing UUID is just an administrative oversight that happens to break
Subversion's assumptions.

-- Brane

Certified & Supported Apache Subversion Downloads:
Received on 2012-08-08 22:02:22 CEST

This is an archived mail posted to the Subversion Dev mailing list.