Problem maintaining cr/lf with soscmd 4.1

[aventi]

Hello,

I upgraded from 4.0.1 to 4.1 the other day.
My builds started failing.

I simply execute msdev (Visual Studio 6 sp4) against a .dsw file to build the whole project. All dependecies defined in .dsw.

Upon further investigation, it seems that my soscmd (4.1) is stripping the cr (\r) and in turn causing the file to not load into MS DEV. I confirmed this by 'getting' the file from the SOS gui and comparing the file after 'getting' with soscmd.

Tried reapplying the options in the gui client for end of line terminator, but that failed.

Any clues?
Desparate for a resolution. We are very much into command-line automation.

About to backtrack to 4.0.1.

[lbauer]

It looks like a bug, as the behavior was different in SOS 4.0. We think the behavior may depend on a combination of SOS and a particular version of the SourceSafe API.

We're investigating this further and should know more next week.

[Guest]

Thank you. I have uninstalled and gone back to 4.0.2.

FYI. We left the server at 4.1 and that was okay. Seems to be client side only.

[eparker]

I just ran into this same problem. Where can I get a copy of
4.0.2?

[lbauer]

We weren't able to reproduce this in-house. Are you using the SOS Windows or Linux Command Line Client?

Could you email me the command and copies a file that was affected. I'd like to see the one retrieved with the GUI client and the one retrieved with the CLC. Send the info to Linda at@ SourceGear.com.

In the email, ask me to send you a copy of the SOS 4.0.2 CLC.

[guest]

This is from chris.winslow@us.army.mil

We are running server 4.1 under Windows Server 2003 with clients on a variety of 2000/xp/redhat systems and are experiencing the loss of eol control with soscmd. When reverting to soscmd 4.0.2, the problem goes away.

We have some projects that were originally controlled with starteam by an outside organization. The bulk of the eol problems seem to be with these projects.

[Mikhail]

I also have this problem
It became after upgrade from 4.02 to 4.10

SOS Server 4.1 / Windows 2000, Visual SourceSafe 6.0d
SOS Client 4.1 Windows XP SP2, Visual SourceSafe 6.0d, Visual C++ 6.0SP5

it happens with all files in all projects, command is
D:\work\install\MI\src\cryptoapi>"C:\Program Files\SourceOffSite\soscmd.exe" -command GetFile -project "$/crypto api" -file "CryptoAPI.dsp" -time modificat
ion -soshome "D:\work\install\MI\src\cryptoapi" -server server2:8080 -name builder -password "UNI" -alias ssi -verbose

[lbauer]

The EOL problem is a known bug in the SOS 4.1 Command Line Client.

It will be fixed in SOS 4.1.2, due out in a few weeks.

[ngaida]

Has 4.1.2 been released (I don't see it on the download page).

Assuming it's been delayed, is there a new timeline?

[lbauer]

It hasn't been released yet. It's due out in a few weeks.