Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Hi all.
This I'm fairly cetain is a bug. :-)
When using a 2.5.03 (Scorpio) Build 2151
or a 2.5.02 (Servalan) Build 2064 client then automated
patching of Unicode files saved in UTF-16 format does
not work.
To reproduce do the following:
- prepare a UTF-16 file with a single line of text.
- add the file to a CVS module as a Unicode file.
- Checkout the same file to another sandbox on the
same client computer.
- In one sandbox add another line of text and commit.
- In the other sandbox do a cvs update.
Now you'll get a message about the file checksum
being invalid and it being refetched from the server.
If you do a change in both sandboxes to force CVSNT
to automatically merge these two files it will mess up the
file contents completely.
This has been reproduced in the following setup:
- Server running Windows 2003 Server SP1 and
2.5.03 (Scorpio) Build 2151.
- Clients running Windows XP Professional SP2
and one of the CVSNT versions mentioned above.
If an older 2.0.62.1817. version of the client is used
everything works ok.
If an older 2.0.58d. version of the server is used then
the problem is similar but not exactly the same. But that
is probably a different and already solved issue.
Any suggestions on what to do about this? It is causing
problems for us as the current stable TortoiseCVS version
comes with this buggy CVSNT client version and so when
any of our developers decides to update their TortoiseCVS
they run into the same bug and have to revert back to the
older version...
Best regards,
Jurko Gospodnetiæ