#547 Removing Directory Problem

[Geir Ove Skjaervik]

Hello,

There seems to be a slight problem with removing
Directories. At least the command works differently in
WinCVS and TkCVS.

In TkCVS a release -d <directoryname> will indeed
release & delete the directory and it vanishes from the
browser.

In WinCVS the contents of the directory will be deleted
but not the directory. If one now deletes the directory
outside WinCVS, it will show a "broken" symbol for the
directory: It looks like WinCVS looks
at the "entry" file in the CVS direcotry of the root of the
deleted directory: It still has an entry for the deleted
directory. If I remove this entry manually, WinCVS will
remove the "broken" directory symbol (Thus that is the
workaround). Would be nice if this could be fixed
though.

[Oliver Giesen]

Logged In: YES
user_id=158827

What version of WinCvs are you using? This was already fixed
in 1.3.11 IIRC but as that fix broke the console window it
was (partially) withdrawn again for 1.3.12. I'm not sure how
far the new fix is but it should definitely be in the works
already.

[Allan Larsen]

Logged In: YES
user_id=932928

In 1.3.14.1 Beta 14 (build 1) the problem is still partly there.
Sometimes wincvs apparently accesses the directory which it
tries to remove and the command therefore fails. Any files or
subdirectories are removed as they should be, but not the
directory itself.

It should be fairly simple to ensure that wincvs changes to
the parent directory before attempting to run the command.

[Charles Oliva]

Logged In: YES
user_id=968183

I have a very similar problem. I've used WinCVS
1.3.14.1beta14 and 1.3.15.1beta15 against a CVSNT 2.0.14
repository.

In both cases, I can release directories from the command
line okay. However, when I use WinCVS and select the
option to "Delete the given directory", it will properly clean
out the directory contents but leave the main directory name
there and give the following error message:
"cvs release: cannot remove <module_name> directory:
Permission denied".

I do have full admin rights on both machines involved. The
directory can be manually cleaned up as a workaround, but it
would be good to have this fixed.