Problems checking in shared files from command line.

mali · Post by **mali** » Mon Mar 01, 2004 3:54 pm

Hi,

I'm unable to check in checked out files that have a share link via the command line.

Steps:
1) Check out a shared file.
2) Make changes and commit using command line.

The log file lists the share path for this file where the checkout did NOT take place and states that this file caused the transaction to fail & I must merge my working copy with the newest version before check in.

Note: I can go into Vault and click on the Commit button to check these files in. Also, this is not an issue with files that do not have a share link. I can check in modified files that do not have a share link via the same command line.

Any clarification on this will be appreciated, thanks.
-ma
Vault Version 1.2.3(758)[/b]

Post by **jclausius** » Mon Mar 01, 2004 5:04 pm

mali:

what was the command used to check out the file?

what is the working folder set to (vault.exe listworkingfolders -user username -password pwd -repository repname -host hostname)?

on you local machine, in which directory were the changes made? is it the same directory listed in listworkingfolders?

what does your checkin command look like?

Guest · Post by **Guest** » Tue Mar 02, 2004 1:19 pm

Jeff,

Here is the info you requested:

Command used to check out file:
%vault% checkout %v_tree%/Common/Version/Version.js %v_cons% %v_logs%

where:
vault="C:\Program Files\SourceGear\Vault Client\vault.exe"
v_tree=$/xyz
v_cons=-user %v_user% -password %v_pass% -host %v_host% -repository %v_repo%
v_logs=-out vault.log

Working directory:
d:\...\Common\Version. This is where Version.js was checked out to, edited, and checked in from.

Check in command:
%vault% commit %v_tree%/Common/Version/Version.js %v_cons% %v_Comm% %v_logs%

where:
v_Comm=-comment "Version incremented by build automation %ver%."

Again, these commands work fine for other files in the same Vault folder. The only difference being that those files do not have a share link in Vault.

Thank you for looking into this.
-ma

Post by **jclausius** » Tue Mar 02, 2004 2:29 pm

ok. thanks.

i currently have my environment in vault 2.0 to work on some other issues. i'll need some time before i can reset back to vault 1.2.3. i'll update you on my progress.

please note, there were problems fixed in vault 2, related to the command line client refreshing client folder. it is possible the errors you are seeing are related.