cvs commit sticky tag is not a ranch

Hi....
I am trying to commit the following but I get an error that it says corret first, yeees, but how do I correct this???????/


cvs commit XML-Production.pl
cvs commit: sticky tag `1.12' for file `XML-Production.pl' is not a branch
cvs [commit aborted]: correct above errors first!
emedia% cvs commit XML-Production.pl
cvs commit: sticky tag `1.12' for file `XML-Production.pl' is not a branch
cvs [commit aborted]: correct above errors first!
LVL 3
rickyrAsked:
Who is Participating?
 
jkrConnect With a Mentor Commented:
This means that you have checked out a specific version of the file by doing,
for instance

    cvs update -r 1.12 CHANGELOG

When you check out something using a tag, that tag is made sticky on the
checked out version of the file. In this case, a version tag was made sticky.

The tag is applied during subsequent cvs operations such as commits.  Needless
to say, you cannot commit to 1.12 of CHANGELOG because there is no branch
there.

In general, you cannot go back to some old version of a file and commit a
change to it; you can only commit changes to the head of the trunk or a branch.

Just run  cvs update -A on these files to revert your working copy to the head
revisions.  If you made changes, they should be patched to the latest versions.
The update -A will clear sticky tags so you can proceed.

0
 
jkrCommented:
Did that help?
0
 
rickyrAuthor Commented:
Oh yes, cvs update -A has helped me alot.
I found a file called Entries in the CVS directory.
/MyFile/1.15/Thu Jul 26 15:36:11 2001//
if the sticky tag is set then the line will look this...
/MyFile/1.15/Thu Jul 26 15:36:11 2001//T1.12
If you remove the Tn.nn then that also clears the sticky tag.

Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.