Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Tue, 17 May 2005 15:45:29 -0600, "Lehman, Curtis" <CLehman at carrieraccess.com> wrote: > >I am trying to create a branch on a given tag in a given project. I get the >following error when I issue the command: > >C:\projects\Practice>cvs rtag -b -r T_curt_1 BR_TEST_CREATE_MODULE Practice >cvs [rtag aborted]: could not chdir to /Engineering/flexengine_sec: >Permission denied > >I have created windows user groups on a per project bases. The person >issuing the command does not have permission on other projects. He does have >permission for the "Practice" project. It seems like rtag is trying to >access more than just the project called out on the command line. > >1. Does rtag try to access all the projects, not just the "Practice" project >that is called out in the command line? > >2. If yes, is this proper operation or a bug that's going to get fixed? > >3. Is there another single command line equivalent I can try to get around >this problem? (I don't want to have to update my local copy to the tag and >then issue a branch command relative to what's in my sandbox.) > The command you are issuing is supposed to do this, right?: - base a branch tag BR_TEST_CREATE_MODULE on the existing tag T_curt_1 for the top level module Practice in the repository given by the CVS metadata in the sandbox where you are issuing the command. The reason for the failure might have something to do with the strange way CVSNT will build the CVSROOT/val-tags file on certain tag operations. I never understood the reason or advantage of this procedure. What it does is that it scans every single file in the complete repository for tag labels in order to put them all into the val-tags file as one line each and followed by the letter y. So there is no real use for this file because it does not list where the tags are found, it is just a list of tags existing "somewhere". In any case the process of scanning for these tags will sometimes put a very large delay on a cvs operation that was hit with the scan. Doesn't happen always though. But I guess that when it runs in a repository where you don't have access to all the modules there will be an access error, possibly that is what you see. I would test issuing the following command in the sandbox: cvs -t -t -t rtag -b .... (your command parameters) This will make CVSNT list what it is actually doing and you can cut-paste the output and post it back here for comment. /Bo (Bo Berglund, developer in Sweden)