Hello, * On Fri, Apr 08, 2005 at 12:36:39PM +1000 Sisyphus wrote: > The FAQ says that Win32 cvs clients don't get along with Unix cvs > servers, and the mix should be avoided. Is that advice still correct ?
I use this constellation myself very often, and I do not have this problem. Thus, from my point of view, this seems not to be correct anymore. But I'm sure others will have to say more on this topic. Perhaps, this was meant for cvsnt clients? > I have cvs-1.11.19 (binaries obtained from cvshome website) on my > Windows 2000 box, and I have cvs-write permission to a sourceforge > project. With 'pserver' I can 'login', 'co' and 'update' - but I can't > 'commit' any changes I make. All I ever get is: > > cvs [server aborted]: "commit" requires write access to the repository > > Well .... I do have write access - I assume the problem is that fact > doesn't get established. No. The problem is that you did not read the sourceforge documentation correctly. ;-) Quoting http://sourceforge.net/cvs/?group_id=122047: "Anonymous CVS Access [... telling about pserver ...] Developer CVS Access via SSH [... telling about writing to cvs with ssh]" You might want to check out http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1#howtoaccess: "If you are a project developer and will be writing to the CVS repository, you will require an additional piece of software, an SSH client." I highly recommand you read the above mentioned web pages, they tell you all you need to set up cvs with sourceforge. Good luck, Spiro. -- Spiro R. Trikaliotis http://cbm4win.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs