Re: [Leaf-devel] cvs commit directory structure ???
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. Michael, You need to use import to add a directory of files. You can use add to make new directories. I get lock failures, even when I try to commit them one directory at a time. Where in our repository are you trying to commit/add/import files? Clearly, there is some approved process for doing this and I do not know what that is. Also, what is this limitation that all files must use *ONLY* lowercase letters??? This was explained recently. http://www.mail-archive.com/leaf-devel%40lists.sourceforge.net/msg05217.html -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- 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
Re: [Leaf-devel] cvs commit directory structure ???
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. ref. CVS Setup - Importing Directories http://sourceforge.net/docman/display_doc.php?docid=9960group_id=13751 Open Source Development with CVS - Starting A New Project http://cvsbook.red-bean.com/cvsbook.html#Starting_A_New_Project -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- 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
Re: [Leaf-devel] cvs commit directory structure ???
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
Re: [Leaf-devel] cvs commit directory structure ???
On Tue, 2002-07-16 at 06:32, Michael D. Schleif wrote: 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. Michael, We have no modules defined at this time. If you would like a module defined, please send me the appropriate information for CVSROOT/modules. http://cvs.leaf-project.org/cgi-bin/viewcvs.cgi/leaf/CVSROOT/ 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. I would need to see the commands you typed in to understand the lock file problem. It may have something to do with a prior command leaving your tree in an unstable state. Are there limitations to cvs remove? What is the cause of the lock problem? Yes. It will not remove directories. Again, I'm unsure. Would you post the commands you used? The information I'm working from is obtained from our leaf-cvs-commits list. http://www.mail-archive.com/leaf-cvs-commits%40lists.sourceforge.net/ -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- 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
Re: [Leaf-devel] cvs commit directory structure ???
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. [ snip ] 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. [ snip ] Is there some way to *transfer* a cvs module from my own cvs to sourceforge/leaf cvs? I have created a cvs environment for my own development. Since I already have [many of] my packages situated as local cvs modules, it would be most convenient if there is some way to move modules from cvs_A to cvs_B. Or, need I *export* a module from my own cvs prior to importing it into sourceforge/leaf cvs? -- 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
Re: [Leaf-devel] cvs commit directory structure ???
On Tue, 2002-07-16 at 06:52, Michael D. Schleif wrote: 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. [ snip ] 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. [ snip ] Is there some way to *transfer* a cvs module from my own cvs to sourceforge/leaf cvs? Michael, Yes. A tarball of your current repository is needed for this. ref. # Introduction to SourceForge.net Project CVS Services Import of Existing CVS Repositories https://sourceforge.net/docman/display_doc.php?docid=768group_id=1 I have created a cvs environment for my own development. Since I already have [many of] my packages situated as local cvs modules, it would be most convenient if there is some way to move modules from cvs_A to cvs_B. CVS doesn't sync repositories. Either you use your local one or the one on SF. Or, need I *export* a module from my own cvs prior to importing it into sourceforge/leaf cvs? This is one method, but you'll lose your history doing it this way. -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- 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
[Leaf-devel] cvs commit directory structure ???
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. Also, what is this limitation that all files must use *ONLY* lowercase letters??? Please, enlighten me . . . -- 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
