4:28 p.m.
This bug report will be sent to the XEmacs Development Team,
not to your local site managers!!
Please write in English, because the XEmacs maintainers do not have
translators to read other languages for them.
Please describe as succinctly as possible:
- What happened.
- What you thought should have happened.
- Precisely what you were doing at the time.
Please also include any C or lisp back-traces that you may have.
================================================================
Dear Bug Team!
PCL_CVS has a confusing behavior in our programming group. It always
prints out a bunch of Parsing Errors in the *CVS* buffer. For
example, for a cvs-update I get:
,----
| PCL-CVS release v2_9_9
|
| Repository : :pserver:gboerrigter＠cvs.i2c-systems.com:/cvs
| Working directory: /home/gboerrigter/workspace/dev-env/tools/
|
|
|
| Message: Parser Error: 'CVS server: Updating .'
| Message: Parser Error: 'CVS server: Updating togetherj'
| Message: Parser Error: 'CVS server: Updating togetherj/bin'
| Message: Parser Error: 'CVS server: Updating togetherj/config'
| Message: Parser Error: 'CVS server: Updating togetherj/doc'
| Message: Parser Error: 'CVS server: Updating togetherj/doc/images'
| Message: Parser Error: 'CVS server: Updating togetherj/gendoc'
| Message: Parser Error: 'CVS server: Updating xemacs'
| Modified xemacs/emacs-i2c.el
| Modified xemacs/init-1.el
| Unknown xemacs/semantic.cache
|
| --------------------- End ---------------------
| -- last cmd: cvs -f -z3 update --
`----
The Messages are very confusing, because they are not always at the
top, but mixed up with the files. This even happens with xemacs
-vanilla (the rest of this buffer is filled from that xemacs).
Any idea, why those messages are printed? Our server runs CVS 1.10.5.
Thanks,
Gerd
================================================================
System Info to help track down your bug:
---------------------------------------
uname -a: Linux lhospital 2.4.9 #1 SMP Mon Jul 30 15:20:16 GMT 2001 i686 unknown
./configure 'i386-suse-linux' '--with-gcc' '--dynamic'
'--rel-alloc' '--debug=no' '--error-checking=none'
'--cflags=-O2 -mcpu=i486 -march=i486 -Wall -Wno-switch -pipe -m486 -malign-loops=2
-malign-jumps=2 -malign-functions=2' '--ldflags=-s -znocombreloc'
'--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/X11R6/bin'
'--datadir=/usr/share'
'--archlibdir=/usr/lib/xemacs/21.4.4/i386-suse-linux'
'--docdir=/usr/lib/xemacs/21.4.4/i386-suse-linux'
'--lispdir=/usr/share/xemacs/21.4.4/lisp'
'--pkgdir=/usr/share/xemacs/21.4.4/lisp'
'--etcdir=/usr/share/xemacs/21.4.4/etc' '--statedir=/var/lib/xemacs'
'--infodir=/usr/share/xemacs/info' '--mandir=/usr/share/man/man1'
'--with-sound=native' '--with-database=gnudbm,berkdb'
'--with-ncurses' '--with-tty=yes' '--with-gpm'
'--with-site-lisp' '--with-xpm' '--with-gif' '--with-tiff'
'--with-jpeg' '--with-png' '--with-x' '--with-athena=3d'
'--with-menubars=lucid' '--with-scrollbars=lucid'
'--with-dialogs=athena' '--with-widgets=athena'
'--x-includes=/usr/X11R6/include' '--x-libraries=/usr/X11R6/lib'
'--with-mule' '--with-xim=xlib' '--with-xfs'
'--with-clash-detection' '--with-ldap' '--with-pop'
XEmacs 21.4.4 "Artificial Intelligence" configured for `i386-suse-linux'.
Compilation / Installation:
Source code location: /usr/src/packages/BUILD/xemacs-21.4.4
Installation prefix: /usr
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler: gcc -O2 -mcpu=i486 -march=i486 -Wall -Wno-switch
-pipe -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2
Relocating allocator for buffers: yes
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11R6/include
- X Windows libraries location: /usr/X11R6/lib
- Handling WM_COMMAND properly.
Compiling in support for the Athena widget set:
- Athena headers location: X11/Xaw3d
- Athena library to link: Xaw3d
Using Lucid menubars.
Using Lucid scrollbars.
Using Athena dialog boxes.
Using Athena native widgets.
TTY:
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Compiling in support for X-Face message headers.
Sound:
Compiling in support for sound (native).
Databases:
Compiling in support for Berkeley database.
Compiling in support for GNU DBM.
Compiling in support for LDAP.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Compiling in support for XIM (X11R5+ I18N input method).
- Using raw Xlib to provide XIM support.
- Using XFontSet to provide bilingual menubar.
Compiling in support for Canna on Mule.
Compiling in support for the WNN input method on Mule.
Mail:
Compiling in support for POP mail retrieval.
Compiling in support for "dot-locking" mail spool file locking method.
Other Features:
Compiling in support for dynamic shared object modules.
Load-Path Lisp Shadows:
----------------------
(/mnt/peach/apps/xemacs/site-packages/lisp/docbookide/make-regexp
/mnt/peach/apps/xemacs/site-packages/lisp/tdtd/make-regexp
/mnt/peach/apps/xemacs/site-packages/lisp/jde/setnu
/mnt/peach/apps/xemacs/xemacs-packages/lisp/edit-utils/setnu
/mnt/peach/apps/xemacs/site-packages/lisp/Updates/iswitchb
/mnt/peach/apps/xemacs/xemacs-packages/lisp/edit-utils/iswitchb
/mnt/peach/apps/xemacs/site-packages/lisp/eieio-0.17beta3/tree
/mnt/peach/apps/xemacs/xemacs-packages/lisp/eieio/tree
/mnt/peach/apps/xemacs/site-packages/lisp/eieio-0.17beta3/eieio
/mnt/peach/apps/xemacs/xemacs-packages/lisp/eieio/eieio
/mnt/peach/apps/xemacs/site-packages/lisp/eieio-0.17beta3/eieio-tests
/mnt/peach/apps/xemacs/xemacs-packages/lisp/eieio/eieio-tests
/mnt/peach/apps/xemacs/site-packages/lisp/eieio-0.17beta3/eieio-speedbar
/mnt/peach/apps/xemacs/xemacs-packages/lisp/eieio/eieio-speedbar
/mnt/peach/apps/xemacs/site-packages/lisp/eieio-0.17beta3/eieio-opt
/mnt/peach/apps/xemacs/xemacs-packages/lisp/eieio/eieio-opt
/mnt/peach/apps/xemacs/site-packages/lisp/eieio-0.17beta3/eieio-doc
/mnt/peach/apps/xemacs/xemacs-packages/lisp/eieio/eieio-doc
/mnt/peach/apps/xemacs/site-packages/lisp/eieio-0.17beta3/eieio-custom
/mnt/peach/apps/xemacs/xemacs-packages/lisp/eieio/eieio-custom
/mnt/peach/apps/xemacs/site-packages/lisp/eieio-0.17beta3/eieio-comp
/mnt/peach/apps/xemacs/xemacs-packages/lisp/eieio/eieio-comp
/mnt/peach/apps/xemacs/site-packages/lisp/eieio-0.17beta3/eieio-base
/mnt/peach/apps/xemacs/xemacs-packages/lisp/eieio/eieio-base
/mnt/peach/apps/xemacs/site-packages/lisp/eieio-0.17beta3/compare-strings
/mnt/peach/apps/xemacs/xemacs-packages/lisp/eieio/compare-strings
/mnt/peach/apps/xemacs/site-packages/lisp/eieio-0.17beta3/chart
/mnt/peach/apps/xemacs/xemacs-packages/lisp/eieio/chart
/mnt/peach/apps/xemacs/site-packages/lisp/eieio-0.17beta3/call-tree
/mnt/peach/apps/xemacs/xemacs-packages/lisp/eieio/call-tree
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/semantic-texi
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/semantic-texi
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/semantic-load
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/semantic-load
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/semanticdb
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/semanticdb
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/semantic-scm
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/semantic-scm
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/semantic-java
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/semantic-java
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/senator
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/senator
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/working
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/working
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/sformat
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/sformat
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/semantic
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/semantic
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/semantic-util
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/semantic-util
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/semantic-sb
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/semantic-sb
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/semantic-make
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/semantic-make
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/semantic-imenu
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/semantic-imenu
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/semantic-el
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/semantic-el
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/semantic-ctxt
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/semantic-ctxt
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/semantic-c
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/semantic-c
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/semantic-bnf
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/semantic-bnf
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/document
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/document
/mnt/peach/apps/xemacs/site-packages/lisp/semantic-1.4beta13/document-vars
/mnt/peach/apps/xemacs/xemacs-packages/lisp/semantic/document-vars
/mnt/peach/apps/xemacs/site-packages/lisp/Updates/sh-script
/mnt/peach/apps/xemacs/xemacs-packages/lisp/sh-script/sh-script
/mnt/peach/apps/xemacs/site-packages/lisp/speedbar-0.14beta2/speedbar
/mnt/peach/apps/xemacs/xemacs-packages/lisp/speedbar/speedbar
/mnt/peach/apps/xemacs/site-packages/lisp/speedbar-0.14beta2/sb-w3
/mnt/peach/apps/xemacs/xemacs-packages/lisp/speedbar/sb-w3
/mnt/peach/apps/xemacs/site-packages/lisp/speedbar-0.14beta2/sb-texinfo
/mnt/peach/apps/xemacs/xemacs-packages/lisp/speedbar/sb-texinfo
/mnt/peach/apps/xemacs/site-packages/lisp/speedbar-0.14beta2/sb-rmail
/mnt/peach/apps/xemacs/xemacs-packages/lisp/speedbar/sb-rmail
/mnt/peach/apps/xemacs/site-packages/lisp/speedbar-0.14beta2/sb-info
/mnt/peach/apps/xemacs/xemacs-packages/lisp/speedbar/sb-info
/mnt/peach/apps/xemacs/site-packages/lisp/speedbar-0.14beta2/sb-image
/mnt/peach/apps/xemacs/xemacs-packages/lisp/speedbar/sb-image
/mnt/peach/apps/xemacs/site-packages/lisp/speedbar-0.14beta2/sb-gud
/mnt/peach/apps/xemacs/xemacs-packages/lisp/speedbar/sb-gud
/mnt/peach/apps/xemacs/site-packages/lisp/speedbar-0.14beta2/rpm
/mnt/peach/apps/xemacs/xemacs-packages/lisp/speedbar/rpm
/mnt/peach/apps/xemacs/site-packages/lisp/speedbar-0.14beta2/dframe
/mnt/peach/apps/xemacs/xemacs-packages/lisp/speedbar/dframe
/mnt/peach/apps/xemacs/site-packages/lisp/speedbar-0.14beta2/bigclock
/mnt/peach/apps/xemacs/xemacs-packages/lisp/speedbar/bigclock
/mnt/peach/apps/xemacs/site-packages/lisp/Updates/folding
/mnt/peach/apps/xemacs/xemacs-packages/lisp/text-modes/folding
/mnt/peach/apps/xemacs/site-packages/lisp/Updates/filladapt
/mnt/peach/apps/xemacs/xemacs-packages/lisp/text-modes/filladapt
/mnt/peach/apps/xemacs/site-packages/xslt-process-2.1/lisp/xslt-process
/mnt/peach/apps/xemacs/xemacs-packages/lisp/xslt-process/xslt-process
/mnt/peach/apps/xemacs/site-packages/lisp/suse-term/gnome
/mnt/peach/apps/xemacs/21.4.4/lisp/gnome)
Installed XEmacs Packages:
-------------------------
((zenirc:version 1.11 :type regular)
(xslt-process :version 1.05 :type regular)
(xemacs-devel :version 1.38 :type single-file)
(xemacs-base :version 1.56 :type regular)
(w3 :version 1.2 :type regular)
(vm :version 7.0 :type regular)
(viper :version 1.29 :type regular)
(view-process :version 1.11 :type regular)
(vhdl :version 1.13 :type regular)
(vc-cc :version 1.18 :type regular)
(vc :version 1.29 :type regular)
(tramp :version 1.0 :type regular)
(tpu :version 1.12 :type regular)
(tooltalk :version 1.13 :type regular)
(tm :version 1.29 :type regular)
(time :version 1.11 :type regular)
(textools :version 1.12 :type regular)
(text-modes :version 1.32 :type single-file)
(texinfo :version 1.2 :type regular)
(supercite :version 1.18 :type regular)
(strokes :version 1.08 :type regular)
(speedbar :version 1.21 :type regular)
(sounds-wav :version 1.1 :type regular)
(sounds-au :version 1.1 :type regular)
(slider :version 1.13 :type regular)
(sh-script :version 1.13 :type regular)
(sgml :version 1.08 :type regular)
(semantic :version 1.1 :type regular)
(scheme :version 1.11 :type regular)
(rmail :version 1.12 :type regular)
(reftex :version 1.23 :type regular)
(psgml :version 1.23 :type regular)
(ps-print-nomule :version 1.05 :type regular)
(prog-modes
:version
1
.44
:type
single-file)
(pcomplete :version 1.01 :type regular)
(pcl-cvs :version 1.55 :type regular)
(pc :version 1.2 :type single-file)
(os-utils :version 1.25 :type single-file)
(net-utils :version 1.23 :type single-file)
(misc-games :version 1.15 :type single-file)
(mine :version 1.14 :type regular)
(mh-e :version 1.13 :type regular)
(mew :version 1.14 :type regular)
(mailcrypt :version 2.09 :type regular)
(mail-lib :version 1.4 :type regular)
(ispell :version 1.23 :type regular)
(ilisp :version 1.19 :type regular)
(igrep :version 1.08 :type regular)
(idlwave :version 1.23 :type regular)
(hm--html-menus :version 1.16 :type regular)
(gnus :version 1.57 :type regular)
(gnats :version 1.12 :type regular)
(games :version 1.13 :type regular)
(fsf-compat :version 1.09 :type single-file)
(frame-icon :version 1.09 :type regular)
(forms :version 1.13 :type regular)
(footnote :version 1.13 :type regular)
(eudc :version 1.34 :type regular)
(eterm :version 1.13 :type regular)
(eshell :version 1.01 :type regular)
(emerge :version 1.09 :type regular)
(elib :version 1.08 :type single-file)
(eieio :version 1.01 :type regular)
(eicq :version 1.05 :type regular)
(efs :version 1.26 :type regular)
(edt :version 1.12 :type regular)
(edit-utils :version 1.73 :type single-file)
(ediff :version 1.33 :type regular)
(edebug :version 1.14 :type regular)
(dired :version 1.11 :type regular)
(dictionary :version 1.04 :type regular)
(debug :version 1.14 :type regular)
(crisp :version 1.12 :type regular)
(cookie :version 1.13 :type regular)
(clearcase :version 1.0 :type regular)
(cc-mode :version 1.26 :type regular)
(calendar :version 1.17 :type regular)
(calc :version 1.17 :type regular)
(c-support :version 1.16 :type single-file)
(build :version 1.03 :type regular)
(bbdb :version 1.16 :type regular)
(auctex :version 1.28 :type regular)
(apel :version 1.2 :type regular)
(ada :version 1.1 :type regular)
(Sun :version 1.13 :type regular)
(skk :version 1.19 :type regular)
(mule-base :version 1.39 :type regular)
(lookup :version 1.08 :type regular)
(locale :version 1.18 :type regular)
(leim :version 1.17 :type regular)
(egg-its :version 1.26 :type regular)
(edict :version 1.12 :type regular))
Features:
--------
(mail-abbrevs xemacsbug shadow sendmail rfc822 annotations pcl-cvs
diff-mode advice advice-preload pcl-cvs-parse pcl-cvs-info
pcl-cvs-defs pcl-cvs-util cvs-compat cus-face dired-faces dired-xemacs
dired cookie dll elib-node zenirc-autoloads xslt-process-autoloads
xemacs-devel-autoloads xemacs-base-autoloads w3-autoloads vm-autoloads
viper-autoloads view-process-autoloads vhdl-autoloads vc-cc-autoloads
vc-autoloads tramp-autoloads tpu-autoloads tooltalk-autoloads
tm-autoloads time-autoloads textools-autoloads text-modes-autoloads
texinfo-autoloads supercite-autoloads strokes-autoloads
speedbar-autoloads sounds-wav-autoloads sounds-au-autoloads
slider-autoloads sh-script-autoloads sgml-autoloads semantic-autoloads
scheme-autoloads rmail-autoloads reftex-autoloads psgml-autoloads
ps-print-nomule-autoloads prog-modes-autoloads pcomplete-autoloads
pcl-cvs-autoloads pc-autoloads os-utils-autoloads net-utils-autoloads
misc-games-autoloads mine-autoloads mh-e-autoloads mew-autoloads
mailcrypt-autoloads mail-lib-autoloads ispell-autoloads
ilisp-autoloads igrep-autoloads idlwave-autoloads
hm--html-menus-autoloads gnus-autoloads gnats-autoloads
games-autoloads fsf-compat-autoloads frame-icon-autoloads
forms-autoloads footnote-autoloads eudc-autoloads eterm-autoloads
eshell-autoloads emerge-autoloads elib-autoloads eieio-autoloads
eicq-autoloads efs-autoloads edt-autoloads edit-utils-autoloads
ediff-autoloads edebug-autoloads dired-autoloads dictionary-autoloads
debug-autoloads crisp-autoloads cookie-autoloads clearcase-autoloads
cc-mode-autoloads calendar-autoloads calc-autoloads
c-support-autoloads build-autoloads bbdb-autoloads auctex-autoloads
apel-autoloads ada-autoloads Sun-autoloads skk-autoloads
mule-base-autoloads lookup-autoloads locale-autoloads leim-autoloads
egg-its-autoloads edict-autoloads lisp-autoloads disp-table loadhist
auto-show fontl-hooks x-iso8859-1 canna-leim slovenian czech romanian
ccl mule-help code-cmds gutter-items menubar-items x-menubar
mode-motion mouse itimer auto-save lisp-mode easymenu iso8859-1 page
buff-menu lib-complete cus-file derived frame text-props obsolete
cus-start custom widget cl-extra mini-cl cl cl-19 packages backquote
very-early-lisp CANNA file-coding wnn mule lucid-scrollbars cut-buffer
lucid-menubars athena-dialogs x c-balloon-help tty-frames tty toolbar
native-sound scrollbar unix-processes multicast network-streams
subprocesses modules menu-accelerator-support menubar berkeley-db dbm
md5 xemacs xim i18n2 gutter tiff png gif jpeg xface xpm xbm
lisp-float-type linux dialog devices window-system base64)
Recent keystrokes:
-----------------
misc-user up w o r k TAB d e v TAB RET home end home
end home end home end home end home end home end home
end home end home end home next next prior prior M-x
up c v s - u p d a t e RET up t o o l s RET home up
up up up up up up up up up M-x r e p o r t - x e m
TAB RET
Recent messages (most recent first):
-----------------------------------
Loading xemacsbug...done
Loading xemacsbug...
CVS process has completed
Running cvs update ...
No preceding item in read-command-history
CVS process has completed
Running cvs update ...
No preceding item in file-name-history
Loading annotations...done
Loading annotations...
Loading pcl-cvs...done
Loading advice...done
Loading advice...
Loading dired-mule...done
Loading dired-mule...
Loading cus-face...done
Loading cus-face...
Loading pcl-cvs...
7:14 p.m.
Gerd Boerrigter <gerd.boerrigter(a)i2c-systems.com> writes:
PCL_CVS has a confusing behavior in our programming group. It
always
prints out a bunch of Parsing Errors in the *CVS* buffer. For
example, for a cvs-update I get:
,----
| PCL-CVS release v2_9_9
|
| Repository : :pserver:gboerrigter＠cvs.i2c-systems.com:/cvs
| Working directory: /home/gboerrigter/workspace/dev-env/tools/
|
|
|
| Message: Parser Error: 'CVS server: Updating .'
| Message: Parser Error: 'CVS server: Updating togetherj'
| Message: Parser Error: 'CVS server: Updating togetherj/bin'
| Message: Parser Error: 'CVS server: Updating togetherj/config'
| Message: Parser Error: 'CVS server: Updating togetherj/doc'
| Message: Parser Error: 'CVS server: Updating togetherj/doc/images'
| Message: Parser Error: 'CVS server: Updating togetherj/gendoc'
| Message: Parser Error: 'CVS server: Updating xemacs'
| Modified xemacs/emacs-i2c.el
| Modified xemacs/init-1.el
| Unknown xemacs/semantic.cache
|
| --------------------- End ---------------------
| -- last cmd: cvs -f -z3 update --
`----
The Messages are very confusing, because they are not always at the
top, but mixed up with the files. This even happens with xemacs
-vanilla (the rest of this buffer is filled from that xemacs).
Any idea, why those messages are printed? Our server runs CVS 1.10.5.
I have experienced this too some times (with 21.1 and 21.4 ) using
'CVS_RSH=ssh', but only over "slower" connections (128kb/s) and
hitting cvs-status a couple of times made it go away. I have never
experienced this when using local (same computer or LAN) cvs
repository.
It could be nice if it was possible to set a cvs-debug variable to let
the cvs output go to a debug buffer to have a closer look at what
pcl_cvs receives.
relevant information:
XEmacs 21.1.14;
pcl-cvs v2_9_9 (pcl-cvs package version 1.49)
cvs-client side 1.11
XEmacs 21.4.4
pcl-cvs v2_9_9 (package version 1.55)
cvs-client side 1.11
cvs version (repository side) 1.10.7 (all cases)
I have not yet experienced it with the xemacs cvs repository yet, what
cvs version runs on that repository?
The problem is easily provoked on (256 kb/s)
':ext:jarlen＠cvs.eicq.sourceforge.net:/cvsroot/eicq', Steve, can you
say what cvs version is installed there? The non-parseable output is
not always identical.
Jarl
8:33 p.m.
>>>> "Jarl" == Jarl Friis <jarl(a)diku.dk>
writes:
Jarl> Gerd Boerrigter <gerd.boerrigter(a)i2c-systems.com> writes:
> PCL_CVS has a confusing behavior in our programming group. It
always
> prints out a bunch of Parsing Errors in the *CVS* buffer. For
> example, for a cvs-update I get:
>
> ,----
> | PCL-CVS release v2_9_9
> |
> | Repository : :pserver:gboerrigter＠cvs.i2c-systems.com:/cvs
> | Working directory: /home/gboerrigter/workspace/dev-env/tools/
> |
> |
> |
> | Message: Parser Error: 'CVS server: Updating .'
> | Message: Parser Error: 'CVS server: Updating togetherj'
> | Message: Parser Error: 'CVS server: Updating togetherj/bin'
> | Message: Parser Error: 'CVS server: Updating togetherj/config'
> | Message: Parser Error: 'CVS server: Updating togetherj/doc'
> | Message: Parser Error: 'CVS server: Updating togetherj/doc/images'
> | Message: Parser Error: 'CVS server: Updating togetherj/gendoc'
> | Message: Parser Error: 'CVS server: Updating xemacs'
> | Modified xemacs/emacs-i2c.el
> | Modified xemacs/init-1.el
> | Unknown xemacs/semantic.cache
> |
> | --------------------- End ---------------------
> | -- last cmd: cvs -f -z3 update --
> `----
>
> The Messages are very confusing, because they are not always at the
> top, but mixed up with the files. This even happens with xemacs
> -vanilla (the rest of this buffer is filled from that xemacs).
>
> Any idea, why those messages are printed? Our server runs CVS 1.10.5.
Jarl> I have experienced this too some times (with 21.1 and 21.4 ) using
Jarl> 'CVS_RSH=ssh', but only over "slower" connections (128kb/s)
and
Jarl> hitting cvs-status a couple of times made it go away. I have never
Jarl> experienced this when using local (same computer or LAN) cvs
Jarl> repository.
Jarl> It could be nice if it was possible to set a cvs-debug variable to let
Jarl> the cvs output go to a debug buffer to have a closer look at what
Jarl> pcl_cvs receives.
How about
C-x b runs the command switch-to-buffer
*cvs-tmp*
Gerd, can you see anything wrong in that buffer?
Jarl> relevant information:
Jarl> XEmacs 21.1.14;
Jarl> pcl-cvs v2_9_9 (pcl-cvs package version 1.49)
Jarl> cvs-client side 1.11
Jarl> XEmacs 21.4.4
Jarl> pcl-cvs v2_9_9 (package version 1.55)
Jarl> cvs-client side 1.11
Jarl> cvs version (repository side) 1.10.7 (all cases)
Jarl> I have not yet experienced it with the xemacs cvs repository
Jarl> yet, what cvs version runs on that repository?
Jarl> The problem is easily provoked on (256 kb/s)
Jarl> ':ext:jarlen＠cvs.eicq.sourceforge.net:/cvsroot/eicq', Steve,
Jarl> can you say what cvs version is installed there? The
Jarl> non-parseable output is not always identical.
Jarl> Jarl
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
9:05 p.m.
Adrian.Aichner(a)t-online.de (Adrian Aichner) writes:
>>>>> "Jarl" == Jarl Friis
<jarl(a)diku.dk> writes:
Jarl> I have experienced this too some times (with 21.1 and 21.4 ) using
Jarl> 'CVS_RSH=ssh', but only over "slower" connections
(128kb/s) and
Jarl> hitting cvs-status a couple of times made it go away. I have never
Jarl> experienced this when using local (same computer or LAN) cvs
Jarl> repository.
Jarl> It could be nice if it was possible to set a cvs-debug variable to let
Jarl> the cvs output go to a debug buffer to have a closer look at what
Jarl> pcl_cvs receives.
How about
C-x b runs the command switch-to-buffer
*cvs-tmp*
I miss that buffer. hmm... I wonder why this is not created or is it
automatically deleted after the cvs command is issued maybe.
Gerd, can you see anything wrong in that buffer?
Can you see that buffer at all?
Jarl
9:32 p.m.
>>>> "Jarl" == Jarl Friis <jarl(a)diku.dk>
writes:
Jarl> Adrian.Aichner(a)t-online.de (Adrian Aichner) writes:
>> >>>> "Jarl" == Jarl
Friis <jarl(a)diku.dk> writes:
>
Jarl> I have experienced this too some times (with 21.1 and 21.4 ) using
Jarl> 'CVS_RSH=ssh', but only over "slower" connections (128kb/s)
and
Jarl> hitting cvs-status a couple of times made it go away. I have never
Jarl> experienced this when using local (same computer or LAN) cvs
Jarl> repository.
>
Jarl> It could be nice if it was possible to set a
cvs-debug variable to let
Jarl> the cvs output go to a debug buffer to have a closer look at what
Jarl> pcl_cvs receives.
>
>> How about
>> C-x b runs the command switch-to-buffer
>> *cvs-tmp*
Jarl> I miss that buffer. hmm... I wonder why this is not created or is it
Jarl> automatically deleted after the cvs command is issued maybe.
Ah, the buffer name is "SPC * c v s - t m p *" without the
double-quotes and spaces.
Multiple of these stay around in my XEmacs, but I have this
;; To use this file, load it or add (require 'uniquify) to your ".emacs"
;; and set `uniquify-buffer-name-style' to one of its non-nil alternative
;; values.
(require 'uniquify)
in my .emacs.
They are:
" *cvs-tmp*"
" *cvs-tmp*<AichnerAd>"
htctu
Adrian
>
>> Gerd, can you see anything wrong in that
buffer?
Jarl> Can you see that buffer at all?
Jarl> Jarl
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
7:38 a.m.
Adrian.Aichner(a)t-online.de (Adrian Aichner) writes:
>>>>> "Jarl" == Jarl Friis
<jarl(a)diku.dk> writes:
Jarl> Adrian.Aichner(a)t-online.de (Adrian Aichner) writes:
>> >>>>> "Jarl" == Jarl Friis <jarl(a)diku.dk>
writes:
>>
Jarl> I have experienced this too some times (with 21.1 and 21.4 ) using
Jarl> 'CVS_RSH=ssh', but only over "slower" connections
(128kb/s) and
Jarl> hitting cvs-status a couple of times made it go away. I have never
Jarl> experienced this when using local (same computer or LAN) cvs
Jarl> repository.
>>
Jarl> It could be nice if it was possible to set a cvs-debug variable to let
Jarl> the cvs output go to a debug buffer to have a closer look at what
Jarl> pcl_cvs receives.
>>
>> How about
>> C-x b runs the command switch-to-buffer
>> *cvs-tmp*
Jarl> I miss that buffer. hmm... I wonder why this is not created or is it
Jarl> automatically deleted after the cvs command is issued maybe.
Ah, the buffer name is "SPC * c v s - t m p *" without the
double-quotes and spaces.
Allright, I got that one, but it is not listed under completions when i
do C-x b TAB neither is it found in *Buffer List* C-x C-b, how sad or
is that intentionally?
Thanks, Adrian.
For one reproduction of the bug, the only strange I can see regarding
the misbehaviour of pcl-cvs is a longer splitter line, in "*cvs*"
buffer I have
/---------------------------------------------
|In directory .:
|Message: Parser Error:
'========================================================================='
|Message: Parser Error: 'File: authorize-here.xpm Status: Up-to-date'
|Message: Parser Error: ''
|Message: Parser Error: ' Working revision: 1.2'
|Message: Parser Error: ' Repository
revision: 1.2 /cvsroot/eicq/eicq/etc/eicq/authorize-here.xpm,v'
|Message: Parser Error: ' Sticky Tag: (none)'
|Message: Parser Error: ' Sticky Date: (none)'
|Message: Parser Error: ' Sticky Options: (none)'
|Message: Parser Error: ''
\----------------------------------------------
and in " *cvs-tmp*" I have
/---------------------------------------------
|===================================================================
|File: icq2tcp.c Status: Needs Patch
|
| Working revision: 1.3
| Repository revision: 1.4 /cvsroot/eicq/eicq/icq2tcp.c,v
| Sticky Tag: (none)
| Sticky Date: (none)
| Sticky Options: (none)
|
|=========================================================================
|File: authorize-here.xpm Status: Up-to-date
|
| Working revision: 1.2
| Repository revision: 1.2 /cvsroot/eicq/eicq/etc/eicq/authorize-here.xpm,v
| Sticky Tag: (none)
| Sticky Date: (none)
| Sticky Options: (none)
|
|===================================================================
|File: disconnect.xpm Status: Up-to-date
|
| Working revision: 1.2
| Repository revision: 1.2 /cvsroot/eicq/eicq/etc/eicq/disconnect.xpm,v
| Sticky Tag: (none)
| Sticky Date: (none)
| Sticky Options: (none)
|
\----------------------------------------------
So that longer splitter line has probably confused the parser. I
believe I have seen other reasons for parser confussions, but I will
take this up as I run in to them again. Now I know where to look (in "
*cvs-tmp*")
Multiple of these stay around in my XEmacs, but I have this
;; To use this file, load it or add (require 'uniquify) to your ".emacs"
;; and set `uniquify-buffer-name-style' to one of its non-nil alternative
;; values.
(require 'uniquify)
in my .emacs.
Even without the uniquify feature (checked `features') I have the
buffer. Thanks. Anyway I should probably have a look at these features
as use of temporary (debugging) buffers to be used in eSMS.
BTW: how do you ask XEmacs to do the kind of quoting? such as
/---------------
|This is quoted
\---------------
Jarl
11:54 p.m.
On Wed, 23 Jan 2002, Gerd Boerrigter stated:
Jarl Friis <jarl(a)diku.dk> writes:
> BTW: how do you ask XEmacs to do the kind of quoting? such as
> /---------------
> |This is quoted
> \---------------
there was a file boxquote.el by Dave Pearson posted to
gnu.emacs.sources which does such kind of emphasis.
See <http://www.davep.org/emacs/boxquote.el>;.
--
`However, if you want to detect whether (say, 1 in 1000) cars are being
abducted by bunnies along their route, you've got a whole new problem.'
- Scott James Remnant on network problems
6:19 a.m.
Nix <nix(a)esperi.demon.co.uk> writes:
On Wed, 23 Jan 2002, Gerd Boerrigter stated:
> Jarl Friis <jarl(a)diku.dk> writes:
>
>> BTW: how do you ask XEmacs to do the kind of quoting? such as
>> /---------------
>> |This is quoted
>> \---------------
>
> there was a file boxquote.el by Dave Pearson posted to
> gnu.emacs.sources which does such kind of emphasis.
See <http://www.davep.org/emacs/boxquote.el>;.
Thanks to both of you.
Jarl
11:11 a.m.
>>>> "Jarl" == Jarl Friis <jarl(a)diku.dk>
writes:
Jarl> Adrian.Aichner(a)t-online.de (Adrian Aichner) writes:
>> >>>> "Jarl" == Jarl
Friis <jarl(a)diku.dk> writes:
>>
Jarl> Adrian.Aichner(a)t-online.de (Adrian Aichner) writes:
>> >> >>>> "Jarl" == Jarl
Friis <jarl(a)diku.dk> writes:
> >>
Jarl> I have experienced this too some times (with 21.1 and 21.4 ) using
Jarl> 'CVS_RSH=ssh', but only over "slower" connections (128kb/s)
and
Jarl> hitting cvs-status a couple of times made it go away. I have never
Jarl> experienced this when using local (same computer or LAN) cvs
Jarl> repository.
> >>
Jarl> It could be nice if it was possible
to set a cvs-debug variable to let
Jarl> the cvs output go to a debug buffer to have a closer look at what
Jarl> pcl_cvs receives.
> >>
>> >> How about
>> >> C-x b runs the command switch-to-buffer
>> >> *cvs-tmp*
>>
Jarl> I miss that buffer. hmm... I wonder why this is not created or is it
Jarl> automatically deleted after the cvs command is issued maybe.
>
> Ah, the buffer name is "SPC * c v s - t m p *" without the
> double-quotes and spaces.
Jarl> Allright, I got that one, but it is not listed under
Jarl> completions when i do C-x b TAB neither is it found in
Jarl> *Buffer List* C-x C-b, how sad or is that intentionally?
Yes. See the documentation of list-buffers :-)
Jarl> Thanks, Adrian.
Jarl> For one reproduction of the bug, the only strange I can see regarding
Jarl> the misbehaviour of pcl-cvs is a longer splitter line, in "*cvs*"
Jarl> buffer I have
That's it!
This is straight out of emacs/lisp/pcvs-parse.el of GNU Emacs:
(defun cvs-parse-status ()
(let (nofile path base-rev head-rev type)
(and
(cvs-match
"===================================================================$")
Your output contains lines with either 67 (handled today) or 73 ='s.
Stefan, does this count as a bug report?
Best regards,
Adrian
Jarl> /---------------------------------------------
Jarl> |In directory .:
Jarl> |Message: Parser Error:
'========================================================================='
Jarl> |Message: Parser Error: 'File: authorize-here.xpm Status:
Up-to-date'
Jarl> |Message: Parser Error: ''
Jarl> |Message: Parser Error: ' Working revision: 1.2'
Jarl> |Message: Parser Error: ' Repository
revision: 1.2 /cvsroot/eicq/eicq/etc/eicq/authorize-here.xpm,v'
Jarl> |Message: Parser Error: ' Sticky Tag: (none)'
Jarl> |Message: Parser Error: ' Sticky Date: (none)'
Jarl> |Message: Parser Error: ' Sticky Options: (none)'
Jarl> |Message: Parser Error: ''
Jarl> \----------------------------------------------
Jarl> and in " *cvs-tmp*" I have
Jarl> /---------------------------------------------
Jarl> |===================================================================
Jarl> |File: icq2tcp.c Status: Needs Patch
Jarl> |
Jarl> | Working revision: 1.3
Jarl> | Repository revision: 1.4 /cvsroot/eicq/eicq/icq2tcp.c,v
Jarl> | Sticky Tag: (none)
Jarl> | Sticky Date: (none)
Jarl> | Sticky Options: (none)
Jarl> |
Jarl> |=========================================================================
Jarl> |File: authorize-here.xpm Status: Up-to-date
Jarl> |
Jarl> | Working revision: 1.2
Jarl> | Repository
revision: 1.2 /cvsroot/eicq/eicq/etc/eicq/authorize-here.xpm,v
Jarl> | Sticky Tag: (none)
Jarl> | Sticky Date: (none)
Jarl> | Sticky Options: (none)
Jarl> |
Jarl> |===================================================================
Jarl> |File: disconnect.xpm Status: Up-to-date
Jarl> |
Jarl> | Working revision: 1.2
Jarl> | Repository revision: 1.2 /cvsroot/eicq/eicq/etc/eicq/disconnect.xpm,v
Jarl> | Sticky Tag: (none)
Jarl> | Sticky Date: (none)
Jarl> | Sticky Options: (none)
Jarl> |
Jarl> \----------------------------------------------
Jarl> So that longer splitter line has probably confused the parser. I
Jarl> believe I have seen other reasons for parser confussions, but I will
Jarl> take this up as I run in to them again. Now I know where to look (in "
Jarl> *cvs-tmp*")
>
> Multiple of these stay around in my XEmacs, but I have this
> ;; To use this file, load it or add (require 'uniquify) to your
".emacs"
> ;; and set `uniquify-buffer-name-style' to one of its non-nil alternative
> ;; values.
> (require 'uniquify)
> in my .emacs.
Jarl> Even without the uniquify feature (checked `features') I have the
Jarl> buffer. Thanks. Anyway I should probably have a look at these features
Jarl> as use of temporary (debugging) buffers to be used in eSMS.
Jarl> BTW: how do you ask XEmacs to do the kind of quoting? such as
Jarl> /---------------
Jarl> |This is quoted
Jarl> \---------------
Jarl> Jarl
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
2:09 p.m.
Jarl> For one reproduction of the bug, the only strange I can
see regarding
Jarl> the misbehaviour of pcl-cvs is a longer splitter line, in "*cvs*"
Jarl> buffer I have
That's it!
This is straight out of emacs/lisp/pcvs-parse.el of GNU Emacs:
(defun cvs-parse-status ()
(let (nofile path base-rev head-rev type)
(and
(cvs-match
"===================================================================$")
Your output contains lines with either 67 (handled today) or 73 ='s.
What kind of strange cvs behavior is that ?
Looking at cvs's source code, I can't see how that can ever happen.
Anyway, the fix on PCL-CVS' side is trivial.
Stefan
10:42 a.m.
Adrian.Aichner(a)t-online.de (Adrian Aichner) writes:
>>>>> "Jarl" == Jarl Friis
<jarl(a)diku.dk> writes:
Jarl> Gerd Boerrigter <gerd.boerrigter(a)i2c-systems.com> writes:
>> PCL_CVS has a confusing behavior in our programming group. It always
>> prints out a bunch of Parsing Errors in the *CVS* buffer. For
>> example, for a cvs-update I get:
>>
>> ,----
>> | PCL-CVS release v2_9_9
>> |
>> | Repository : :pserver:gboerrigter＠cvs.i2c-systems.com:/cvs
>> | Working directory: /home/gboerrigter/workspace/dev-env/tools/
>> |
>> |
>> |
>> | Message: Parser Error: 'CVS server: Updating .'
>> | Message: Parser Error: 'CVS server: Updating togetherj'
>> | Message: Parser Error: 'CVS server: Updating togetherj/bin'
>> | Message: Parser Error: 'CVS server: Updating togetherj/config'
>> | Message: Parser Error: 'CVS server: Updating togetherj/doc'
>> | Message: Parser Error: 'CVS server: Updating
togetherj/doc/images'
>> | Message: Parser Error: 'CVS server: Updating togetherj/gendoc'
>> | Message: Parser Error: 'CVS server: Updating xemacs'
>> | Modified xemacs/emacs-i2c.el
>> | Modified xemacs/init-1.el
>> | Unknown xemacs/semantic.cache
>> |
>> | --------------------- End ---------------------
>> | -- last cmd: cvs -f -z3 update --
>> `----
>>
>> The Messages are very confusing, because they are not always at the
>> top, but mixed up with the files. This even happens with xemacs
>> -vanilla (the rest of this buffer is filled from that xemacs).
>>
>> Any idea, why those messages are printed? Our server runs CVS 1.10.5.
Jarl> I have experienced this too some times (with 21.1 and 21.4 ) using
Jarl> 'CVS_RSH=ssh', but only over "slower" connections
(128kb/s) and
Jarl> hitting cvs-status a couple of times made it go away. I have never
Jarl> experienced this when using local (same computer or LAN) cvs
Jarl> repository.
Jarl> It could be nice if it was possible to set a cvs-debug variable to let
Jarl> the cvs output go to a debug buffer to have a closer look at what
Jarl> pcl_cvs receives.
How about
C-x b runs the command switch-to-buffer
*cvs-tmp*
Gerd, can you see anything wrong in that buffer?
No, it looks right for me (same CVS update as above):
,----
| ? xemacs/semantic.cache
| CVS server: Updating .
| CVS server: Updating togetherj
| CVS server: Updating togetherj/bin
| CVS server: Updating togetherj/config
| CVS server: Updating togetherj/doc
| CVS server: Updating togetherj/doc/images
| CVS server: Updating togetherj/gendoc
| CVS server: Updating xemacs
| M xemacs/emacs-i2c.el
| M xemacs/init-1.el
`----
Hmm, can it be a problem, that it says "CVS server:" at the beginning?
We access the repository using pserver, but maybe pcl-cvs doesn't
handle that right?
Thanks for looking into this.
Gerd
8:55 p.m.
|--==> "JF" == Jarl Friis <jarl(a)diku.dk> writes:
JF> Gerd Boerrigter <gerd.boerrigter(a)i2c-systems.com> writes:
[...]
>| Message: Parser Error: 'CVS server: Updating .'
[...]
JF> I have experienced this too some times (with 21.1 and 21.4 ) using
JF> 'CVS_RSH=ssh', but only over "slower" connections (128kb/s)
and
JF> hitting cvs-status a couple of times made it go away. I have never
JF> experienced this when using local (same computer or LAN) cvs
JF> repository.
JF> It could be nice if it was possible to set a cvs-debug variable to let
JF> the cvs output go to a debug buffer to have a closer look at what
JF> pcl_cvs receives.
Look in 'pcl-cvs-parse.el'. I'd say that's where you might be able to
fix this.
JF> I have not yet experienced it with the xemacs cvs repository yet, what
JF> cvs version runs on that repository?
I've seen this from cvs.xemacs.org (it happens a lot for me). The CVS
server is a "Martin Buchholz hybrid", but I'm not sure what version it
is based on.
JF> The problem is easily provoked on (256 kb/s)
JF> ':ext:jarlen＠cvs.eicq.sourceforge.net:/cvsroot/eicq', Steve, can you
JF> say what cvs version is installed there?
I have no idea.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
10:34 p.m.
>>>> "SY" == Steve Youngs
<youngs(a)xemacs.org> writes:
SY> |--==> "JF" == Jarl Friis <jarl(a)diku.dk> writes:
JF> Gerd Boerrigter <gerd.boerrigter(a)i2c-systems.com> writes:
SY> [...]
>> | Message: Parser Error: 'CVS server: Updating .'
SY> [...]
JF> I have experienced this too some times (with 21.1 and 21.4 ) using
JF> 'CVS_RSH=ssh', but only over "slower" connections (128kb/s)
and
JF> hitting cvs-status a couple of times made it go away. I have never
JF> experienced this when using local (same computer or LAN) cvs
JF> repository.
JF> It could be nice if it was possible to set a cvs-debug variable to let
JF> the cvs output go to a debug buffer to have a closer look at what
JF> pcl_cvs receives.
SY> Look in 'pcl-cvs-parse.el'. I'd say that's where you might be
able to
SY> fix this.
JF> I have not yet experienced it with the xemacs cvs repository yet, what
JF> cvs version runs on that repository?
SY> I've seen this from cvs.xemacs.org (it happens a lot for me). The CVS
SY> server is a "Martin Buchholz hybrid", but I'm not sure what
version it
SY> is based on.
It's a patched version of
Concurrent Versions System (CVS) 1.11 (client/server)
The patch is very minimal to allow commit from multiple users via
shared account.
JF> The problem is easily provoked on (256 kb/s)
JF> ':ext:jarlen＠cvs.eicq.sourceforge.net:/cvsroot/eicq', Steve, can you
JF> say what cvs version is installed there?
SY> I have no idea.
SY> --
SY> |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
SY> | XEmacs - It's not just an editor. |
SY> | It's a way of life. |
SY> |------------------------------------<youngs(a)xemacs.org>---|
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
1:20 a.m.
>>>> "APA" == Adrian Aichner
<Adrian.Aichner(a)t-online.de> writes:
APA> It's a patched version of Concurrent Versions System (CVS)
APA> 1.11 (client/server)
APA> The patch is very minimal to allow commit from multiple users
APA> via shared account.
To be precise, it is a single new line that allows sshd to specify the
CVS user name. So as long as the problem does not depend on CVS user
name == Unix user name, or something like that, we are running vanilla
CVS built from source.
I note that my Debian system says the version is "1.11.1p1", so maybe
there's something more recent that what we're running at SunSITE?
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.
8:19 a.m.
Steve Youngs <youngs(a)xemacs.org> writes:
|--==> "JF" == Jarl Friis <jarl(a)diku.dk> writes:
JF> Gerd Boerrigter <gerd.boerrigter(a)i2c-systems.com> writes:
[...]
>>| Message: Parser Error: 'CVS server: Updating .'
[...]
JF> I have experienced this too some times (with 21.1 and 21.4 ) using
JF> 'CVS_RSH=ssh', but only over "slower" connections (128kb/s)
and
JF> hitting cvs-status a couple of times made it go away. I have never
JF> experienced this when using local (same computer or LAN) cvs
JF> repository.
JF> It could be nice if it was possible to set a cvs-debug variable to let
JF> the cvs output go to a debug buffer to have a closer look at what
JF> pcl_cvs receives.
Look in 'pcl-cvs-parse.el'. I'd say that's where you might be able to
fix this.
Yep, Adrian allready pointed out the line, so I guess we're just
waiting for a patch from Stefan. But maybe he/we wait to isolate the
problem more, cause I don't think this is the root of the problem. I
have seen other non-parseable situations, that eventually went away
after a couple of cvs-status.
JF> I have not yet experienced it with the xemacs cvs repository yet, what
JF> cvs version runs on that repository?
I've seen this from cvs.xemacs.org (it happens a lot for me). The CVS
server is a "Martin Buchholz hybrid", but I'm not sure what version it
is based on.
Could you send us (or me) the content of " *cvs-tmp*" buffer (note the
initial space in the buffer name).
Does "it happens a lot for me" means that it also sometimes parses
without problems?
What version do you use locally (as client)?
Jarl
8337
days inactive
8340
days old
15 comments
8 participants
participants (8)
-
Adrian Aichner -
Adrian Aichner -
Gerd Boerrigter -
Jarl Friis -
Nix -
Stefan Monnier -
Stephen J. Turnbull -
Steve Youngs