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.

Rebuild evolution-mapi and openchange with Samba rebase.

Samba was rebased to 4.16.1 with bug 2077487. Use side-tag c9s-build-side-463.

The packages [1] are slowly processing through its gating, but they will fail, because the server they use had been accidentally removed (note later target milestone for QA).

Anyway, I suppose the errata thing will be done in a similar way as with the bug #2081620, right?


[1] openchange-2.3-39.el9
    evolution-mapi-3.40.1-4.el9

The errata for the builds for the same sidetag (rhel-9.1.0-build-sidetag-101733-stack-gate) was just created.

https://errata.devel.redhat.com/advisory/95470

I am not sure if openchange-2.3-39.el9 and evolution-mapi-3.40.1-4.el9 builds will be added to the errata automatically or not.

I see that there are separate Errata for  openchange-2.3-39.el9 and evolution-mapi-3.40.1-4.el9 builds:

https://errata.devel.redhat.com/advisory/95468
https://errata.devel.redhat.com/advisory/95469

Correct, they have their own erratas.

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 (evolution-mapi bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2022:8104