Problems with the :server: access
Hi, We are using the :server: access method to access our CVS repository. Trying to check-out a module, one of my users got the following message: warning: unrecognized response `text' from cvs server (where 'text' is some arbitrary string.) I figured out that 'text' was actually printed from the ~/.cshrc file on the server. The ~/.cshrc file of the user printed a few things to the standard output (e.g., "echo $PATH" or printing some special characters that change the title of the xterm window) and these things got back to the CVS client as an "unregcognized response from cvs server". Most of these things ended in a warning message like the above but some of them also caused erroneous conflicts to occur. What is wrong here, and what can the user do to fix it? Is it a server configuration problem (is the .cshrc restricted not to print on stdout) or a client configuration problem? Thanks, Shlomo ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Problems with the :server: access
Reinstein, Shlomo <[EMAIL PROTECTED]> writes: > We are using the :server: access method to access our CVS repository. Trying > to check-out a module, one of my users got the following message: > warning: unrecognized response `text' from cvs server > (where 'text' is some arbitrary string.) > > I figured out that 'text' was actually printed from the ~/.cshrc file on the > server. The ~/.cshrc file of the user printed a few things to the standard > output (e.g., "echo $PATH" or printing some special characters that change > the title of the xterm window) and these things got back to the CVS client > as an "unregcognized response from cvs server". Most of these things ended > in a warning message like the above but some of them also caused erroneous > conflicts to occur. > > What is wrong here, and what can the user do to fix it? Is it a server > configuration problem (is the .cshrc restricted not to print on stdout) or a > client configuration problem? > > Thanks, > Shlomo The :server: protocol needs to be clean without any unexpected text from the initial rsh or ssh connection. The user needs to make sure that non-interactive shell use does not generate messages on stdout or stderr. If we assume that the command that is generating this output is primarily intended for interactive users and is the command echo foo somewhere in the users ~/.cshrc script, then either that text should be moved to the ~/.login file where it is done once on interactive login or it should be protected for non-interactive use by checking to see if the prompt has been set: if ($?prompt) then # commands useful interactive use of this shell go inside of this block echo foo endif Enjoy! -- Mark ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Restriction on tags count ?
Hi, Please update us with the info 1) whether there is any restriction on number of tags put for a file? 2) is there any restriction on the size of the cvs admin files? Thanks in advance for the help With regards, kudi ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Restriction on tags count ?
Kudiyarasan writes: > > Please update us with the info > > 1) whether there is any restriction on number of tags put for a file? > 2) is there any restriction on the size of the cvs admin files? There are no hard limits, although they may be limited by available memory or your system file size limit. -Larry Jones When you're as far ahead of the class as I am, it doesn't take much time. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Filenames with spaces
I added a filename with spaces in it to a repository. This is the log from the ouput window: cvs -q commit -m "added to cvs" "MT930B Program Guide.pdf" (in directory C:\tiltwin\SatCon\Protocols\Standard\) RCS file: /cvsrepo/tiltracroot/tiltwin/SatCon/Protocols/Standard/MT930B Program Guide.pdf,v done Checking in MT930B Program Guide.pdf; /cvsrepo/tiltracroot/tiltwin/SatCon/Protocols/Standard/MT930B Program Guide.pdf,v <-- MT930B Program Guide.pdf initial revision: 1.1 done rlog: /cvsrepo/tiltracroot/tiltwin/SatCon/Protocols/Standard/RCS/MT930B,v: No such file or directory rlog: /cvsrepo/tiltracroot/tiltwin/SatCon/Protocols/Standard/RCS/Program,v: No such file or directory rlog: /cvsrepo/tiltracroot/tiltwin/SatCon/Protocols/Standard/RCS/Guide.pdf,v: No such file or directory co: /cvsrepo/tiltracroot/tiltwin/SatCon/Protocols/Standard/RCS/Guide.pdf,v: No such file or directory I received 3 emails instead of one. Is this a problem with my email script? Brian ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Filenames with spaces
Brian Kowald writes: > > I received 3 emails instead of one. Is this a problem with my email script? Most likely. -Larry Jones You should see me when I lose in real life! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Info on CVS server best practices
I am looking for information as to CVS server best practices. By this I am suggesting: - CVS repository be installed on a dedicated server rather than on a box contending with developers and other applications for memory, swap space and disk space - CVS repository be on a server where users don't have direct login access - shadowing of CVS repository in the event of a calamity for instant switchover to the other repository rather than wait for the lengthy restore process Does anybody have any other suggestions, plus comments on the above? Thanks. Susan Johnson ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Weird release message
Title: Weird release message I'm in the process of switching my team's source control from SourceSafe to CVS (using CVSNT). Everything has gone great, but there's been one little issue that's bugged me. When I invoke "cvs release -d somedir" on a directory where I know I all my changes have been committed, I get the message "You have [1] altered files in this repository." If I abort the release, switch to somedir, and run "cvs -q -n update", CVS doesn't find any altered files. After some more experimentation, I found that "cvs release -d" would always report one altered file, no matter how many files had actually been altered. Have I missed something somewhere? On my Solaris server, I'm using a different cvs command-line client (1-11-1p1), and it seems to report the correct number of altered files. This is a small issue, everything else seems to work fine. But it's bugging me, and possibly I've missed something important. Lance Peterson VERTICORE TECHNOLOGIES 801 453 9111 www.verticore.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Info on CVS server best practices
> - CVS repository be installed on a dedicated server >rather than on a box contending with developers and >other applications for memory, swap space and disk >space > > - CVS repository be on a server where users don't have > direct login access I've never felt a need to enforce either of these. It depends on the scope of your project, of course, but even with a half-dozen active developers on a common dev box (Linux or FreeBSD), running periodic builds of moderate-sized source trees (say 100K SLOC), I've never had problems such as would significantly deteriorate CVS's relatively low I/O & resource requirements. > - shadowing of CVS repository in the event of a calamity > for instant switchover to the other repository rather than > wait for the lengthy restore process We just ran an hourly rsync script to keep our hot-swap /usr/local/cvsroot current, then switched over the DNS hostname of the old repository to the backup box when the prime went down for some reason (as happened twice, I believe). Worked like a charm, and very lightweight to implement. Also, by not being a stickler about the "nologin/dedicated" rule, we were able to use another development box (db server, webserver, whatever) as the hot-swap, avoiding the expense of an unused standby host. In the post-Bubble world, cost-cutting is once again recognized as an admirable business trait :-) ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Filenames with spaces
-Original Message- From: Brian Kowald [mailto:[EMAIL PROTECTED]] Sent: Monday, January 13, 2003 6:40 PM To: CVS-Info List - Post Subject: Filenames with spaces >I added a filename with spaces in it to a repository. This is the log from >the ouput window: [SNIP] >I received 3 emails instead of one. Is this a problem with my email script? No. It's a problem with your file name. rlog expects a repository location and a list of files *separated by spaces*. So rlog received a repository and three "words" separated by spaces. Please, don't use spaces in the name of files controlled by CVS or even CVSNT, so you'll don't get in trouble. The files will be stored in your repository but server side scripts won't run correctly and no logging will be done correctly by CVSNT and specially by CVS. >Brian Xandao. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS and multiple platforms - version conflicts, featuresavailable etc.
After several helpful comments from people here, and a bit of digging
around, have been examining 1.11.4 from cvshome.org as well as the
source package from Debian for 1.11.2...
Have noticed something .. in the Debian 1.11.2 source package, there is
a patch file which adjusts server.c's handling of watch statements..
Is the following a problem with the patch in the debian 1.11.2 package,
or a problem inherent with 1.11.2 - and would either necessitate an
upgrade to 1.11.4 (which isn't available as a package for debian yet)?
For example - server.c exerpt
-
serve_watch_add (arg)
char *arg;
{
do_cvs_command ("watch_add", watch_add);
}
Patch file 10_watch_on_pserver exerpt
-
@@ -3732,7 +3732,7 @@
serve_watch_add (arg)
char *arg;
{
-do_cvs_command ("watch_add", watch_add);
+do_cvs_command ("watch", watch_add);
}
... would this have anything to do with the following?
Example session
---
$ cvs watch add -R -a all *
cvs watch: warning: directory CVS specified in argument
cvs watch: but CVS uses CVS for its own purposes; skipping CVS directory
cvs [server aborted]: unknown command: watch_add
cvs [watch aborted]: end of file from server (consult above messages if any)
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
