Fixes are available
Rational ClearCase Fix Pack 03 (8.0.0.3) for 8.0
Rational ClearCase Fix Pack 11 (8.0.0.11) for 8.0
Rational ClearCase Fix Pack 12 (8.0.0.12) for 8.0
Rational ClearCase Fix Pack 13 (8.0.0.13) for 8.0
Rational ClearCase Fix Pack 14 (8.0.0.14) for 8.0
Rational ClearCase Fix Pack 15 (8.0.0.15) for 8.0
Rational ClearCase Fix Pack 16 (8.0.0.16) for 8.0
Rational ClearCase Fix Pack 17 (8.0.0.17) for 8.0
Rational ClearCase Fix Pack 18 (8.0.0.18) for 8.0
Rational ClearCase Fix Pack 19 (8.0.0.19) for 8.0
Rational ClearCase Fix Pack 20 (8.0.0.20) for 8.0
Rational ClearCase Fix Pack 21 (8.0.0.21) for 8.0
APAR status
Closed as Permanent restriction.
Error description
Headline: rebase fails to propagate new baseline dependency hierarchy Description: When a component is included at multitple points in a baseline dependency tree, and a stream based upon the root composite baseline has also made baselines in the same component and the parent stream removes the component from one of its inclusion points and the child stream rebases onto the new root composite baseline Then a new baseline in the child stream will still have that component included at its multiple inclusion points. Steps to reproduce: --------------------- =? Create C1, C2, C3, C4 components and projects C1_MAIN, C2_MAIN, C3_MAIN and C4_MAIN. Create 2 or 3 baselines on each component. =? Create composite component COMP_BLD and create a read only project called 'COMP_INT_Proj'. And do edit baseline dependency as below. COMP_BLD C1 C2 =? Create build tree composite component BuildTree_BLD and create a read only project called 'Project_1' and do edit baseline dependency as below. Baseline shall be BuildTree_BLD_BL1_Project_1_Int BuildTree_BLD C3 COMP_BLD C1 C2 =? Create second buildtree project 'Project_2' using Project_1 baseline 'BuildTree_BLD_BL1_Project_1_Int'. Override component C3 and make baseline on Project_2. =?Go Back to Project_1. Now add C4 under BuildTree_BLD by using edit baseline dependency as below. And make a baseline. Baseline shall be 'BuildTree_BLD_BL2_Project_1_Int' BuildTree_BLD C3 C4 COMP_BLD C1 C2 =? Go back to project 'COMP_INT_Proj' and add C4 under COMP_BLD and make one baseline. COMP_BLD C1 C2 C4 =? Go to project 'Project_1' and rebase COMP_BLD which is created on COMP_INT_Proj. And make one baseline. Baseline shall be BuildTree_BLD C3 C4 COMP_BLD C1 C2 C4 =? Go to project 'Project_2'. And rebase to project_1 baseline (BuildTree_BLD_BL3_Project_1_Int). Now override C3 again and make one baseline. BuildTree_BLD C3 C4 COMP_BLD C1 C2 C4 =?Go to project 'project_1'. And remove the C4 from BuildTree_BLD by using Edit baseline dependency window. And make one more baseline 'BuildTree_BLD_BL4_Project_1_Int'. BuildTree_BLD C3 COMP_BLD C1 C2 C4 =?Go to project 'Project_2'. Rebase to baseline 'BuildTree_BLD_BL4_Project_1_Int'. After this step you can see C4 will be always present in Edit Baseline Dependency window. BuildTree_BLD C3 C4 COMP_BLD C1 C2 C4 'cleartool mkbl' in now says 'no new baselines are needed' At this point, if you go to Properties of Stream ? Configuration, it says BuildTree_BLD C3 COMP_BLD C1 C2 C4 now rebase to a new override of C4 to make a new baseline necessary. Make a new baseline. Then show its properties. The hierarchy matches the most recent 'Edit Baseline Dependency window', not the most recent 'Stream Configuration' ---------------------------------------------------- Workaround: Edit Baseline Dependencies in the child stream and make the required change (== cleartool mkbl -ddepends ...)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** This is not a defect, but works as designed
Problem conclusion
na
Temporary fix
Comments
APAR Information
APAR number
PM59761
Reported component name
CLEARCASE WIN
Reported component ID
5724G2900
Reported release
712
Status
CLOSED PRS
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-03-05
Closed date
2012-06-27
Last modified date
2012-06-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
Document Information
Modified date:
27 June 2012