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.

Created attachment 1894011 [details]
nothing provides libxml2(x86-64) = 2.9.7-11.el8 needed by libxml2-devel, (got version 2.9.7-14.el8 provided by libxml2)

Description of problem:


From https://bugzilla.redhat.com/show_bug.cgi?id=2102548, we are facing a limitation from OBS (https://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks#Adding_multiple_repositories_to_a_project):

> The order of the included repositories is important: The BuildService will try to use a package from the first repository that includes the package, even if the version doesn't match.

From https://lists.opensuse.org/archives/list/buildservice@lists.opensuse.org/message/HHGG5FZEZZYK33BXP7QEEOO67B2XRPE2/, we support to move OBS repo order in "BaseOS > AppStream":

> However, this order is supposed to work, see https://bugzilla.redhat.com/show_bug.cgi?id=2102548#c8. Based on some internal discussions, I expect that we treat violations of the BaseOS > AppStream rule as content glitches that need to be fixed.

It does solve most of the problem, but my project still coming with 15 packages with missing dependency (https://build.opensuse.org/project/monitor/home:alvistack?arch_x86_64=1&defaults=0&repo_CentOS_8_Stream=1&unresolvable=1):

> nothing provides libxml2(x86-64) = 2.9.7-11.el8 needed by libxml2-devel, (got version 2.9.7-14.el8 provided by libxml2)

From https://pkgs.org/search/?q=libxml2, we could find that libxml2-devel-2.9.7-13.el8.x86_64.rpm and libxml2-devel-2.9.7-14.el8.x86_64.rpm ONLY exists in AppStream, but missing from BaseOS. Since libxml2-2.9.7-14.el8.x86_64.rpm is now coming from BaseOS ONLY, corresponding libxml2-devel-2.9.7-14.el8.x86_64.rpm should also co-exist in BaseOS, too?

With AlviStack's "Just patch it, don't wait" principal, I solve this issue for my self by backport libxml2 2.9.14 from Debian Sid / Fedora Rawhide / openSUSE Thumbleweed with OBS: https://build.opensuse.org/package/show/home:alvistack/GNOME-libxml2-2.9.14.

RHEL repo enablement in OBS continues to not understand the RHEL content split and we cannot fix that.

Both BaseOS and AppStream are required for RHEL installation and operation.  BaseOS is the foundational repo, with AppStream requiring BaseOS for dependencies.  In this specific case, it is perfectly fine for BaseOS to contain libxml2 and AppStream to contain libxml2-devel as both repositories are required to be enabled.