We have a remote CVS server that uses SecureShell to access it via an "ext"
CVS root. Our development team is experiencing repeated CVS access problems
with this server. The server runs RedHat 7.2 and has the latest build of
the CVS server
When we transfer a large number of files (e.g. cvs -n
Narendra Kumar wrote:
CVSROOT is /home/cvs
But, can we change it to pserver now?
Yes, follow steps at the link in my prev. mail.
-Narendra
--- Rohan Nandode <[EMAIL PROTECTED]> wrote:
As you mentioned earlier you are trying for password authentication.
i guess to do that you need to set-up cvs as
may be this would help
http://cvsbook.red-bean.com/cvsbook.html#The%20pserver%20access%20method%20is%20not%20working
more information on what error you are getting would help
-Rohan
Narendra Kumar wrote:
Hello,
We have a CVS server setup on a Linux machine. The authentication mechanism
selected
Hello,
We have a CVS server setup on a Linux machine. The authentication mechanism
selected is "passwd".
I have also installed a winCVS client setup on a Windows machine (both are
on same LAN).
I am trying to connect to CVS server thru this win-client. But, it is
failing.
Can anybody
: Monday, June 14, 2004 1:24 PM
>To: [EMAIL PROTECTED]
>Subject: Remote access problem - part 2
>
>
>What user/group/other permissions do I need from my remote
>cvs repository so users belonging to the same group can have
>access to it? To be more specific...
>
>user1 exists
What user/group/other permissions do I need from my remote
cvs repository so users belonging to the same group can have
access to it? To be more specific...
user1 exists both locally and remotely (cvs server) with same
userid and groupid. Local user1 uses the :fork: method to get
to the cvs reposi
--- "'Thomas S. Urban'" <[EMAIL PROTECTED]> wrote:
> My experience is that the client will get all my
> automated changes as
> long as keyword expansion will be done on the file.
> Looking at the
> client/server debug output files, it appears that
> the entire file is
> sent back to the client ev
[ On Thursday, March 21, 2002 at 09:46:06 (-0800), Noel Yap wrote: ]
> Subject: Re: cvs commitinfo - remote access issues - enforced code beautification
>
> If you're going this route, I would suggest your
> commitinfo script also check for the existence of RCS
> keywo
[ On Thursday, March 21, 2002 at 10:26:07 (-0500), Larry Jones wrote: ]
> Subject: Re: cvs commitinfo - remote access issues - enforced code beautification
>
> No, commit does a checkout to expand keywords -- see checkin.c starting
> at the comment that says:
>
>
--- "Thomas S. Urban" <[EMAIL PROTECTED]> wrote:
> Yeah, I understand that keywords expansion is
> required for my kludge to
> work, and that what I am doing is a definitely a
> kludge.
If you're going this route, I would suggest your
commitinfo script also check for the existence of RCS
keywords
On Thu, Mar 21, 2002 at 12:20:39 -0500, Larry Jones sent 0.5K bytes:
> Thomas S. Urban writes:
> >
> > It certainly does work for changes made with the commitinfo script - an
> > undocumented feature, perhaps.
>
> Only if there are RCS keywords in the file that also change as a result
> of the c
Thomas S. Urban writes:
>
> It certainly does work for changes made with the commitinfo script - an
> undocumented feature, perhaps.
Only if there are RCS keywords in the file that also change as a result
of the checkin. Like I said, using RCS keywords to get under-the-table
changes made on the
On Thu, Mar 21, 2002 at 08:15:03 -0800, Noel Yap sent 0.9K bytes:
> --- Larry Jones <[EMAIL PROTECTED]> wrote:
> > No, commit does a checkout to expand keywords -- see
> > checkin.c starting
> > at the comment that says:
> >
> > /* The checkin succeeded. If checking the file out
> >
On Thu, Mar 21, 2002 at 09:15:00 +0530, Shubhabrata Sengupta sent 3.1K bytes:
> I think that the server "writes back" the files to the client. Isn't
> this the way keywords are expanded on the client side once the checkin
> is through?
This is true.
Greg, I'm replying to your stuff here, since y
--- Larry Jones <[EMAIL PROTECTED]> wrote:
> No, commit does a checkout to expand keywords -- see
> checkin.c starting
> at the comment that says:
>
> /* The checkin succeeded. If checking
> the file out again
>would not cause any changes, we are
> done. Otherwise,
>
Noel Yap writes:
>
> I think Greg is correct in his assessment. My guess
> as to how keyword expansion works is that the client
> already knows how to expand the keywords without any
> help from the server. This can be tested by creating
> a commitinfo script that would, say, empty out the
> fi
--- Shubhabrata Sengupta
<[EMAIL PROTECTED]> wrote:
> I think that the server "writes back" the files to
> the client. Isn't
> this the way keywords are expanded on the client
> side once the checkin
> is through?
I think Greg is correct in his assessment. My guess
as to how keyword expansion wo
[ On Thursday, March 21, 2002 at 09:15:00 (+0530), Shubhabrata Sengupta wrote: ]
> Subject: RE: cvs commitinfo - remote access issues - enforced code beautification
>
> I think that the server "writes back" the files to the client. Isn't
> this the way keywords are
March 21, 2002 8:43 AM
To: Thomas S. Urban
Cc: CVS-II Discussion Mailing List
Subject: Re: cvs commitinfo - remote access issues - enforced code
beautification
[ On Wednesday, March 20, 2002 at 15:12:06 (-0800), Thomas S. Urban
wrote: ]
> Subject: Re: cvs commitinfo - remote access issu
[ On Wednesday, March 20, 2002 at 15:12:06 (-0800), Thomas S. Urban wrote: ]
> Subject: Re: cvs commitinfo - remote access issues - enforced code beautification
>
> What do you mean by "can not really"? I do some modification of
> committed files with a script called
-
From: Thomas S. Urban [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 20, 2002 12:54 PM
To: Austin Lauree
Cc: CVS Info - Mailing List (E-mail)
Subject: Re: cvs commitinfo - remote access issues - enforced code
beautification
Yeah, I've seem this with my commitinfo scripts. I think i
On Wed, Mar 20, 2002 at 16:37:44 -0500, Greg A. Woods sent 1.4K bytes:
<...>
> The source code control tool is not the place to do the beautification.
>
> You might want to validate the code and reject a commit if it does not
> meet your coding standards, but you should not (and indeed with CVS,
[ On Wednesday, March 20, 2002 at 12:18:26 (-0800), Austin Lauree wrote: ]
> Subject: cvs commitinfo - remote access issues - enforced code beautification
>
> I am trying to administer our cvs repository to ensure that all java
> code commited runs through a 'beautification'
On Wed, Mar 20, 2002 at 12:18:26 -0800, Austin Lauree sent 6.4K bytes:
> I am trying to administer our cvs repository to ensure that all java
> code commited runs through a 'beautification' process.
>
> I setup a test system where CVSROOT/commitinfo contains:
> ALL /scm/cvsscripts/commitscript
>
Title: cvs commitinfo - remote access issues - enforced code beautification
I am trying to administer our cvs repository to ensure that all java
code commited runs through a 'beautification' process.
I setup a test system where CVSROOT/commitinfo contains:
ALL /scm/
On Thu, Jun 28, 2001 at 06:38:44PM -0700, Burk Braun wrote:
> reading several web sites on CVS installation, I can not quite figure
> out whether the basic functions of CVS would be accessible by a basic
> FTP client like BBedit,
Ummm, you don't say which platform. I'll guess Mac -- only
BBedi
Hi, cvs-
I am investigating the use of CVS for my organization, and have to
say that we are addicted to BBedit to work on all the code for a set
of UNIX-hosted web sites, using its own on-board FTP functions. After
reading several web sites on CVS installation, I can not quite figure
out whe
Hi,
How to connect to a remote system and setting up password for CVS.
When i connect a remote system i want the information that how to set
the cvspassword in server side while i accessing the repository from
client. i have an message while connection with the server failure
aborted with
kvarman writes:
>
> cvs -d :pserver:[EMAIL PROTECTED]:/usr/local/cvsroot login
> (Logging in to [EMAIL PROTECTED])
> CVS password:
>
> cvs [login aborted]: recv() from server lor.kovaiteam.com: Connection
> reset by peer
There's something wrong with the server or its configuration. Most
lik
"Furmaniuk, Michael" wrote:
> I've built and moved the crypto.h file created when I built the OpenSSL
> package, but still get stopped when I am doing make for CVSI get to this
> point and am not sure why.
>
> -L/usr/local/include/gssapi/lib -lgssapi_krb5 -lkrb5 -lcrypto -lcom_err -o
> cvs
>> Thanks for the assist on this, but I am still having problems
compiling.
>> I got the Kerberos distribution from MIT and built it thinking that I'd
find
>> a crypto library in the build but I'm not seeing it. This is my first
time
>> building CVS, so maybe I need to get a "crypto" library fr
"Furmaniuk, Michael" wrote:
> Thanks for the assist on this, but I am still having problems compiling.
> I got the Kerberos distribution from MIT and built it thinking that I'd find
> a crypto library in the build but I'm not seeing it. This is my first time
> building CVS, so maybe I need to
19, 2001 4:07 PM
To: Furmaniuk, Michael
Cc: [EMAIL PROTECTED]
Subject: Re: Setting up remote access
"Furmaniuk, Michael" wrote:
> I've got the 1.11 version on my test server, just want to make sure it
> builds without problems before trying it out on the real server. I've
c
"Furmaniuk, Michael" wrote:
> I've got the 1.11 version on my test server, just want to make sure it
> builds without problems before trying it out on the real server. I've come
> up against a problem during make however. I am getting a message it cannot
> find a file called "crypto" which it
11:52 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Setting up remote access
Furmaniuk, Michael writes:
>
> In order to make sure that I have a proper build of CVS, I am going to
> re-build the CVS binary version 1.10 (it is the current one we are using)
I strongly sug
figuration files and
have always been able to access CVS remotely using pserver mode.
- Dennis
- Original Message -
From: "Furmaniuk, Michael" <[EMAIL PROTECTED]>
To: "Info-Cvs (E-mail)" <[EMAIL PROTECTED]>
Sent: Wednesday, January 17, 2001 7:17 AM
Subject: Se
Furmaniuk, Michael writes:
>
> In order to make sure that I have a proper build of CVS, I am going to
> re-build the CVS binary version 1.10 (it is the current one we are using)
I strongly suggest upgrading to the current release (1.11), which you
can get from www.cvshome.org, instead -- it ha
In order to make sure that I have a proper build of CVS, I am going to
re-build the CVS binary version 1.10 (it is the current one we are using)
with the required options for remote connection. The person who built our
current binary is no longer here, and I'd rather make sure that we are able
Hi Shawn,
> I'm not clear on the remote access methods for gaining access to the
> repo. Our development server will house the CVS bin files and CVS
> repository, as well as everyone's working copy [but not all in the
> same directory, that would get too confusing]. Our d
I'm not clear on the remote access
methods for gaining access to the repo. Our development server will house
the CVS bin files and CVS repository, as well as everyone's working copy [but
not all in the same directory, that would get too confusing]. Our dev.
server currently sup
40 matches
Mail list logo
