[no subject]

Hi, I am getting this error while checking out data from Linux CVS Server thru my Windows CVSClient. Can anybody help me to understand the cause for this problem. COMMAND supplied: cvs -z9 -q update test.h (in directory C:\work) ERROR: cvs update: inflate: unknown compression method cvs

Discouraging :local:

--On Wednesday, January 22, 2003 12:08 PM -0500 Eric Siegerman [EMAIL PROTECTED] wrote: That'd be nice. Rather a challenge to implement though -- how *does* one tell, portably and from application code, whether a given directory is locally or remotely mounted? Perhaps a better way to phrase

Re: unknown compression

I am getting this error while checking out data from Linux CVS Server thru my Windows CVSClient. Can anybody help me to understand the cause for this problem. COMMAND supplied: cvs -z9 -q update test.h (in directory C:\work) ERROR: cvs update: inflate: unknown compression method cvs

RE: unknown compression

CVS version is 1.11.1p1 (client/server). We are using -z9 option with cvs update command getting the Input/Output error. --prem -Original Message- From: Fabian Cenedese [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 1:49 PM To: '[EMAIL PROTECTED]' Subject: Re: unknown

CVS win2000 gurus, are you there?

Hi all wise guys and girls! I'm about to install CVS (cvsnt) on Win2000 instead of using MS SourceSafe. I know that any of the Unix based OS is preferred (as always) for this. Unfortunately a win2000 server is the only server I able to use. I've read some documentation and have been

Re: unknown compression

Hi! I think the mailing list that you should post this query to should be [EMAIL PROTECTED] . Anyway, coming to your problem, you have used the TCP/IP compression in your CVS client. If you are using WinCVS, this option can be disabled by going to the Admin Menu - Preferences and the Global Tab.

Upgrading repository from CVS 1.10.7 to 1.11.5

Hi, I'm hoping for some guidance on moving a repository between the above CVS versions (and also to a different machine architecture Linux Pentium to Linux Alpha). Naively I guess I just copy the files - but is there anything else to be aware of? Thanks Simon Scott Avellino Technologies

How to tell WinCvs where is Python?

Hi, I just installed WinCvs13b10.zip. When I invoked the program the first time it searches for tcl and python After this I installed: tcl823.exe and Python-2.3a1.exe ok this is an alpha release but also with the official version 2.2 NOT in Administrator mode (dlls are locally) everytime I

Re: CVS case problem

I've a problem, I have a lot of files with the same name but with different case in the same directory, since I working on UNIX there is not a problem, but now when I tried to check out on NT this return a Conflict and this is fine because cvs try to check out 2 files with the same name

Terminated with fatal signal 4

Anyone are familiar with this error? Checking in JP/main/Resource.h; /cvsrepository/JP/main/Resource.h,v -- Resource.h new revision: 1.13; previous revision: 1.12 done Terminated with fatal signal 4 cvs commit: saving log message in C:\DOCUME~1\admin\LOCALS~1\Temp\1\4 Thanks. Moises.

Re: Upgrading repository from CVS 1.10.7 to 1.11.5

Simon Scott writes: I'm hoping for some guidance on moving a repository between the above CVS versions (and also to a different machine architecture Linux Pentium to Linux Alpha). Naively I guess I just copy the files - but is there anything else to be aware of? Nope. It's a good idea

Re: Discouraging :local:

Kenneth Porter writes: Perhaps a better way to phrase the issue is: What properties of a filesystem make :local: inadvisable, and can those properties be easily detected? What makes :local: inadvisable is the disk not being local, but rather being on some kind of network filesystem. I don't

RE: CVS win2000 gurus, are you there?

Benni Stefanutti writes: I've read some documentation and have been following the discussions. There seems to be to be some pitfalls using Windows. Is that so? Not particularly. We were, in fact, running our repository on a Win2000 Pro box for a while (until the box itself died). We just

Re: Terminated with fatal signal 4

Zanabria, Moises writes: Checking in JP/main/Resource.h; /cvsrepository/JP/main/Resource.h,v -- Resource.h new revision: 1.13; previous revision: 1.12 done Terminated with fatal signal 4 cvs commit: saving log message in C:\DOCUME~1\admin\LOCALS~1\Temp\1\4 That indicates that the

How to Connect WinCVS 1.3b10 to New CVS 1.11.5 pserver?

We're testing out the new version of CVS 1.11.5 on a new pserver (Solaris 5.8) using port 2402. All of our cross-platform access (i.e., Solaris, Linux Win2K) to this new port and version check out okay **except** for WinCVS. We're using WinCVS 1.3b10. There are two problems: 1) Switching

Re: How to Connect WinCVS 1.3b10 to New CVS 1.11.5 pserver?

[Thu, 23 Jan 2003 16:22:18 -0800] Thus spake Peter Connolly [EMAIL PROTECTED]: We're testing out the new version of CVS 1.11.5 on a new pserver (Solaris 5.8) using port 2402. All of our cross-platform access (i.e., Solaris, Linux Win2K) to this new port and version check out okay

Re: How to tell WinCvs where is Python?

Richard Uhlmann wrote: Hi, I just installed WinCvs13b10.zip. When I invoked the program the first time it searches for tcl and python For future questions regarding WinCVS, you will get best results posting to the cvsgui mailing list ([EMAIL PROTECTED]). After this I installed: tcl823.exe