Issue 72149 - Symbolic link not created in patch set when upgrading a versioned library to a newer version
Summary: Symbolic link not created in patch set when upgrading a versioned library to ...
Status: CLOSED FIXED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: current
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: OOo 2.2
Assignee: stefan.baltzer
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-30 17:25 UTC by ooo
Modified: 2007-03-13 12:48 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description ooo 2006-11-30 17:25:31 UTC 
Hi Ingo,

As commented in CWS icuupgrade and discussed, the necessary link with major
number to a newer version of a versioned library (=> different name) isn't
created by a patch set installation. Please add this issue to CWS icuupgrade.

Thanks
  Eike
Comment 1 ooo 2006-12-01 12:19:40 UTC 
Aligning target with CWS icuupgrade.
Comment 2 ingo.schmidt-rosbiegal 2006-12-01 15:57:13 UTC 
Fixed with a very special fix. 
If a link changes a name (like in this case the version number from 26 to 36),
it has to be included into the patch. For Linux this means, that the link has to
be included into core05u instead of core05, because core05 must not be included
into a patch. Therefore the flag FORCE_INTO_UPDATE_PACKAGE was introduced. Links
with this flag are integrated into the "u"-RPMs instead of the standard-RPMs.
This can only work, if the name of the link changes. If the name does not
change, the link has to stay in the same RPM as in the past, because the link is
already assigned to a package in the system database.
Concerning to Eike, it is sufficient to add the link libicuxyz.so.36. The link
libicuxyz.so does not change its name and therefore has to stay in core05-RPM.
Therefore libicuxyz.so points to the old library libicuxyz.so.26.0.1.1, even
after installing the patch. New is only the link libicuxyz.so.36, that points to
the link libicuxyz.so.36.0. And this link points to the new file
libicuxyz.so.36.0.1.1.
Comment 3 ooo 2006-12-01 18:45:54 UTC 
Reassigning to QA for verification.

Some clarification on "libicuxyz.so points to the old library
libicuxyz.so.26.0.1.1, even
after installing the patch": linkage of the libicu*.so files is always done
using the name including the version number, e.g. libicuuc.so.36, so a link with
the name libicuuc.so effectively is not needed.
Comment 4 stefan.baltzer 2006-12-06 15:57:44 UTC 
SBA: Verified in CWS icuupgrade.
Comment 5 stefan.baltzer 2007-03-13 12:48:06 UTC 
SBA: OK in OOF680_m11. Closed.