Branch tag broke my CVS - how can I repair it?

[Colin MacDonald]

I created a branch, tagged as cm_av_bug321, and this tagged, among 
others, a file that was version 1.3 (tagged as rel-3-0-3-10 in the list 
below).  That version 1.3 is the one that I was working with at the time.

In the meantime, a colleague decided to trash version 1.3 from CVS and 
reverted to 1.2.  The file hasn't changed since then.

Here's an extract from 'cvs log access_log.c':

Working file: access_log.c
head: 1.2
branch:
locks: strict
access list:
symbolic names:
        cm_av_bug321: 1.3.0.2
        rel-3-0-8-10: 1.2
        rel-3-0-7-10: 1.2
        rel-3-0-6-10: 1.2
        rel-3-0-5-10: 1.2
        rel-3-0-4-10: 1.2
        rel-3-0-3-10: 1.3
        rel-3-0-2-10: 1.2
        rel-3-0-1-10: 1.2

My branch tag, though, expects that 1.3 still exists.

Thus if I enter 'cvs status access_log.c' then I get:

cvs [status aborted]: could not find desired version 1.3 in <path 
snipped>/access_log.c,v

I can't move the branch tag to revision 1.2 - the response from 'cvs tag 
-F -r 1.2 cm_av_bug321 access_log.c' is:

cvs tag: access_log.c: Not moving branch tag `cm_av_bug321' from 1.3 to 1.2.

I want the cm_av_bug321 tag to refer to revision 1.2.  Any idea how I 
can do this?

Thanks,
Colin MacDonald