I now believe that all of my cvs study led me to conclude that I was creating and modifying ``modules''; but, modules can only exist at the top level under CVSROOT. Therefore, you are probably correct that cvs import is the solution here.
In an effort to correct my miscreant behaviour, I tried using cvs remove. Under some conditions, cvs remove works as expected. However, see failed transaction, at end, to see problems with inability to generate locked files. Are there limitations to cvs remove? What is the cause of the lock problem? Mike Noyes wrote: > > On Mon, 2002-07-15 at 22:39, Michael D. Schleif wrote: > > > > No matter how hard I try, I cannot commit a directory structure to cvs. > > > > I get lock failures, even when I try to commit them one directory at a > > time. > > > > Clearly, there is some approved process for doing this and I do not know > > what that is. > > Michael, > I looked at your commit messages, and I think I understand what you were > trying to accomplish. Here is a sequence that I believe would have > worked. > > >From a directory out side of your checked out cvs tree (devel/helices). > Create the directory hierarchy that you wish to add to our repository. > Then from inside the root of this new hierarchy execute: > > $ cvs -d:ext:[EMAIL PROTECTED]:/cvsroot/leaf import \ > -I ! "devel/helices/ntpclnt" vendor start > > Note: naming conventions aren't enforced on imports. > > Note: this command will not work now, as there is already a > directory with that name in our repository. > > Would you like me to open a SF support request, and have them clean your > devel/helices tree out? You can start fresh that way. Yes, have somebody purge/delete/remove devel/helices/ntpclnt and everything below that. [ snip ] # ls devel/helices/ CVS netsnmp.lrp netsnmpd.lrp nettrapd.lrp ntpclnt # cvs -d:ext:[EMAIL PROTECTED]:/cvsroot/leaf remove devel/helices/ntpclnt [EMAIL PROTECTED]'s password: cvs remove: warning: directory CVS specified in argument cvs remove: but CVS uses CVS for its own purposes; skipping CVS directory ? devel/helices/ntpclnt/package/ntpclnt.lrp ? devel/helices/ntpclnt/target/etc/ntpclient.conf ? devel/helices/ntpclnt/target/etc/init.d/ntpclient ? devel/helices/ntpclnt/target/var/lib/lrpkg/ntpclnt.bktype ? devel/helices/ntpclnt/target/var/lib/lrpkg/ntpclnt.conf ? devel/helices/ntpclnt/target/var/lib/lrpkg/ntpclnt.help ? devel/helices/ntpclnt/target/var/lib/lrpkg/ntpclnt.list ? devel/helices/ntpclnt/target/var/lib/lrpkg/ntpclnt.local ? devel/helices/ntpclnt/target/var/lib/lrpkg/ntpclnt.version cvs server: Removing devel/helices/ntpclnt cvs server: file `devel/helices/ntpclnt/readme.txt' still in working directory cvs server: Removing devel/helices/ntpclnt/package cvs server: Removing devel/helices/ntpclnt/target cvs server: Removing devel/helices/ntpclnt/target/etc cvs server: failed to create lock directory for `/cvsroot/leaf/devel/helices/ntpclnt/target/etc' (/cvsroot/leaf/devel/helices/ntpclnt/target/etc/#cvs.lock): No such file or directory cvs server: failed to obtain dir lock in repository `/cvsroot/leaf/devel/helices/ntpclnt/target/etc' cvs [server aborted]: read lock failed - giving up -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
