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.
(In reply to Honza Horak from comment #2)
> What's the point of this BZ on top of Bug #2168193?
Two components need to be updated for the change to take effect. BZ#2168193 is for the pyproject-rpm-macros component (which adds the subpackage), and this one is a clone for the redhat-rpm-config component (which pulls in the subpackage).
FYI there still the issue with RHEL-9.2 and 9.3 nightly composes:
package: pyproject-srpm-macros-1.6.2-1.el9.noarch from tested
unresolved deps:
(pyproject-rpm-macros = 1.6.2-1.el9 if pyproject-rpm-macros)
(In reply to Zdenek Veleba from comment #8)
> FYI there still the issue with RHEL-9.2 and 9.3 nightly composes:
> package: pyproject-srpm-macros-1.6.2-1.el9.noarch from tested
> unresolved deps:
> (pyproject-rpm-macros = 1.6.2-1.el9 if pyproject-rpm-macros)
How do you trigger this error?
$ repoquery -q --repo=RHEL9.2-AppStream --latest=1 pyproject-srpm-macros
pyproject-srpm-macros-0:1.6.2-1.el9.noarch
$ repoquery -q --repo=RHEL9.2-CRB --latest=1 pyproject-rpm-macros
pyproject-rpm-macros-0:1.6.2-1.el9.noarch
$ repoquery -q --repo=RHEL9.3-AppStream --latest=1 pyproject-srpm-macros
pyproject-srpm-macros-0:1.6.2-1.el9.noarch
$ repoquery -q --repo=RHEL9.3-CRB --latest=1 pyproject-rpm-macros
pyproject-rpm-macros-0:1.6.2-1.el9.noarch
That's output from dnf-repoclosure done on AppStream repo. (I should have checked what's going on and formulate it better.)
Actually the issue is that package in AppStream repo depends on package from CRB.
CRB is optional and unsupported repository.
(In reply to Zdenek Veleba from comment #10)
> That's output from dnf-repoclosure done on AppStream repo. (I should have
> checked what's going on and formulate it better.)
> Actually the issue is that package in AppStream repo depends on package from
> CRB.
> CRB is optional and unsupported repository.
Ugh. Would you please file a new bug? This looks like a release blocker. Thanks.
The AppStream package does not depend on a package from CRB. It depends explicitly on "(pyproject-rpm-macros = 1.6.2-1.el9 if pyproject-rpm-macros)" which does nothing in AppStream only.
It could be treated as "(nothing if never)" in the AppStream-only context.
(In reply to Miro Hrončok from comment #12)
> The AppStream package does not depend on a package from CRB. It depends
> explicitly on "(pyproject-rpm-macros = 1.6.2-1.el9 if pyproject-rpm-macros)"
> which does nothing in AppStream only.
>
> It could be treated as "(nothing if never)" in the AppStream-only context.
Huh. I had not considered that. It really should be okay. I now remember (other?) checks not recognizing rich dependencies like that properly.
The requirement is there just to enforce the version of pyproject-rpm-macros if installed. It is rather paranoid really and could be replaced by 2 conflicts if really needed, but works as is like a charm.
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 (redhat-rpm-config 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-2023:2228