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.
DescriptionBranislav Náter
2013-03-14 12:06:37 UTC
Description of problem:
We are doing some checks regarding correct placement of *.py[co] files in rpm packages.
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.
Could you please move files to /usr/lib64?
Or should this package be build as noarch?
Version-Release number of selected component (if applicable):
sssd-1.9.3-1.el7.x86_64.rpm
Actual results:
sssd-1.9.3-1.el7.x86_64.rpm]: /usr/lib/python2.7/site-packages/SSSDConfig/__init__.py$
sssd-1.9.3-1.el7.x86_64.rpm]: /usr/lib/python2.7/site-packages/SSSDConfig/__init__.pyc$
sssd-1.9.3-1.el7.x86_64.rpm]: /usr/lib/python2.7/site-packages/SSSDConfig/__init__.pyo$
sssd-1.9.3-1.el7.x86_64.rpm]: /usr/lib/python2.7/site-packages/SSSDConfig/ipachangeconf.py$
sssd-1.9.3-1.el7.x86_64.rpm]: /usr/lib/python2.7/site-packages/SSSDConfig/ipachangeconf.pyc$
sssd-1.9.3-1.el7.x86_64.rpm]: /usr/lib/python2.7/site-packages/SSSDConfig/ipachangeconf.pyo
<snip>
Expected results:
Correct placement of files under /usr/lib64 or package built as noarch
Verified the bug on SSSD python pacakage version: python-sssdconfig-1.11.2-10.el7.noarch
All python files have been moved to new noarch package - python-sssdconfig
[root@rhel-7 sssd]# rpm -ql python-sssdconfig | grep python
/usr/lib/python2.7/site-packages/SSSDConfig
/usr/lib/python2.7/site-packages/SSSDConfig-1.11.2-py2.7.egg-info
/usr/lib/python2.7/site-packages/SSSDConfig/__init__.py
/usr/lib/python2.7/site-packages/SSSDConfig/__init__.pyc
/usr/lib/python2.7/site-packages/SSSDConfig/__init__.pyo
/usr/lib/python2.7/site-packages/SSSDConfig/ipachangeconf.py
/usr/lib/python2.7/site-packages/SSSDConfig/ipachangeconf.pyc
/usr/lib/python2.7/site-packages/SSSDConfig/ipachangeconf.pyo
/usr/lib/python2.7/site-packages/SSSDConfig/sssd_upgrade_config.py
/usr/lib/python2.7/site-packages/SSSDConfig/sssd_upgrade_config.pyc
/usr/lib/python2.7/site-packages/SSSDConfig/sssd_upgrade_config.pyo
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.