Repository on Mounted Network Drive

2003-10-01 Thread Wayne Call 
What are the advantages of putting the Repository on a Mounted Network
Drive?  The purpose for putting the Repository on a network drive is so that
it automatically gets backed up by the Network Administrator.  The software
will get checked out onto a Linux Computer or Computers, and then the
software will get checked back in to a Mounted Network Drive.  The
Repository will be on a Mounted Network Drive.  What are the gottchas for
this type of development setup?  What would be another option?

I'm running into trouble with the cvs locks.  I can check out software, but
I cannot check in software and get the following error:

cvs commit: failed to create lock directory for '\mnt\ .'

This error is produced because I'm a guest user and the cvs attempts to
create a lock on the Mounted Network Drive.  It was suggested to me to put
the locks in another directory rather than the Repository, but I believe I
would still have the same problem.

Any suggestions?


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

Re: Directory command on import

2003-10-01 Thread Larry Jones 
Brice Oliver writes:
> 
> What does the "Directory" command do?  It then is always followed by some
> path in the repository.  Thanks!

Have you read the CVS Client/Server manual (doc/cvsclient.* in the CVS
source distribution)?  It contains a fairly complete explanation of the
Directory command.  You may have to read through the manual multiple
times before you start to understand it all.

-Larry Jones

Everything's gotta have rules, rules, rules! -- Calvin


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

Re: Repository on Mounted Network Drive

2003-10-01 Thread Larry Jones 
Wayne Call writes:
> 
> What are the advantages of putting the Repository on a Mounted Network
> Drive?  The purpose for putting the Repository on a network drive is so that
> it automatically gets backed up by the Network Administrator.  The software
> will get checked out onto a Linux Computer or Computers, and then the
> software will get checked back in to a Mounted Network Drive.  The
> Repository will be on a Mounted Network Drive.  What are the gottchas for
> this type of development setup?  What would be another option?

The "advantages" are that you get to learn a lot about the internal
format of RCS files and how well your backup/restore process works as
you try to fix the repository file corruption that will probably result.
In other words, it's a very bad idea; don't do it.  We've had lots of
reports of repository corruption caused by interoperability problems
between different NFS implementations.

> I'm running into trouble with the cvs locks.  I can check out software, but
> I cannot check in software and get the following error:
>
> cvs commit: failed to create lock directory for '\mnt\ .'

You also get to learn more about differnt permission systems, how
(badly) they map to each other, and how they work across a network (not
very well) than you ever wanted to.  Save yourself a lot of grief and
use client/server CVS with the repository on a disk that's local to the
server.

-Larry Jones

The authorities are trying to silence any view contrary to their own!
-- Calvin


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

Re: Repository on Mounted Network Drive

2003-10-01 Thread JacobRhoden 
On Thu, 2 Oct 2003 08:12 am, Wayne Call wrote:
> cvs commit: failed to create lock directory for '\mnt\ .'
>
> This error is produced because I'm a guest user and the cvs attempts to
> create a lock on the Mounted Network Drive.  It was suggested to me to put
> the locks in another directory rather than the Repository, but I believe I
> would still have the same problem.

I would suggest you create a lock directory on the mounted network drive and 
give it public read/write access, and make sure all machines using the 
repository use that public directory for the lock files (:

Regards,
Jacob

___
JacobRhoden -- http://rhoden.id.au/


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

Re: Directory command on import

2003-10-01 Thread Alexander Taler 


> "Brice" == Brice Oliver <[EMAIL PROTECTED]> writes:
  Brice> To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
  Brice> Subject: Directory command on import
  Brice> Date: Wed, 1 Oct 2003 16:44:23 -0500

  Brice> I am writing an interface to CVS for my company and I am confused as
  Brice> to the use of the directory command while carrying on a direct socket
  Brice> communication with the CVS server.

You might be interested in the LibCVS project:
http://libcvs.cvshome.org/ we are working on libraries that do
that very thing.  We would be very happy to have more brains
around.

  Brice> What does the "Directory" command do?  It then is always followed by
  Brice> some path in the repository.

Basically, the Directory command tells the server which
directories you are going to work in, and the correspondance
between directories in the repository and those locally.

The most important thing to do is send the "original directory"
at the end.  Since I'm not using the protocol in the way it was
intended, I use the common ancestor of all the previous
directories, or the current working directory.  This seems to
work fine.  I'm not sure what cvs itself does.

I agree that the docs could be made a bit clearer, especially
that for Directory.  With a fair amount of effort I feel that I
pretty much understand them.  It is part of my plan to submit
some updates to the docs, at some undetermined time in the
future.

Alex 

-- 
http://libcvs.cvshome.org/Access CVS through a library. 
PGP:  ID: 0x23DC453B  FPR: 42D0 66C2 9FF8 553A 373A  B819 4C34 93BA 23DC 453B
You left out all the cheap character, Sam, why's the brave?
  -- The Two Towers  - Malaysian Edition


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

RE: Bug tracking.

2003-10-01 Thread Zieg, Mark 
I'm heavily invested in Lenscrafters :-)

-Original Message-
From: Terrence Enger [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2003 3:31 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Bug tracking.


At 11:15 2003-09-30 -0400, "Zieg, Mark" <[EMAIL PROTECTED]> wrote:
[snip]
>
>You can do that easily with "cvs update -j ... -j ..." as long as you
create a tag each time you do the synchronization, or you can use
something
like my  to extract a patchfile
after-the-fact.

I think I shall try some of the scripts there.  But, tell me, why ?

Terry.




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


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

Repository on Mounted Network Drive

2003-10-01 Thread Wayne Call 
What are the advantages of putting the Repository on a Mounted Network
Drive?  The purpose for putting the Repository on a network drive is so that
it automatically gets backed up by the Network Administrator.  The software
will get checked out onto a Linux Computer or Computers, and then the
software will get checked back in to a Mounted Network Drive.  The
Repository will be on a Mounted Network Drive.  What are the gottchas for
this type of development setup?  What would be another option?

I'm running into trouble with the cvs locks.  I can check out software, but
I cannot check in software and get the following error:

cvs commit: failed to create lock directory for '\mnt\ .'

This error is produced because I'm a guest user and the cvs attempts to
create a lock on the Mounted Network Drive.  It was suggested to me to put
the locks in another directory rather than the Repository, but I believe I
would still have the same problem.

Any suggestions?



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

Directory command on import

2003-10-01 Thread Brice Oliver 
I am writing an interface to CVS for my company and I am confused as to the
use of the directory command while carrying on a direct socket communication
with the CVS server.

What does the "Directory" command do?  It then is always followed by some
path in the repository.  Thanks!

Brice Oliver

Systems Analyst, Infrastructure
Product Development
Ontario Systems
Tel 765.751.7100
Fax 765.751.7199
mailto:[EMAIL PROTECTED]



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

cvs-1.11.7 seems to have changed the api for "release"

2003-10-01 Thread David Everly 
Using pserver cvs-1.11.7 on solaris and client cvs-1.11.6 for aix,
hpux, or solaris, there is this problem which does not occur when
the client and server are the same version:

cvs release -d example

Protocol error: bad global option -l
cvs release: unable to release `example'

Thanks,
Dave.


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