Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
/usr/lib64/libocpf.so.0.9 in openchange-0.9-7.el6.x86_64 defines the "yyin" symbol (and other flex-related symbols). This can lead to collisions and bugs, so the symbols should be mangled or hidden. I do not see them in the Fedora 18 version, so this might have been fixed upstream.
(In reply to comment #2)
> RHEL 6.4 rebases openchange to 1.0. Can you recheck the rebased package?
I checked openchange-1.0-1.el6.x86_64, and the flex-generated symbols have a ocfp_ prefix, so this is indeed fixed through the rebase. Thanks.
There are two non-namespaced symbols remaining, "error_flag" and "indent", which should eventually be fixed as well, but the risk of a collision is lower there. libmapi-openchange defines "Subscribe", "Unsubscribe" (among others), but these appear to be low-risk, too.
Comment 4RHEL Program Management
2012-12-14 08:19:21 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
The list of conflicting symbols is open-ended in the sense that it depends on what other libraries use. Symbols starting with "yy" and generic terms such as "buffer", "mutex", "line" are suspicious, though.
I have tools to determine conflicting symbols by looking at entire composes at once. Apart from the heuristics mentioned above, it is not possible to test a single package in isolation.
(In reply to Florian Weimer from comment #7)
> The list of conflicting symbols is open-ended in the sense that it depends
> on what other libraries use. Symbols starting with "yy" and generic terms
> such as "buffer", "mutex", "line" are suspicious, though.
>
> I have tools to determine conflicting symbols by looking at entire composes
> at once. Apart from the heuristics mentioned above, it is not possible to
> test a single package in isolation.
So are you able to run your tool once fixed packages are ready?
Thanks
Tom
Comment 10RHEL Program Management
2013-08-27 10:15:58 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.