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:
We are doing some checks regarding correct placement of *.py[co] files in rpm packages. So maybe this is false positive, but...

In your x86_64 package, we found *.py[co] files placed under /usr/lib/ directory. Our test expect *.py[co] files from 64b package to be placed in /usr/lib64/ dir or package to be build as noarch package.

Can this package be build as noarch?
Or can the yum bits be moved to a noarch subpackage?

Version-Release number of selected component (if applicable):
subscription-manager-1.8.2-1.el7.x86_64.rpm

Moving bugs from 7.0 to 7.1

Acking 7.1

Unfortunately the subscription-manager does have an architecture.  The RHSMD daemon is written in C and is bundled in with the subscription-manager subpackage.  The portions of the application placed in /usr/lib are Yum plugins which are read from /usr/lib/yum-plugins by default in Yum. [1]

Ideally we would package the Yum plugins in a noarch subpackage, but RPM does not support having a subpackage that is a different architecture [2].  Consequently, I don't know of a solution as we want RHSMD to be included in the subscription-manager subpackage.  If RHSMD were a separate package, we would have a circular dependency issue as the daemon is meant to be required by subscription-manager and the daemon requires subscription-manager to be fully functional.

[1] See 'pluginpath' at http://linux.die.net/man/5/yum.conf
[2] https://bugzilla.redhat.com/show_bug.cgi?id=227790#c10