differences

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
andyjoy
Posts: 2
Joined: Tue Aug 30, 2011 5:45 am

differences

Post by andyjoy » Tue Aug 30, 2011 5:55 am

Hi, I am a developer using Vault Standard version 5.1.1 there are 4 of us in the company and we use Vault exclusivly to keep version control on our projects.

The problems I am facing is with the current status of files in the repository showing as renegade or needs merge, but when you do a show differences they are identical or equivalent under the current rule set.

One situation where this occurs is when the file is checked in on the local client of a developer and the file is copied to our DEV server outside of Vault. When I then look at the Vault Client on the DEV server the file shows as renegade, even though it is identical and has been checked into Vault.

I have two main questions 1) Why is Vault marking the file as renagade when it is identical? and 2) Where can I find the rule set mentioned in the show differences dialog?

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: differences

Post by lbauer » Tue Aug 30, 2011 10:51 am

Why is Vault marking the file as renagade when it is identical?
The Vault client keeps a client side cache and hidden state folder to determine the status of files in the working directory. When you first do a Get, baseline files are established in the _sgvault folder, which is usually in the user's local profile on the client machine.

When you copy a file into the working folder, the Vault client doesn't automatically compare the contents. Rather it looks at the timestamp. If the timestamp of the file in the working folder is different than the timestamp of the baseline file, the Vault client assumes the file has been modified.

If it is modified and not checked out, then the status becomes Renegade. If the file had originally had the status of Old, and then you copied over the file, the status would then become Needs Merge --a file that has been modified, but is out of date compared to the repository version.

Is there a reason you don't do a Get with the Vault client or commandline client on the Dev machine?

Another option might be to enable CRC's, so then the client would actually compare the contents of the file with the repository version. This setting is in the Vault Client under Tools->Options-> Local Files.
Linda Bauer
SourceGear
Technical Support Manager

andyjoy
Posts: 2
Joined: Tue Aug 30, 2011 5:45 am

Re: differences

Post by andyjoy » Tue Aug 30, 2011 10:58 am

Thanks for your reponse CRC is what I need, I'll try this setting and see how I get on.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: differences

Post by lbauer » Tue Aug 30, 2011 3:58 pm

Let me know if you have additional questions.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply