Hi,

"KOIE Hidetaka ($B8q9>1QN4(B)" wrote:
> 
> From: Anton Lavrentiev <[EMAIL PROTECTED]>
> Subject: CVS release and status commands
> Date: Fri, 28 Jul 2000 01:20:15 +0900 (JST)
> 
>   | It seems that there is a bug in the current CVS release, 1.10.8, which
>   | I have downloaded from www.cyclic.com.
>   |
>   | Once a module, suppose CVSROOT, is checked out (with 'cvs co CVSROOT'),
>   | and then released (like 'cvs release -d CVSROOT'), it is still in CVS/Entries 
>file,
>   | so that any further attempt to do 'cvs status' fails (CVSROOT: No such 
>directory).
> 
> I fail to repeat.  The working directory is removed cleanly.
Yes, you're right, the directory is removed, but not the entry from
CVS/Entries file. Then, if you try to do 'cvs status', it will fail
due to CVSROOT is not actually present.

> 
> ***** SCRIPT: foo
> #!/bin/sh
> DIR=`pwd`/repo
> [ -d $DIR ] && exit 1
> CVSROOT=:local:$DIR
> #CVSROOT=:fork:$DIR
> export CVSROOT
> cvs init
> cvs version
> cvs co CVSROOT
> ls CVSROOT
> cvs -Q release -d CVSROOT
> ls CVSROOT
Add 'cvs status' here, and see!

> rm -rf $DIR
> 
> ***** EXAMINE
> % sh foo
> Concurrent Versions System (CVS) 1.10.8.1 (client/server)
> cvs checkout: Updating CVSROOT
> U CVSROOT/checkoutlist
> U CVSROOT/commitinfo
> U CVSROOT/config
> U CVSROOT/cvswrappers
> U CVSROOT/editinfo
> U CVSROOT/loginfo
> U CVSROOT/modules
> U CVSROOT/notify
> U CVSROOT/rcsinfo
> U CVSROOT/taginfo
> U CVSROOT/verifymsg
> CVS             config          loginfo         rcsinfo
> checkoutlist    cvswrappers     modules         taginfo
> commitinfo      editinfo        notify          verifymsg
> ls: CVSROOT: No such file or directory
> %
> 
> --
> KOIE Hidetaka <[EMAIL PROTECTED]>

Regards,

Anton Lavrentiev

NCBI NIH
Bethesda MD USA

Reply via email to