Opened 9 years ago

Closed 9 years ago

#179 closed defect (fixed)

Is LIBICU incomplete? AOO fails with ICUUC42 error

Reported by: Mat Owned by:
Priority: minor Milestone:
Component: yum Version:
Severity: medium Keywords: ICUUC
Cc:

Description

When installing AOO-4120-GA-base-en-US.wpi it lists as one of the requirements icu. Via Yum, libicu is installed, and it contains things like icuuc.dll. However, when starting OO, it pop up an error that icuuc42 is missing. These icu* dlls where present in the program directory of OO 3. Is this a build failure of AOO 4.1.2 in that it should use icuuc.dll instead of icuuc42.dll? Or does libicu miss the *42 versions of the icu dlls, or a forwarder for it?
(By the way, just copying the OO3 DLLs into the programs directory of OO412 makes the error go away but OO mostly disappears when starting). As it is, I cannot use AOO 4.1.2.

Change History (5)

comment:1 by dmik, 9 years ago

The ICU RPMs were updated to ICU 56.1, they have different DLL names. Please downgrade ICU to the previous level with

yum downgrade libicu

This should solve your problem. We will either provide forwarders or rebuild AOO against the new DLLs later.

comment:2 by Mat, 9 years ago

Just "yum downgrade libicu" didn't fix it, this downgraded from 56.1-3 to 56.1-1.oc00. Using the package manager, I downgraded to 4.2.1-1(oc00), and now AOO 4.1.2 seems to start properly.
Thanks for the quick reply, Mat

comment:3 by dmik, 9 years ago

It would but there was, by accident, a wrong package in the index that resulted it what you saw. Already removed.

comment:4 by Lewis Rosenthal, 9 years ago

An alternative way of handling this (just did) is to use ANPM's option to install specific release, and then select the 4.2.1-1 package for your arch.

Note that this will also only affect those of us with the experimental repo enabled, which is hopefully limited to people who can more easily handle such occurrences (just happened to me).

comment:5 by Silvan Scherrer, 9 years ago

Resolution: fixed
Status: newclosed

no news from the reporter, so we assume it's fixed

Note: See TracTickets for help on using tickets.