Package: cvs
Version: 1:1.12.9-17
Severity: normal

I have a default $CVSROOT value on all my accounts, even when the
corresponding directory isn't a valid CVS repository. When I want
to do some operation on a working directory, cvs shouldn't look at
$CVSROOT since the working directory has the necessary information
about the corresponding CVS repository. However one can see that
this is not the case, and cvs may fail even when the $CVSROOT value
is useless:

For instance, I have a working directory ~/software/rox/rox, and
I can do:

dixsept:~/software/rox/rox> cvs log README
[output: log of the README file]
dixsept:~/software/rox/rox> cd ..
dixsept:~/software/rox> cvs log rox/README
cvs [log aborted]: /home/vlefevre/cvsroot/CVSROOT: No such file or directory

I shouldn't have got an error here.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.4-20051215
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)

Versions of packages cvs depends on:
ii  debconf [debconf-2.0]         1.4.70     Debian configuration management sy
ii  libc6                         2.3.5-12   GNU C Library: Shared libraries an
ii  libpam-runtime                0.79-3     Runtime support for the PAM librar
ii  libpam0g                      0.79-3     Pluggable Authentication Modules l
ii  zlib1g                        1:1.2.3-9  compression library - runtime

Versions of packages cvs recommends:
ii  emacs-snapshot-gtk [info-br 1:20060120-2 The GNU Emacs editor (with GTK+ 2.
ii  emacs21 [info-browser]      21.4a-3      The GNU Emacs editor
ii  info [info-browser]         4.8-4        Standalone GNU Info documentation 
ii  konqueror [info-browser]    4:3.5.1-1    KDE's advanced file manager, web b
ii  netbase                     4.24         Basic TCP/IP networking system

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to