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.

Description of problem:
OpenChange links against an internal Samba library which is wrong. The OpenChange project wanted to fix that correctly but did not do so yet.

However we should not link against internal samba libraries. As a workaroudn the DEBUG macro should be added to an OpenChange header file to work around the problem.

Else we will always have to update OpenChange if we change Samba.

We should work with Samba upstream to implement a correct fix for upcoming Samba and OpenChange versions.

I tried to address this in Fedora using these three commits:
http://pkgs.fedoraproject.org/cgit/openchange.git/commit/?id=3e7f4bcbf8c584
http://pkgs.fedoraproject.org/cgit/openchange.git/commit/?id=e0dd24b23a1300
http://pkgs.fedoraproject.org/cgit/openchange.git/commit/?id=06f95d04bb816d

These are related to OpenChange 2.3. The changes are not compatible with 2.2 (Fedora 22), neither with 2.0 which is shipped in RHEL 7.2.

I suggest to update OpenChange to 2.3 version and apply these changes (basically get to the version as is in the Fedora 23 right now). It'll help significantly with the maintenance and such.

(In reply to Milan Crha from comment #1)
> I suggest to update OpenChange to 2.3 version and apply these changes
> (basically get to the version as is in the Fedora 23 right now). It'll help
> significantly with the maintenance and such.

I marked this bug report as a rebase request due to the above reason.

I have the rebase ready, it only requires rebuild of the evolution-mapi, for which I filled bug #1314261. These two are supposed to be released together. I'll postpone release/commit of the rebase until the evolution-mapi bug is also approved.

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.

https://rhn.redhat.com/errata/RHBA-2016-2206.html