RE: Why does 'cvs admin -l<branchname>' complain that my branch is absent?

[Teala Spitzbarth]

Oh, yuck.....

I know from other email that Larry has sent me that the way CVS handles
branches can be problematic in some commands - i.e. CVS doesn't actually

create a branched version of each file when the branch is created (that
is why you 
see the magic zero in that fake branch revision number for files that 
haven't been modified yet).  This behavior can sometimes cause conflict
with how RCS 
works under the covers.   For example, the log command will have
erroneous output
for files on branches when they are first modified, due to the fact that
the "previous" (magic zero) revision on the branch doesn't really exist
yet
at the RCS level, causing the log code to fall into an error condition.
(Larry may
have fixed this is the development version by now...)

I believe the admin -l command is fundamentally an RCS level command -
so I bet
it can't lock unmodified versions on a branch, because at the RCS level,
those
versions of the file don't really "exist".....

There are versions of commit-info scripts kicking around that allow you
to 
lock branches - you may want to consider one of those.  See for example:

http://ccvs.cvshome.org/servlets/GetAttachment?msgId=1229&attachId=1&lis
tName=info

(Note:  I'm pretty sure this script got munged somehow and the exit 0
should be outside
of the for loop, otherwise recursive commits might slip through onto a
locked branch)

Cheers,
Teala

-----Original Message-----
From: Whitlock, Ginger [mailto:address@hidden
Sent: Wednesday, January 09, 2002 7:33 PM
To: address@hidden
Subject: Why does 'cvs admin -l<branchname>' complain that my branch is
absent?


Hello CVS-Guru's

We're running Solaris 8, with CVS 1.11

Might someone help me with an error I'm receiving with attempting to
lock a
branch in CVS?

I receive an error complaining that my branch is absent:

cvs admin:
/opt/cvs/customer1/software/src/com/gers/sales/order/persist/OrderDaoFac
tory
.java,v: branch customer1-0_5C1_00E absent  

running cvs log to verify the branch exists :

   customer1-0_5C1_00E: 1.11.0.2   

and it does.

I thought I'd found a work around , (cvs admin -bcustomer1-0_5C1_00E
<repository>, to set the default to this branch then
cvs admin -l -L <repository> , to lock what is now the branch at 'tip' ,
followed by cvs admin -b <repository> to set it back to the trunk)
....and this works well as long as every-single file on the branch has
actually been modified, if there are any that have not, the cvs command
to
lock bombs with an assertion failed error from hash.c

I appreciate any assistance with this matter.

Thank you
Ginger Whitlock





_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs