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 firstname.lastname@example.org.
Arthur, >Did you upgrade the server and the client or just the server? Check >that there is no old cvs.exe in the WinCVS directory. >You may have to 'delete' the 'broken' fileattr.xml from the server. I upgraded the server to CVSNT 2.5.05, client to Wincvs 18.104.22.16884(march-hare.com Build 2784), and run 2.5.x server in 'unicode' mode, When I add a file, I got the following: cvs add -kb -- GTD81B_配置管理计划.doc (in directory G:\temp\tmp2\new temp\文档\) cvs [server aborted]: Couldn't open RCS file /StelcomRoot/new temp/ 文档/GTD81B_Ж#)Ж#)Ж#)Ж#)Ж#)Ж#)Ж#)Ж#)Ж#)Ж#)Ж#)Ж #).doc,v: Invalid argument When I run 2.5.x server in non 'unicode' mode , I got this: cvs add -kb -- GTD81B_配置管理计划.doc (in directory G:\temp\tmp2\new temp\文档\) cvs server: scheduling file `GTD81B_配置管理计划.doc' for addition cvs server: use 'cvs commit' to add this file permanently after commit, I got cvs commit -m "no message" -- GTD81B_配置管理计划.doc (in directory G:\temp\tmp2\new temp\文档\) RCS file: /StelcomRoot/new temp/文档/GTD81B_配置管理计划.doc,v done XML error at line 0: xmlEncodeEntitiesReentrant : input not UTF-8 Checking in GTD81B_配置管理计划.doc; /StelcomRoot/new temp/文档/GTD81B_配置管理计划.doc,v <-- GTD81B_配 置管理计划.doc initial revision: 1.1 done XML error at line 0: output conversion failed due to conv error, bytes 0xDC 0xC0 0xED 0xBC XML error at line 0: encoder error Unable to create D:/StelcomRoot/new temp/文档/CVS/fileattr.xml cvs server: cannot write /StelcomRoot/new temp/文档 /CVS/fileattr.xml: No such file or directory just the same problem as before. Seems CVSNT 2.5.x didn't fix this bug, and I cannot download free CVS suite 2008 or CVS suite 2008 trial version, Can I get a CVS suite 2008 trial version? Or will you fix bug 5555 in the next version of CVSNT, or any patch exist? Thanks so much, Wendy ***** CVS exited normally with code 0 ***** ***** CVS exited normally with code 0 ***** -----邮件原件----- 发件人: Arthur Barrett [mailto:arthur.barrett at march-hare.com] 发送时间: 2009年9月14日 18:08 收件人: ???; cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook 主题: RE: [cvsnt]write to fileattr.xml error when commit a file Wendy, > After I upgraded the CVSNT 2.5.05, the problem of the > fileattr.xml is still there. Did you upgrade the server and the client or just the server? Check that there is no old cvs.exe in the WinCVS directory. You may have to 'delete' the 'broken' fileattr.xml from the server. > > Upgrade the client and the server and the problem will go away, or > > upgrade the server to 2.5.05 and set the options as described in bug > > 5555. > > And also I cannot get the 'assumed > character set' for each type of client (CVSNT, non-CVSNT, etc). in > the 'compatibility options' tab. My mistake - 2.5.05 does NOT have bug fix 5555 - that fix is only in CVS Suite 2008. The bug does say that, but my comments in the e-mail misled you. If you upgrade the client then it should work OK - the problem is that the 'old' client does not send the codepage to the server - so the server make some assumptions which can easily be wrong in a multi-character set environment. You should: 1) run 2.5.x server in 'unicode' mode and 2.5.x clients Or 2) run 2.0.x server and clients in the identical character set *may* work Or 3) run 2.5.x server and 2.0.x clients with the server and client configured for the same character set *may* work Either way you will almost certainly need to 'delete' the old fileattr.xml from the server. This *may* cause some things like renamed files and watch/edit to misbehave in the short term. Let the group know if you need more clarification. Regards, Arthur Barrett