Forum OpenACS Development: direct manipulation of CVS repository and shifting packages into /contrib/obsolete-packages
by directly manipulating the repository, there is now no record on the CVS server that these used to live in /packages and /contrib/packages, so doing a cvs up -Pd will not delete them from their existing location in my working copy since as far as the repository is concerned they were never deleted from there...
as a heads-up for CVS users, any directory you see this kind of error message for
cvs server: cannot open directory /cvsroot/openacs-4/packages/acs-util: No such file or directoryshould be deleted manually in your working copy... it might also be worth fixing the repository by copying those directories back to their previous locations and then cvs rming them so that people's working copies will clean themselves up correctly the next time they update...
cvs server: skipping directory packages/acs-util
This is, in my personal opinion, not acceptable. If the packages affected were all non-core it might be easier to wear, but 3 of them were previously "core", so this will screw people looking (for example) to upgrade from previous versions to OACS5.
Yes, this can be worked around, but we have revision control for a reason.
Is it safe to rm my local instance? Fortunately for me currently its just an annoyance. Although maybe in the near future I will be likely on the same boat as you.
- copy (not move) the directories in the repository back to where they came from
- do a full update in a -HEAD checkout, there should now be copies of these packages in both the old and new locations
- use "cvs rm" to delete the files and directories from the old locations in the checkout
Relevant section of the CVS manual is at http://www.cvshome.org/docs/manual/cvs-1.11.7/cvs_7.html