Red Hat Bugzilla – Bug 809466
libreoffice-core (unintentionally) provides libraptor.so.1()() and librdf.so.0()()
Last modified: 2012-06-20 08:53:36 EDT
Description of problem:
Because of libreoffice incrusion into ComputeNode we need to add mythes-*.noarch, hyphen-*.noarch and hunspell-*.noarch packages into Computenode chanell.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
We build with internal raptor, because the system one is not usable for us (comment in configure.in says: "versions before 1.0.8 write RDF/XML that is useless for ODF (@xml:base)"). The Provides are generated by rpmbuild; I do not know what can be done about that.
dtardon->jnovy: Is there a way to filter the generated Provides list?
I suppose that we could just change the redland libraries' names, e.g., add a 'lo' suffix. That would require (small) change in 3 or 4 source files, which is IMHO quite manageable...
+1 for changing the provides instead of filtering them.
dgregor said "I'll manually filter libreoffice from ComputeNode for the beta", so that part of urgent is taken care of.
caolanm->dtardon: want to have a shot at it. Disabling AutoProvides and doing that manually is real painful. Fridrich was talking about trying to do custom sonames for all the "external" libraries we have to to bundle upstream.
Same problem exists for e.g. xmlsec and other stuff we have to bundle downstream.
Done for redland libs. There is actually no problem with libxmlsec and mythes, because we build them as static archives.
dtardon->caolanm: fixed in F-16, as usual.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
No Documentation needed
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.