Hello, * On Wed, Jan 19, 2005 at 10:35:08AM -0800 Mark D. Baushke wrote: > Second, I have seen something similar related to NFS operations on > some hosts where the directory being released was on an NFS mounted > directory and there were kernel messages like > > 'got bad cookie vp <hexstring> bp <hexstring>' > > with the user seeing something like: > > % cvs release -d foo > You have [0] altered files in this repository. > Are you sure you want to release (and delete) directory `foo': yes > cvs release: deletion of directory src failed: Directory not empty > % > > but I have not actually seen the error you are reporting.
Just for the records: I have seen exactly the behaviour you are reporting on a Windows machine. Some poeple might remember my problems with getting CVS to run on DOS I posted some time ago. My setup is now as follows: I checkout everything on a Windows box, and completely work from the Windows share on the DOS box. That is, nothing is done locally in DOS, but all in the (shared) directory. Now, if I just worked in the directory in the DOS box and I am ready to stop working, I am not allowed to "cvs release -d" the directory. If I do this, I get exactly the message you mentioned above. Interestingly, I have now the following situation: 1. I cannot delete the directory from the Windows share until I have waited some time (> 15 minutes, it seems to me) 2. I cannot issue a "cvs release -d" afterwards, because CVS does not recognize the directory as a CVS repository anymore. It seems to me that some administrative files are already removed. (and: Yes, I have made sure on the DOS box that I am not in the directory on the network drive anymore: The sandbox can be found in r:\dos\<SANDBOXNAME>, and I issue a cd \ in r: before trying to release the sandbox.) Regards, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ http://www.viceteam.org/ _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
