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.
Tony,
You have made the 1862 build now, so I got the binaries, and trying out
with our "strange" directory- and file-names. Unfortunately we use
non-us-ascii characters in directory- and file-names. Previous versions
(2.0.58d and earlier) handles these files/directories correctly.
- Fail: Importing modules, containing files/directories with name including
non-us-ascii chars in it
(cvs server: cannot lstat file á?rvĂ-ztĹ?rĹ?tĂĽkĂ?rfĂşrĂłgĂ?pe: No
such file or directory
No conflicts created by this import
*** ERRORS DURING THIS IMPORT ***)
- Fail: Checkout modules with name including non-us-ascii chars in it, if
it contains files/directories with name including non-us-ascii chars in it
(cvs -d :sspi:@localhost:/test checkout -P árvíztűrőtükörfúrógép (in
directory C:\work\local)
cvs server: Updating árvíztűrőtükörfúrógép
cvs server: cannot open directory /test/árvíztűrőtükörfúrógép: No
such file or directory
cvs server: skipping directory árvíztűrőtükörfúrógép
cvs.exe checkout: in directory .:
cvs.exe checkout: cannot open CVS/Entries for reading: No such file
or directory)
- Fail: Update modules with name including non-us-ascii chars in it,
(cvs update -P (in directory
C:\work\local\webtest\_ujdir_\Pres\01.Tanács\)
cvs server: Updating .
cvs server: cannot open directory
/test/webtest/_ujdir_/Pres/01.Tanács: No such file or directory
cvs server: skipping directory )
- Successfully adding, and commiting files with names including
non-us-ascii chars in it
- Successfully adding, and commiting files which included in a module with
names including non-us-ascii chars in it (with Recursive Add macro)
- Successfully commits modules with names including non-us-ascii chars in
it
- Successfully tagging modules/files with names including non-us-ascii
chars in it
I think, something wrong.
Best regards!
Zoltan Szathmáry