Issue 76897 - CVS: cannot move branch tag
Summary: CVS: cannot move branch tag
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: _openoffice.org CVS (obsolete) (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks: 2587 76821
  Show dependency tree
 
Reported: 2007-05-03 10:59 UTC by rt
Modified: 2007-05-09 09:35 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Log to reproduce what I did (1.58 KB, text/plain)
2007-05-03 11:04 UTC, rt
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description rt 2007-05-03 10:59:04 UTC
- create a branch on revision A of file x
   cvs tag -d mybranch <filename>
- update that file to some other revision B
   cvs update -r <B> <filename>
- not try to move the branch tag
   cvs tag -F -b mybranch <filename>
  that just results in a message 
  cvs tag: <filename>: Not moving branch tag `mybranch' from <A> to <B>.

Removing a branch tag does not work either:
  cvs tag -d mybranch <filename>
  cvs tag: Not removing branch tag `mybranch' from `<filename>,v'.
Comment 1 rt 2007-05-03 11:01:04 UTC
Setting to 'P1': moving tags is necessary in our CWS scenario. You cannot
'resync' without that.
Comment 2 rt 2007-05-03 11:04:00 UTC
Created attachment 44831 [details]
Log to reproduce what I did
Comment 3 Martin Hollmichel 2007-05-03 12:44:16 UTC
I just called collab.net support directly via phone to take care of this issue
immediately.
Comment 4 Unknown 2007-05-03 12:46:16 UTC
Thank you for contacting Collabnet Customer Support. Based on the information
that has been provided to us, we will start our research & we would provide an
update as soon as we have gathered adequate information.

Regards,
Ramya
Support Operations
Comment 5 Unknown 2007-05-03 13:27:25 UTC
We were able to replicate the issue.We are working on this with high priority,
will update you with our findings.

Regards,
Ramya
Support Operations
Comment 6 Unknown 2007-05-03 14:26:46 UTC
There has been a lot of changes in the CVS side of things from 3.5.1 to 4.5.2.
Currently cvs tag will only do those options(move/delete) on an already
existing branch if the -B flag is provided. 

We are working on certain options where  when adding  -B to    
 cvs tag -F -b mybranch <filename> ----> cvs tag -B -F -b mybranch <filename>
we are able to move the branch tag

-bash-2.05b$ cvs tag
Usage: cvs tag [-bcdFflR] [-r rev|-D date] tag [files...]
        -b      Make the tag a "branch" tag, allowing concurrent development.
        -B      Allows -F and -d to disturb branch tags.  Use with extreme care.
        -c      Check that working files are unmodified.
        -d      Delete the given tag.
        -F      Move tag if it already exists.
        -f      Force a head revision match if tag/date not found.
        -l      Local directory only, not recursive.
        -R      Process directories recursively.
        -r rev  Existing revision/tag.
        -D      Existing date.

According to the code(src/tag.c), the two operations are allowed only if -B
option is specified.

Regards,
Ramya
Support Operations
Comment 7 rt 2007-05-03 14:51:15 UTC
Ramya,

Thanks for pointing to that description. I'll check how to add '-B' option into
our tooling.

Ruediger
Comment 8 Unknown 2007-05-03 15:02:38 UTC
FYI,
The option -B is available only in upgraded CVS client version 1.11.2 & not in 1.11.

Regards,
Ramya
Support Operations
Comment 9 Unknown 2007-05-03 15:52:31 UTC
According to the CVS NEWS file, as of version 1.11.2:

   "tag" and "rtag" commands will no longer move or delete branch
   tags unless you use the new -B option.  (This prevents accidental
   changes to branch tags that are hard to undo.)

Regards,
Ramya
Support Operations
Comment 10 Unknown 2007-05-03 15:54:25 UTC
Bringing down the priority as the feature does work along with extra flag for
security/accidental reasons .
Comment 11 Unknown 2007-05-04 07:46:54 UTC
I am marking this as fixed. Please feel free to get back to us on any further
clarification.

Regards,
Ramya
Support Operations
Comment 12 rt 2007-05-09 09:34:21 UTC
Verified, everything works well.
Comment 13 rt 2007-05-09 09:35:25 UTC
closing.