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.
TortoiseCVS works extremely well as a client. Some IDE/Editor programs like PeggyPro also work easily. ViewCVS will fairly easily work with Build 57J, and with Build 65 is you configure things properly. (read the history in ViewCVS mailing list). The copy of the repository will probably work, although you may have to manually edit the plain text files in the CVSROOT to correct the paths, then when CVSNT is running, check out CVSROOT, do the same changes, and commit them. Alternate try: Checkout a full copy of the repository from the Linux Box. Delete all the \CVS\ dirs in it. Then Add the whole thing to the new server. And finally, overwrite the newly created repo files (xxx,v) with the ones from the Linux box - that should put the history into each file. I believe the repository files are supposed to be the same format for CVS and CVSNT. If not: Check in a simple one line file to both the linux box and the new server. Then compare the contents of the two new repository xxx,v files. You can use an IDE/Edittor with multifile replace (PeggyPro, CodeWright...) to adjust a copy of the repository files for use in the new repository. Good luck! - Paul Mark Stuhr <mark at nolo.com> wrote:We are considering doing what the subject line says and are doing some testing. We've successfully got CVSNT up and running. I'm trying to run it with only ssspi for logins. This seems to mean that we can only use wincvs beta 1.3 clients is that correct?? Now for the meaty thing. Is it possible to commit all existing changes outstanding in our linux repository and then just move the whole repository over to the Win2K server that's running cvsnt?? If possible what steps would need to be made after the copy to get the repository up and running and available to all clients?? (Mainly will I have to recreate all the repository routes manually in the cvsnt control panel??) I've tried a version of this (just moving over the CVSROOT folder and one repository and whenever I try to do anything with that migrated repository there's a message in the terminal window of wincvs that it can't find Cannot access E:/cvsrepo/ql_biz_2004_win/CVSROOT No such file or directory That looks like correct directory structure on the cvsnt server except there's no CVSROOT folder inside the repository folder?? If it's not possible to move the repository files over is there some other method for migrating this information in a way that wouldn't take too much work and would allow us to keep all of the version history of the existing projects/files?? Thanks Mark Stuhr Director of Inf. Tech. Nolo mark at nolo.com _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs --------------------------------- Post your free ad now! Yahoo! Canada Personals -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.cvsnt.org/pipermail/cvsnt/attachments/20030114/4c52f3ee/attachment.html