SOS 3.5.3 BUG Renegade status on Shared members

davekrekel · Post by **davekrekel** » Wed Feb 16, 2005 8:47 am

I have a member that is shared between two folders. Both folders have the same working directory. Both folders are in a same project.

When I perform a get latest on the project. SOS pulls down the shared member from the first folder into the common working directory. Then SOS pulls the same shared member in the second folder to the same working directory. It set the status of the shared member on the first folder to a renegade status.

If you go back to the first folder and do a manual GetLatest. It corrects the renegade status on the member first folder but then the member in the second folder gets set to a renegade status.

Is there a correction for this problem? Is this resolved in 4.1?

Thanks Dave K

lbauer · Post by **lbauer** » Wed Feb 16, 2005 3:09 pm

Use a different working folder for each SOS project/folder.

SOS compares the timestamp of the file in the working directory with the time it was retrieved from the SOS Server. If the timestamp has changed, SOS assumes the file has been modified. A file that is modified but not checked out is renegade.

Since you are doing gets from two different projects into the same working folder, the timestamp on the file is changing relative to the time it was retrieved from the previous folder in SOS.