Re: CVSROOT must be an absolute pathname problem
Ganeshram Madhavan writes: > > But commit is capable of working with absolute file names, and *NOT* > other commands Not in client/server mode: $ cvs -d:fork:/tmp/cvstest ci -m. /tmp/CVSROOT/loginfo absolute pathname `/tmp/CVSROOT' illegal for server As far as I know, *all* CVS commands work fine with absolute paths in local mode but none of them work with absolute paths in client/server mode. -Larry Jones Hello, I'm wondering if you sell kegs of dynamite. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVSROOT must be an absolute pathname problem
Mike Ayers writes: > > Larry Jones wrote: > > > I don't think so -- I'm talking about when you install Cygwin stuff, on > > the "Select Root Install Directory" screen, there's a "Default Text File > > Type" check-box that allows you to select "DOS" or "Unix". Provided you > > select "DOS", the Cygwin cvs interoperates just fine with WinCVS. > > Whoa, that's new! You sound like you've verified this, yes? To a certain extent. They can certainly interoperate in a working directory when using client/server mode. Local mode is a bit trickier since WinCVS uses native DOS paths and Cygwin uses it's own mapped file system paths, but it could probably be made to work with a bit of effort. But, as I've said before, there's no reason to do so -- WinCVS comes with a fine command-line CVS (cvs.exe), so there's no reason to use Cygwin CVS too. -Larry Jones It's either spectacular, unbelievable success, or crushing, hopeless defeat! There is no middle ground! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVSROOT must be an absolute pathname problem
Larry Jones wrote: I don't think so -- I'm talking about when you install Cygwin stuff, on the "Select Root Install Directory" screen, there's a "Default Text File Type" check-box that allows you to select "DOS" or "Unix". Provided you select "DOS", the Cygwin cvs interoperates just fine with WinCVS. Whoa, that's new! You sound like you've verified this, yes? /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVSROOT must be an absolute pathname problem
Mike Ayers writes: > > You are thinking of text mode mounts. That has been mentioned a few > times here, as have a few other prospects for cooperative behavior, > but I have never seen a report of anyone successfully configuring a > system in which Cygwin CVS and a Windows style CVS were able to work > on the same repository. Until we do get confirmation (and > instructions), I think it is best to say that it hasn't been done and > possibly can't be done. I just want people to understand that, if > they want to try to make it happen, they're in for a very bumpy ride. I don't think so -- I'm talking about when you install Cygwin stuff, on the "Select Root Install Directory" screen, there's a "Default Text File Type" check-box that allows you to select "DOS" or "Unix". Provided you select "DOS", the Cygwin cvs interoperates just fine with WinCVS. -Larry Jones Yep, we'd probably be dead by now if it wasn't for Twinkies. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVSROOT must be an absolute pathname problem
Larry Jones wrote: Mike Ayers writes: I do not think it is possible to use WinCVS and Cygwin compiled CVS on the same sandbox. Cygwin CVS expects ALL files to be in Unix mode. While WinCVS can check out sandbox files with Unix line endings, it should still expect the CVS/* files to use Windows line endings. You must choose one tool or the other. I believe it is possible, provided you configure Cygwin to use DOS line endings when you install CVS. (There may be a way to specify DOS line endings at run-time, too; I don't know a whole lot about Cygwin). Conversely, WinCVS comes with a command-line CVS; you can just use it directly (by adding the WinCVS directory to your PATH) rather than using the Cygwin version. You are thinking of text mode mounts. That has been mentioned a few times here, as have a few other prospects for cooperative behavior, but I have never seen a report of anyone successfully configuring a system in which Cygwin CVS and a Windows style CVS were able to work on the same repository. Until we do get confirmation (and instructions), I think it is best to say that it hasn't been done and possibly can't be done. I just want people to understand that, if they want to try to make it happen, they're in for a very bumpy ride. /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVSROOT must be an absolute pathname problem
Mike Ayers writes: > > I do not think it is possible to use WinCVS and Cygwin compiled CVS > on the same sandbox. Cygwin CVS expects ALL files to be in Unix mode. > While WinCVS can check out sandbox files with Unix line endings, it > should still expect the CVS/* files to use Windows line endings. You > must choose one tool or the other. I believe it is possible, provided you configure Cygwin to use DOS line endings when you install CVS. (There may be a way to specify DOS line endings at run-time, too; I don't know a whole lot about Cygwin). Conversely, WinCVS comes with a command-line CVS; you can just use it directly (by adding the WinCVS directory to your PATH) rather than using the Cygwin version. -Larry Jones I've got an idea for a sit-com called "Father Knows Zilch." -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVSROOT must be an absolute pathname problem
Hi Mark, I'd advise to just use the CVSNT.exe file instead. It's dump-in-a-folder installable, and much more windows friendly -- for example, all the repository settings can be specified in the registry instead of environment variables (which are a total pain to modify globally in 98 _and_ 2000). Plus you will never run into the CR-LF line termination issues that people sometimes get with cygwin CVS when they choose the wrong setting. It also has some little things like using "cvs pass" will bring up asterixes as you type. cheers, matt -Original Message- Thank-you. After resetting CVSROOT (CVSROOT=:local:/cygdrive/c/cygwin/home/Mark/src/master), cvs init returned the following: cvs init: syntax error in /cygdrive/c/cygwin/home/Mark/src/master/CVSROOT/config' is missing '=' Subsequent cvs init's from c:/ runs without error - but ONLY in c:/ Performing a cvs init or any other cvs command from any other directory continues to render: GANDALF:/cygdrive/c/ensignInternet> cvs up cvs update: CVSROOT must be an absolute pathname (not `c:\cygwin\home\Mark\src\m')ter cvs update: when using local access method. '.s [update aborted]: Bad CVSROOT: `:local:c:\cygwin\home\Mark\src\master I am not sure why the "ter" shows up following the close paren above. And the .s is confusing as well. Mark. -Original Message- From: Larry Jones [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 9:35 AM To: Mark Scoville Cc: [EMAIL PROTECTED] Subject: Re: CVSROOT must be an absolute pathname problem Mark Scoville writes: > > GANDALF:/cygdrive/c> cvs init > cvs init: CVSROOT must be an absolute pathname (not > `c:/cygwin/home/Mark/src/master') > cvs init: when using local access method. > cvs [init aborted]: Bad CVSROOT: `:local:c:/cygwin/home/Mark/src/master'. Try using ":local:/cygdrive/c/cygwin/home/Mark/src/master" instead. -Larry Jones I don't need to do a better job. I need better P.R. on the job I DO. -- Calvin -- ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs End of Info-cvs Digest, Vol 1, Issue 2132 * ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVSROOT must be an absolute pathname problem
Mark Scoville wrote: I removed the directories and did a new checkout on the command line (bash) and that did the trick! Thanks. Now WinCvs is confused. What is the trick in WinCvs to teach it better (UNIX - CR/LF) manners? I did uninstall it and reinstalled it hoping it would pick up the environment more intelligently, but it looks like it retained its previous settings. I do not think it is possible to use WinCVS and Cygwin compiled CVS on the same sandbox. Cygwin CVS expects ALL files to be in Unix mode. While WinCVS can check out sandbox files with Unix line endings, it should still expect the CVS/* files to use Windows line endings. You must choose one tool or the other. /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: CVSROOT must be an absolute pathname problem
I removed the directories and did a new checkout on the command line (bash) and that did the trick! Thanks. Now WinCvs is confused. What is the trick in WinCvs to teach it better (UNIX - CR/LF) manners? I did uninstall it and reinstalled it hoping it would pick up the environment more intelligently, but it looks like it retained its previous settings. -m- -Original Message- From: Larry Jones [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 10:28 AM To: Mark Scoville Cc: [EMAIL PROTECTED] Subject: Re: CVSROOT must be an absolute pathname problem Mark Scoville writes: > > cvs init: syntax error in > /cygdrive/c/cygwin/home/Mark/src/master/CVSROOT/config' is missing '=' That implies that you already had a CVSROOT/config file (normally, init would have create it), the contents of which are not valid. > Performing a cvs init or any other cvs command from any other directory > continues to render: > > GANDALF:/cygdrive/c/ensignInternet> cvs up > cvs update: CVSROOT must be an absolute pathname (not > `c:\cygwin\home\Mark\src\m')ter > cvs update: when using local access method. > '.s [update aborted]: Bad CVSROOT: `:local:c:\cygwin\home\Mark\src\master If you're running in a checked-out directory, CVS uses the root stored in the CVS/Root file rather than what the $CVSROOT environment variable is set to. The above messages show the classic symptoms of line-ending problems. If you're using both cynwin CVS and WinCVS, you need to make sure that both are set to use the same line ending conventions (either DOS or Unix); right now, it looks like they're different. -Larry Jones It's hard to be religious when certain people are never incinerated by bolts of lightning. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVSROOT must be an absolute pathname problem
Mark Scoville writes: > > cvs init: syntax error in > /cygdrive/c/cygwin/home/Mark/src/master/CVSROOT/config' is missing '=' That implies that you already had a CVSROOT/config file (normally, init would have create it), the contents of which are not valid. > Performing a cvs init or any other cvs command from any other directory > continues to render: > > GANDALF:/cygdrive/c/ensignInternet> cvs up > cvs update: CVSROOT must be an absolute pathname (not > `c:\cygwin\home\Mark\src\m')ter > cvs update: when using local access method. > '.s [update aborted]: Bad CVSROOT: `:local:c:\cygwin\home\Mark\src\master If you're running in a checked-out directory, CVS uses the root stored in the CVS/Root file rather than what the $CVSROOT environment variable is set to. The above messages show the classic symptoms of line-ending problems. If you're using both cynwin CVS and WinCVS, you need to make sure that both are set to use the same line ending conventions (either DOS or Unix); right now, it looks like they're different. -Larry Jones It's hard to be religious when certain people are never incinerated by bolts of lightning. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: CVSROOT must be an absolute pathname problem
Thank-you. After resetting CVSROOT (CVSROOT=:local:/cygdrive/c/cygwin/home/Mark/src/master), cvs init returned the following: cvs init: syntax error in /cygdrive/c/cygwin/home/Mark/src/master/CVSROOT/config' is missing '=' Subsequent cvs init's from c:/ runs without error - but ONLY in c:/ Performing a cvs init or any other cvs command from any other directory continues to render: GANDALF:/cygdrive/c/ensignInternet> cvs up cvs update: CVSROOT must be an absolute pathname (not `c:\cygwin\home\Mark\src\m')ter cvs update: when using local access method. '.s [update aborted]: Bad CVSROOT: `:local:c:\cygwin\home\Mark\src\master I am not sure why the "ter" shows up following the close paren above. And the .s is confusing as well. Mark. -Original Message- From: Larry Jones [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 9:35 AM To: Mark Scoville Cc: [EMAIL PROTECTED] Subject: Re: CVSROOT must be an absolute pathname problem Mark Scoville writes: > > GANDALF:/cygdrive/c> cvs init > cvs init: CVSROOT must be an absolute pathname (not > `c:/cygwin/home/Mark/src/master') > cvs init: when using local access method. > cvs [init aborted]: Bad CVSROOT: `:local:c:/cygwin/home/Mark/src/master'. Try using ":local:/cygdrive/c/cygwin/home/Mark/src/master" instead. -Larry Jones I don't need to do a better job. I need better P.R. on the job I DO. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVSROOT must be an absolute pathname problem
Mark Scoville writes: > > GANDALF:/cygdrive/c> cvs init > cvs init: CVSROOT must be an absolute pathname (not > `c:/cygwin/home/Mark/src/master') > cvs init: when using local access method. > cvs [init aborted]: Bad CVSROOT: `:local:c:/cygwin/home/Mark/src/master'. Try using ":local:/cygdrive/c/cygwin/home/Mark/src/master" instead. -Larry Jones I don't need to do a better job. I need better P.R. on the job I DO. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs