MAJOR problem with Get Latest Version

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

Moderator: SourceGear

Post Reply
JohnASchmitz
Posts: 12
Joined: Fri Apr 09, 2010 1:46 pm

MAJOR problem with Get Latest Version

Post by JohnASchmitz » Thu May 06, 2010 10:50 am

Hi,

I am trying to use Vault to get source up-to-date for a build. I used GetLatestVersion to recursively get all the files to a folder with older versions. Every file that has changed since the version in the folder is marked as Renegade or Needs Merge. When you use Show Differences, the changes from the current version of the file are marked as being different from the version in source control. This is the same handed-off repository with the date problems, but this seems to occur whether the file has the right date or not. The file history for one of the files shows the current version to be the same version that SourceSafe knows to be current.

All of the files with the problem are shared with other projects, but not all of the shared files show the problem.

John

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

Re: MAJOR problem with Get Latest Version

Post by lbauer » Thu May 06, 2010 11:34 am

Is the latest version in the repository? Do you want to overwrite all the files in the build folder? If so, have you tried doing a Get latest with Overwrite instead of Attempt Automatic Merge?

As to why the statuses don't seem right -- Vault may think those files have been modified because the baselines are out of sync, the timestamp has changed or if the working folder is shared with another user.

If you have more questions about this, I'd suggest we schedule a remote assist session where I can take a closer look. Send and email to sourcegear.com, Attn: Linda and we'll set something up. Please include a link to this forum post.
Linda Bauer
SourceGear
Technical Support Manager

JohnASchmitz
Posts: 12
Joined: Fri Apr 09, 2010 1:46 pm

Re: MAJOR problem with Get Latest Version

Post by JohnASchmitz » Mon May 10, 2010 9:22 am

Some explanation of the Vault caching helped clear up the issue. I consider this closed.

For anyone else that sees this, the core of the problem was getting the source out of Vault into a folder already containing source code that we got from the previous source control system. Vault did not have any baseline and actually thinks that differences in the older source are new modifications.

There are two ways to prevent this. The best way is to get the source from Vault into an empty folder if that is at all possible.

In some cases, we can't do that. In those cases, you need to use Linda's suggestion, and change from the default "Attempt Automatic Merge" setting to the "Overwrite" setting.

Thanks,
John

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

Re: MAJOR problem with Get Latest Version

Post by lbauer » Mon May 10, 2010 1:38 pm

You're a quick study. :D

Thanks for the update.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply