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

Re: Which is the best tool /process to migrate VSS (with history) to Subversion

From: Branko ─îibej <brane_at_apache.org>
Date: Sun, 26 Jun 2016 20:14:34 +0200

On 26.06.2016 16:49, Mark Phippard wrote:
> The issue is that a lot of VSS repositories have hidden corruptions
> that do not surface until you try to migrate the history. It seems
> like the corruptions are often in the history or something, so it is
> only when you start trying to extract old data that it surfaces.

The reason for that is that the architecture of VSS requires that every
user has write access to the actual repository databases; these are just
files in a shared folder, and VSS assumes that CIFS locking is
sufficient to implement distributed transactions. Since that's not the
case, there's no way to avoid silent corruptions.

Back in the day I administered a VSS repository used by a team of some
20 or so developers ... fixing corruptions was a regular daily task.

-- Brane
Received on 2016-06-26 20:13:11 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.