PM58859: conflict detected with symlinks in Synergy 7.1.0.5 in Web mode

Rational Synergy Fix Pack 6 (7.1.0.6) for 7.1
Rational Synergy Fix Pack 3 (7.2.0.3) for 7.2
Rational Synergy Fix Pack 6 (7.2.0.6) for 7.2
Rational Synergy Interim Fix 1 for 7.2.0.6
Rational Synergy Interim Fix 2 for 7.2.0.6
Rational Synergy Fix Pack 7 (7.2.0.7) for 7.2
Rational Synergy Interim Fix 1 for 7.2.0.7
Rational Synergy Interim Fix 2 for 7.2.0.7
Rational Synergy Interim Fix 3 for 7.2.0.7

APAR status

• Closed as program error.

Error description

• Tested with Linux and Synergy 7.1.0.5 in web mode
  
  1) Conflict reported immediately after creating a symlink.
  -start a new session in Web mode.
  -create a task
  -create a new project with a Copy based workarea.
  -create 2 directories in the Root directory: 'sources' and
  'test1'.
  -add a file 'main.c' in the directory 'sources'.
  -add a new file called 'main.c' in the 'test1' directory.
  -select the file 'main.c' in the 'test1' directory, then click
  on: Edit/Change Type.
  Change the type to Symlink.
  -right click on the main.c symlink, and select Properties.
  Set the Custom Link to' field to:
  ../sources/main.c
  =? At this stage we have now a Symlink 'main.c' pointing to a
  real file: ../sources/main.c
  
  However if you run a Sync on the Project, it detects a conflict
  on the Symlink:
  'Work area change to checked-out file'
  
  =? So there is a conflict detected, although we just created a
  new object.
  
  For information, a Java session in Traditional mode does not
  return any conflict if we do exactly the same operations.
  
  
  
  2) Conflict never resolved.
  In the Workarea Conflict dialog, right click on the symlink
  having the conflict and select:
  'Keep work area changes'
  The conflict seems to be resolved.
  =? However, if you run a Sync again on the Project, the same
  conflict 'Work area change to checked out file' is reported.
  As long as you resolve the conflict with the option 'Keep work
  area changes', a new Sync will detect a new conflict.
  
  =? So we have this conflict again and again immediately even
  when we resolve it.
  
  
  3) The only way to resolve this conflict is to select:
  'Discard Workarea changes'.
  Select that option.
  The conflict is now resolved (if you run a Sync on the project
  again, no conflict is reported).
  Then directly in the Workarea modify the file 'sources/main.c'.
  Then run a Sync on the project.
  
  Result:
  -2 conflicts 'Work area change to checked-out file' are
  reported:
  ---One for the sources/main.c file
  ---One for the test1/main.c symlink.
  
  =? We have a conflict on the Symlink as well as on the object.
  (with the JC in traditional mode, only the conflict on the file
  sources/main.c is reported).
  (If you had 10 symlinks pointing to the same file sources/main.c
  you would have 11 conflicts.)
  
  
  4) To resolve the conflict we decide to keep the changes from
  the workarea.
  Select the 2 lines in the conflict dialog, for the
  sources/main.c file and for the test/main.c  symlink.
  And resolve the conflict using the option 'keep workarea
  changes'.
  
  -Run a Sync after resolving the conflicts.
  =? The conflict on the file sources/main.c is resolved.
  =? The conflict on the symlink appears again.
  
  The only way to resolve the conflict on the Symlink is to select
  'Discard workarea changes'.
  
  If the conflict on the symlink was reported because of the
  change on the file it is pointing to, then resolving the
  conflict on the file sources/main,c should resolve the conflict
  on the symlink.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  conflict detected with symlinks in Synergy 7.1.0.5 in Web
  mode
  

Problem conclusion

• Fixed in Rational Synergy 7.1.0.6 and planned for 7.2.0.3
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TLOGIC SYNERGY

• Fixed component ID

  5724V66SN

Applicable component levels

• R710 PSN

     UP