Renegade - False Positives

[andrews]

Using 4.1.0. We have a vault repository, into which we're loading successive versions of files from our old PVCS repo.

When we do an extract from PVCS into the Vault working directory, some files (by no means all!) are being marked as renegade even though they haven't changed. Their timestamp is the same, their size is the same ... and in Vault when we select Show Differences it says the files are equivalent - but still marks them as renegade.

If we checkout and commit, Vault doesn't create a new version number for the files - evidently it realises that no change is required. It does, however, change the local file's timestamp to the current date/time (which is definitely undesirable!) The real problem though is the wrong identification of these files as renegade.

If you have difficulty replicating this we can send you some of the problematic files...

[lbauer]

Is there any pattern to which files are renegade? Are these certain types of files? Are you doing a get from PVS in to a Vault working directory?

What is the status of files that have actually changed?

It does, however, change the local file's timestamp

You can change the local files timestamp to current time, check-in time, or modification time in the Vault GUI client under Tools-> Options-> Local Files> Set file time.

[andrews]

There doesn't seem to be much pattern to it. Sometimes the files are binary, and others are mergeable. We're doing the Get from PVCS to a series of directories (not the Vault working directory). We clear Vault's directory, copy the contents of a PVCS "get" directory into it, then in Vault we go looking for files to add, missing files (ie to be deleted) and renegades (changes). After this we apply a label identifying the version and repeat the process for the next version of files.

Once a file has appeared as a "false positive" renegade, it will continue to do so with subsequent versions from PVCS - so after several versions

I'm trying to narrow it down to a small sample that demonstrates the problem reliably.

What is the status of files that have actually changed?

The status of files that actually changed is also Renegade. There's no way to tell them apart at that stage. Once checked out, I can look through the list in the Pending Changes, going through those with no size changes & choosing Show Differences to identify them.

You can change the local files timestamp to current time, check-in time, or modification time in the Vault GUI client under Tools-> Options-> Local Files> Set file time.

I already have it set to modification time, but Vault's checkin seems to be ignoring it & setting the current timestamp. Only the false positives have their timestamps changed - files that have genuine changes are left untouched.

[lbauer]

You could switch to CVS mode during the import, so that files won't be renegade. Also, in the Vaut GUI Client Tools->Options->Local Files, use CRC's to determine file status.