I recently branched a project in which there are a number of files which have their EOL conversion set to "Unix (LF)". In the new branch, all these files have their EOL conversion set to "None". I'm using Vault 2.0.3 (both Server and Client).
When I look at the History for the file in the new branch, it correctly shows the entry for "EOL Conversion changed to Unix (LF)", and there are no subsequent entries for any changes to the EOL conversion.
Is this a known bug? Is there a workaround? (It's broken our build process, and it's going to hit us again when we have to do our next branch in the next week or two.)
On a related note: when getting the latest version, is there any way to override the file and client settings and specify a particular EOL conversion? If not, I'd like to submit it as a feature request; it would make it much easier to solve EOL problem, by just forcing it when getting source for a platform that needs a particular conversion..
Branched file loses EOL conversion property
Moderator: SourceGear
It looks like a bug - we'll check it out and add it to the bug DB after we verify it.
For the 2nd question: There is a very specific and limited way to override EOL for a given user. If a file's EOL setting is currently "Native", there is a setting in Tools->Options->Local Files that allows you to override the actual Native EOL with a specific EOL setting. For example, if you are on a windows box, but want to retrieve files to a Unix drive using the Unix EOL setting, this will allow you to accomplish that. However, it only works on file EOL's of Native, so it probably won't help you with the setting of None.
For the 2nd question: There is a very specific and limited way to override EOL for a given user. If a file's EOL setting is currently "Native", there is a setting in Tools->Options->Local Files that allows you to override the actual Native EOL with a specific EOL setting. For example, if you are on a windows box, but want to retrieve files to a Unix drive using the Unix EOL setting, this will allow you to accomplish that. However, it only works on file EOL's of Native, so it probably won't help you with the setting of None.
More details
While manually re-setting all the files to Unix/LF, I found that files with certain extensions (.sh, .cfg, .txt) retained their Unix/LF designation, but files with no extension or with other extensions did not.
The extensions for which branched files retained their Unix/LF designation were all listed in the set of mergeable file types in the repository options in the Admin Tool.
So to mitigate the problem for my next branch, I've added every extension I've encountered to the set of mergeable file types for all repositories. Unfortunately, there does not seem to be any way to mitigate the problem for files with no extension (of which we have quite a few).
The extensions for which branched files retained their Unix/LF designation were all listed in the set of mergeable file types in the repository options in the Admin Tool.
So to mitigate the problem for my next branch, I've added every extension I've encountered to the set of mergeable file types for all repositories. Unfortunately, there does not seem to be any way to mitigate the problem for files with no extension (of which we have quite a few).