RE: strange problems with cvs
Just a note to inform you that I've downgrade my cygwin dll (to 1.5.11-1), and now cvs is working perfectly again. So, the problem is in the new dll release! Nuno -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: strange problems with cvs
I'm using pserver auth Don't -- use ssh. If you set up your router/firewall correctly, you and whomever you grant an account to can access your CVS server from anywhere on the Internet. It's *really* useful. I use the php.net cvs server :) Isn't my choice... and the cygwin is installed with *DOS* line-endings. I use Cygwin with DOS line endings and the Cygwin CVS client. Everything works fine. I think it might be cause of the release of the lastest dll version. (I update cygwin often..) I very much doubt it. I've used/ been using DOS, Windows NT, GNU/Linux, BSD, DJGPP, Cygwin, and CVS for several years new, and any CVS problems I've had were always my fault. The problem is that it is working now.. and I haven't do anything... really strange... Thanks anyway, Nuno -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: strange problems with cvs
Nuno Lopes wrote: > I use CVS with cygwin a long time ago, but after a recent updte it stoped > working. ... I find it is better to have a separate computer as the CVS server; I use GNU/Linux. > I'm using pserver auth Don't -- use ssh. If you set up your router/firewall correctly, you and whomever you grant an account to can access your CVS server from anywhere on the Internet. It's *really* useful. I wrote a Perl convenience script 'cvsenv' that I can launch from Bash that sets up the client end of things. I also figured out how to use Unix groups to isolate multiple CVS repositories on one server; the Perl script is called 'dvs'. You can download both of them here: http://www.holgerdanske.com/dpchrist/source.html > and the cygwin is installed with *DOS* line-endings. I use Cygwin with DOS line endings and the Cygwin CVS client. Everything works fine. > When I try to do something with cvs -1.11.17- (cvs up, cvs diff, > etc..) it simply returns: ": no such repository" > > Normally if I close cygwin, run the setup again (without installing > anything) and opening cygwin again fixes the problem. > > If I do a fresh checkout, it will checkout the files with *unix* > file-endings, which isn't what I asked for.. > > Does anyone knows whats the problem here? Get this book: http://cvsbook.red-bean.com/ > I think it might be cause of the release of the lastest dll > version. (I update cygwin often..) I very much doubt it. I've used/ been using DOS, Windows NT, GNU/Linux, BSD, DJGPP, Cygwin, and CVS for several years new, and any CVS problems I've had were always my fault. HTH, David -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: strange problems with cvs
[snip] > I have vim, but I still like to use notepad, which only works > with \r\n... Dude, nobody *likes* to use notepad ;-). Google for a little gem called "Textpad", and don't look back. -- Gary R. Van Sickle -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: strange problems with cvs
Nuno Lopes kirjoitti: I use CVS with cygwin a long time ago, but after a recent updte it stoped working. I'm using pserver auth and the cygwin is installed with *DOS* line-endings. When I try to do something with cvs -1.11.17- (cvs up, cvs diff, etc..) it simply returns: ": no such repository" Normally if I close cygwin, run the setup again (without installing anything) and opening cygwin again fixes the problem. If I do a fresh checkout, it will checkout the files with *unix* file-endings, which isn't what I asked for.. Does anyone knows whats the problem here? I think it might be cause of the release of the lastest dll version. (I update cygwin often..) Seems like you have encountered fancy EOL problem. To be safe use unix line-endings since CVS is pretty picky about those. And of course if you want to use DOS type line endings, use real win32 version of CVS. It had always worked, so there might be some change in the code that caused this... Anyway, the files in the cvs server use the unix EOL, but on my pc they use the win EOL. But cvs used to handle this for me.. This might be due difference between binary/textmode mounts in cygwin... Maybe they change for a reason or another in some of your updates... I've encountered numerous problems with CVS due the line-endings... Any decent text editor should be handle both CR+LF or LF/CR only line-endings and preserving existing ones... If yours doesn't it's time to upgrade... I have vim, but I still like to use notepad, which only works with \r\n... Is there anything I can do to help solving this problem ASAP? Getting a bit offtopic, but I personally use scite, or to be precise wscite, scintilla based editor. Small, extremely lightweight and fast, has decent code colouring, block wrapping and such. And best of all, works well with different line-endings. Of course there is some good alternatives in Cygwin distribution also... -- Jani Tiainen -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: strange problems with cvs
I use CVS with cygwin a long time ago, but after a recent updte it stoped working. I'm using pserver auth and the cygwin is installed with *DOS* line-endings. When I try to do something with cvs -1.11.17- (cvs up, cvs diff, etc..) it simply returns: ": no such repository" Normally if I close cygwin, run the setup again (without installing anything) and opening cygwin again fixes the problem. If I do a fresh checkout, it will checkout the files with *unix* file-endings, which isn't what I asked for.. Does anyone knows whats the problem here? I think it might be cause of the release of the lastest dll version. (I update cygwin often..) Seems like you have encountered fancy EOL problem. To be safe use unix line-endings since CVS is pretty picky about those. And of course if you want to use DOS type line endings, use real win32 version of CVS. It had always worked, so there might be some change in the code that caused this... Anyway, the files in the cvs server use the unix EOL, but on my pc they use the win EOL. But cvs used to handle this for me.. I've encountered numerous problems with CVS due the line-endings... Any decent text editor should be handle both CR+LF or LF/CR only line-endings and preserving existing ones... If yours doesn't it's time to upgrade... I have vim, but I still like to use notepad, which only works with \r\n... Is there anything I can do to help solving this problem ASAP? Thanks, Nuno -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: strange problems with cvs
Nuno Lopes kirjoitti: Hi, I use CVS with cygwin a long time ago, but after a recent updte it stoped working. I'm using pserver auth and the cygwin is installed with *DOS* line-endings. When I try to do something with cvs -1.11.17- (cvs up, cvs diff, etc..) it simply returns: ": no such repository" Normally if I close cygwin, run the setup again (without installing anything) and opening cygwin again fixes the problem. If I do a fresh checkout, it will checkout the files with *unix* file-endings, which isn't what I asked for.. Does anyone knows whats the problem here? I think it might be cause of the release of the lastest dll version. (I update cygwin often..) Seems like you have encountered fancy EOL problem. To be safe use unix line-endings since CVS is pretty picky about those. And of course if you want to use DOS type line endings, use real win32 version of CVS. I've encountered numerous problems with CVS due the line-endings... Any decent text editor should be handle both CR+LF or LF/CR only line-endings and preserving existing ones... If yours doesn't it's time to upgrade... (Of course there might be problem in bin/textmode mounts) cygcheck output would do good here... -- Jani Tiainen -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
