https://bugzilla.novell.com/show_bug.cgi?id=851065
https://bugzilla.novell.com/show_bug.cgi?id=851065#c5
Petr Mladek changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |NEEDINFO
CC| |bnc-team-gnome@forge.provo.
| |novell.com,
| |dimstar@opensuse.org,
| |tchvatal@suse.com
InfoProvider| |jcheung@suse.com
See Also| |https://bugs.freedesktop.or
| |g/show_bug.cgi?id=65432
--- Comment #5 from Petr Mladek 2013-12-05 13:33:58 UTC ---
It seems that we are affected by the bug
https://bugs.freedesktop.org/show_bug.cgi?id=65432.
The symbol "hb_icu_get_unicode_funcs" has been removed in harfbuzz-0.9.20, see
http://upstream-tracker.org/compat_reports/harfbuzz/0.9.19_to_0.9.20/abi_com....
They removed the symbol but did not bump the SONAME version because it was
still alpha release :-(
libreoffice package currently has the following atomatic dependency:
libharfbuzz-icu.so.0()(64bit)
libharfbuzz.so.0()(64bit)
It is not enough because, so.0 is used by all harfbuzz alpha versions and they
are not backward compatible.
I see several possibilities:
1. Add a hack into specfile and require the exact "libharfbuzz-icu*" package
version that was used during build. I am slightly afraid of this because such
bugs tends to shoot us into the other leg sooner or later. We would need to do
this in all other packages that require harfbuzz. Then it might be a nightmare
to update the system if the packages come from different repositories.
2. Another possibility would be to bundle some workling harfbuzz library with
the package. It is easy. We already do this for builds on older distributions.
3. Ignore this problem if it is a corner case. I wonder where the incompatible
"libharfbuzz-icu0" package comes from. In usual cases, both "libreoffice" and
"libharfbuzz-icu0" packages should come from the same repository and they
should be binary compatible.
Note that https://bugs.freedesktop.org/show_bug.cgi?id=65432#c1 suggests that a
stable harfbuzz release should be out within few weeks. This should avoid the
problem in the next releases and builds.
In each case, the solution is "easy". It is enough to upgrade/downgrade the
package libharfbuzz-icu0 to build from the same repository as yout
"libreoffice" package.
If anyone still see the problem. Could you please paste output from the
following command?
rpm -qi libharfbuzz-icu0
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.