Re: pserver login problem to Linux from Win2k

2002-11-01 Thread david
> Ok, got this figured out.  Just incase anyone wants to know:
> 
> Here's what is happening:
> 1. J: is a networked drive connected to my home directory on our Linux
> server via Samba

If that networked drive contains the repository, that's a bad idea.
Most cases of CVS file corruption seem to happen when somebody has
remote-mounted the repository.

If it's your sandbox, well, that's not the most efficient way to
do things, but it shouldn't cause problems.

> 2. I started doing my work telneted into the server and got checkin and
> checkouts working fine
> 3. CVS creates the directory CVS inside your workspace when you do your
> checkout; it also creates the file Root in that directory set to your
> CVSROOT where you got your files checked out from.  In my case this CVS/Root
> looked like '/swdev/cvsroot'

Right.

> 4. I then tried to checkin some changes via CVS in a DOS box on my local
> machine, with CVSROOT=:pserver:derosier@engswdev:/swdev/cvsroot
> These failed with a message of:
> cvs commit: ignoring CVS/Root because it specifies a non-existent repository
> /swdev/cvsroot
>
Right.
 
> Reason: CVS stores your CVS Root in the file Root off of the subdirectory
> CVS in you project's working directory.  It uses this file to determine
> where the files should be checked back into, ignoring the actual CVSROOT
> variable.

This is a feature.  Many CVS users have source checked out from multiple
repositories, and if the CVSROOT variable was not overridden by
CVS/Root that would be a real pain.

  This is normally not a problem, but it is in the case where you
> do the check out locally, then do the edits and try to check them in
> remotely (since this is a samba network drive to my windows 2k machine)
> using the pserver method.  In this case it fails because CVS/Root has the
> "wrong" CVSROOT string.
>
Right.  Assuming you're on the command line, you can specify the
CVSROOT variable on the command line.  This is a pain, and is why
CVS/Root overrides CVSROOT.
 
> New question:  Is there an easy way to fix this problem, so I can
> transparently use CVS in the same working directory both remotely and
> locally?
>
Nope.  Not that you should be casually switching back between Windows
and Unix anyway, since you'll likely eventually cause line-ending
problems by accident.
 
> Basically, my current "fix" is to only use one method, ie only do my work
> remotely using pserver.
> 
That sounds like an excellent idea to me, and the correct thing to do.

-- 
Now building a CVS reference site at http://www.thornleyware.com
[EMAIL PROTECTED]



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



RE: pserver login problem to Linux from Win2k

2002-10-31 Thread R P Herrold
On Fri, 1 Nov 2002, Shabbir Poonawala wrote:

> Somone please unsubscribe me.

As I pointed out off list, you are subscribed under another 
address than is being delivered to you.  We CANNOT see what 
address you are receiving email from -- the Received header 
chain which is ONLY in the piece ultimately delivered to you 
shows that (assuming RFC 2821 compliant MTA's are at each step 
of the delivery chain.)

You, and only you can see that address, and remove yourself.

-- Russ Herrold



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



RE: pserver login problem to Linux from Win2k

2002-10-31 Thread Shabbir Poonawala
Somone please unsubscribe me.




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: pserver login problem to Linux from Win2k

2002-10-31 Thread Mike Ayers
Kaz Kylheku wrote:

On Thu, 31 Oct 2002, Steve deRosier wrote:



Here's what is happening:
1. J: is a networked drive connected to my home directory on our Linux
server via Samba


You can't do that, because Linux and Windows don't agree on the
representation of text files.  This affects the treatment of text
documents on update and commit, and also the representation of the CVS/
administrative files.


	Also, you should always use native drives both for your sandbox and 
repository.  Generally speaking, networked drives within their native 
systems (NFS across Unix clones, SMB between Windows boxes) can be 
considered native.  Anything that crosses OS architectures (especially 
Unix/Windows) is bad.

So even if you solve the location non-transparency problem by using
a CVSROOT that works everywhere, you still have this problem.


New question:  Is there an easy way to fix this problem, so I can
transparently use CVS in the same working directory both remotely and
locally?


	This is not a "problem", so much as an architectural fact.  Unix and 
Windows do not agree on what constitutes a text file.  It is 
impossible for them to work together without some sort of intermediary.


/|/|ike




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs


RE: pserver login problem to Linux from Win2k

2002-10-31 Thread Steve deRosier
Well, I don't know that I "can't do that", considering that it works just
great for me.  Though the editor that I'm using on my Win2k box (SNiFF+)
understands UNIX line endings and has an option to save as Win/DOS, Mac, or
UNIX line endings (which is of course what I have selected).  So my code
files get edited properly.

I assume that the client CVS program actually contacts the server CVS
program when a checkout or checkin is done.  So...presumably it is the
server CVS that handles the writing of the administrative files, so I would
assume the integrity of the line endings would stay intact (UNIX style).  Am
I assuming too much?

Unfortunately the two-sandbox thing doesn't work with the tools I'm using.
But since I seem to be perfectly functional if I choose to do one or the
other (local or remote), but not both, things workout fine.  I just wanted
to know if there was a way I could do both (have my cake and eat it too).
See...the other two people in my development team will only use Win2k but as
I'm very much a Linux person I'd rather have the option of doing both.  But
if not, oh well.

The biggest problem was that I tried getting each piece up and running
independently first than tried to get them to work together.  Usually is a
great idea to make sure two parts work by themselves first.  Who knew? :)

- Steve


> -Original Message-
> From: Kaz Kylheku [mailto:kaz@;footprints.net]On Behalf Of Kaz Kylheku
> Sent: Thursday, October 31, 2002 4:12 PM
> To: Steve deRosier
> Cc: Shankar Unni; CVS Discussion List
> Subject: Re: pserver login problem to Linux from Win2k
>
>
> On Thu, 31 Oct 2002, Steve deRosier wrote:
>
> > Here's what is happening:
> > 1. J: is a networked drive connected to my home directory on our Linux
> > server via Samba
>
> You can't do that, because Linux and Windows don't agree on the
> representation of text files.  This affects the treatment of text
> documents on update and commit, and also the representation of the CVS/
> administrative files.
>
> So even if you solve the location non-transparency problem by using
> a CVSROOT that works everywhere, you still have this problem.
>
> > New question:  Is there an easy way to fix this problem, so I can
> > transparently use CVS in the same working directory both remotely and
> > locally?
>
> You can simply maintain two separate sandboxes.  To propagate changes
> from one to the other, commit in one, and update in the other.
>



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: pserver login problem to Linux from Win2k

2002-10-31 Thread Kaz Kylheku
On Thu, 31 Oct 2002, Steve deRosier wrote:

> Here's what is happening:
> 1. J: is a networked drive connected to my home directory on our Linux
> server via Samba

You can't do that, because Linux and Windows don't agree on the
representation of text files.  This affects the treatment of text
documents on update and commit, and also the representation of the CVS/
administrative files.

So even if you solve the location non-transparency problem by using
a CVSROOT that works everywhere, you still have this problem.

> New question:  Is there an easy way to fix this problem, so I can
> transparently use CVS in the same working directory both remotely and
> locally?

You can simply maintain two separate sandboxes.  To propagate changes
from one to the other, commit in one, and update in the other.



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



RE: pserver login problem to Linux from Win2k

2002-10-31 Thread Steve deRosier
Ok, got this figured out.  Just incase anyone wants to know:

I'm using a CVS binary from cvshome.org's download pages.  Specially the one
from:
http://www.cvshome.org/dev/codewindow.html

I did define the HOME environment variable and now it's creating the
.cvspass properly.

But still:

J:\projects\ORHwBringUp>cvs ci -m "mycvstry" Makefile
cvs commit: in directory .:
cvs commit: ignoring CVS/Root because it specifies a non-existent repository
/swdev/cvsroot
cvs commit: in directory .:
cvs commit: ignoring CVS/Root because it specifies a non-existent repository
/swdev/cvsroot
cvs commit: in directory .:
cvs commit: ignoring CVS/Root because it specifies a non-existent repository
/swdev/cvsroot

Here's what is happening:
1. J: is a networked drive connected to my home directory on our Linux
server via Samba
2. I started doing my work telneted into the server and got checkin and
checkouts working fine
3. CVS creates the directory CVS inside your workspace when you do your
checkout; it also creates the file Root in that directory set to your
CVSROOT where you got your files checked out from.  In my case this CVS/Root
looked like '/swdev/cvsroot'
4. I then tried to checkin some changes via CVS in a DOS box on my local
machine, with CVSROOT=:pserver:derosier@engswdev:/swdev/cvsroot
These failed with a message of:
cvs commit: ignoring CVS/Root because it specifies a non-existent repository
/swdev/cvsroot

Reason: CVS stores your CVS Root in the file Root off of the subdirectory
CVS in you project's working directory.  It uses this file to determine
where the files should be checked back into, ignoring the actual CVSROOT
variable.  This is normally not a problem, but it is in the case where you
do the check out locally, then do the edits and try to check them in
remotely (since this is a samba network drive to my windows 2k machine)
using the pserver method.  In this case it fails because CVS/Root has the
"wrong" CVSROOT string.

New question:  Is there an easy way to fix this problem, so I can
transparently use CVS in the same working directory both remotely and
locally?

Basically, my current "fix" is to only use one method, ie only do my work
remotely using pserver.

Thanks,
- Steve

> -Original Message-
> From: Shankar Unni [mailto:shankar@;cotagesoft.com]
> Sent: Wednesday, October 30, 2002 11:35 AM
> To: 'Steve deRosier'
> Subject: RE: pserver login problem to Linux from Win2k
>
>
> Looks like you should do these operations in a clean area.
>
> Also, which Windows CVS client are you using? The CVSNT client? Or the
> Cygwin CVS client? Try defining a HOME environment so that it has
> forward slashes instead of backslashes.  (set HOME=c:/).
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:info-cvs-admin@;gnu.org] On Behalf
> Of Steve deRosier
> Sent: Wednesday, October 30, 2002 9:38 AM
> To: CVS Discussion List
> Subject: pserver login problem to Linux from Win2k
>
>
> I have a CVS repository on our Linux development server that I need to
> access from my Win2k box.  I can access that repository logged in
> locally on the sever via telnet, and I can also access it via WinCVS,
> but I need to be able to access it from the command line (trying
> psever).  CVS from the command line is complaining about my CVSROOT
> variable.  It's probably just a simple Win vs Unix syntax issue, but I
> need help.
>
> Version on the sever is CVS 1.11.1p1 and I just downloaded the binary
> for Win which is v1.11.2
>
> Sample of my session via a DOS window (CVSROOT is set as an environment
> variable to be ':pserver:derosier@engswdev:/swdev/cvsroot'):
>
> ---
> J:\projects\ORHwBringUp>cvs ci -m "cmdline test" Makefile
> cvs commit: in directory .:
> cvs commit: ignoring CVS/Root because it specifies a non-existent
> repository /swdev/cvsroot cvs commit: in directory .: cvs commit:
> ignoring CVS/Root because it specifies a non-existent repository
> /swdev/cvsroot cvs commit: warning: failed to open C:\/.cvspass for
> reading: No such file or directory cvs commit: authorization failed:
> server engswdev rejected access to /swdev/cvsroot for user derosier cvs
> commit: used empty password; try "cvs login" with a real password
>
> J:\projects\ORHwBringUp>set
> CVSROOT=:pserver:derosier@engswdev:/swdev/cvsroot
>
> J:\projects\ORHwBringUp>echo %CVSROOT%
> :pserver:derosier@engswdev:/swdev/cvsroot
>
> J:\projects\ORHwBringUp>cvs login
> cvs login: in directory .:
> cvs login: ignoring CVS/Root because it specifies a non-existent
> repository /swdev/cvsroot Logging in to
> :pserver:derosier@engswdev:2401/swdev/cvsroot
> CVS password:
> cvs login: warning: failed to open C:\/.cvspass for readi

pserver login problem to Linux from Win2k

2002-10-30 Thread Steve deRosier
I have a CVS repository on our Linux development server that I need to
access from my Win2k box.  I can access that repository logged in locally on
the sever via telnet, and I can also access it via WinCVS, but I need to be
able to access it from the command line (trying psever).  CVS from the
command line is complaining about my CVSROOT variable.  It's probably just a
simple Win vs Unix syntax issue, but I need help.

Version on the sever is CVS 1.11.1p1 and I just downloaded the binary for
Win which is v1.11.2

Sample of my session via a DOS window (CVSROOT is set as an environment
variable to be ':pserver:derosier@engswdev:/swdev/cvsroot'):

---
J:\projects\ORHwBringUp>cvs ci -m "cmdline test" Makefile
cvs commit: in directory .:
cvs commit: ignoring CVS/Root because it specifies a non-existent repository
/swdev/cvsroot
cvs commit: in directory .:
cvs commit: ignoring CVS/Root because it specifies a non-existent repository
/swdev/cvsroot
cvs commit: warning: failed to open C:\/.cvspass for reading: No such file
or directory
cvs commit: authorization failed: server engswdev rejected access to
/swdev/cvsroot for user derosier
cvs commit: used empty password; try "cvs login" with a real password

J:\projects\ORHwBringUp>set
CVSROOT=:pserver:derosier@engswdev:/swdev/cvsroot

J:\projects\ORHwBringUp>echo %CVSROOT%
:pserver:derosier@engswdev:/swdev/cvsroot

J:\projects\ORHwBringUp>cvs login
cvs login: in directory .:
cvs login: ignoring CVS/Root because it specifies a non-existent repository
/swdev/cvsroot
Logging in to :pserver:derosier@engswdev:2401/swdev/cvsroot
CVS password:
cvs login: warning: failed to open C:\/.cvspass for reading: No such file or
directory



BTW--engswdev properly resolves to the IP of the server as it is set in my
hosts file.

Any ideas would be great.

Thanks,
- Steve

--
Steve deRosier
PianoDisc Design Engineer
(916) 567- ext. 175
www.pianodisc.com
[EMAIL PROTECTED]



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs