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.
Bug 839487 - renamed test examples in python-nss-doc
Summary: renamed test examples in python-nss-doc
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-nss
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: beta
: 7.0
Assignee: John Dennis
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 880660
TreeView+ depends on / blocked
 
Reported: 2012-07-12 06:03 UTC by Aleš Mareček
Modified: 2012-12-11 14:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 880660 (view as bug list)
Environment:
Last Closed: 2012-12-11 14:57:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Aleš Mareček 2012-07-12 06:03:43 UTC
Description of problem:
Previous version of python-nss-doc in RHEL-6 has different naming of test examples.
RHEL-6:
$ rpm -ql python-nss-doc | grep "^.*\/test\/.*\.py\$"
/usr/share/doc/python-nss-0.11/test/cipher_test.py
/usr/share/doc/python-nss-0.11/test/digest_test.py
/usr/share/doc/python-nss-0.11/test/setup_certs.py
/usr/share/doc/python-nss-0.11/test/test_cert_components.py

RHEL-7:
$ rpm -ql python-nss-doc | grep "^.*\/test\/.*\.py\$"
/usr/share/doc/python-nss-0.12/test/setup_certs.py
/usr/share/doc/python-nss-0.12/test/test_cert_components.py
/usr/share/doc/python-nss-0.12/test/test_cipher.py
/usr/share/doc/python-nss-0.12/test/test_client_server.py
/usr/share/doc/python-nss-0.12/test/test_digest.py
/usr/share/doc/python-nss-0.12/test/test_pkcs12.py


Version-Release number of selected component (if applicable):
python-nss-doc-0.12-3.el7

How reproducible:
Always

Steps to Reproduce:
1. rpm -ql python-nss-doc | grep "^.*\/test\/.*\.py\$"

  
Actual results:
/usr/share/doc/python-nss-<VERISON>/test/test_<SPECIFIC TEST>

Expected results:
Same as in RHEL-6 like: /usr/share/doc/python-nss-<VERISON>/test/<SPECIFICTEST>_test
OR some documentation

Additional info:

Comment 3 John Dennis 2012-12-11 14:57:04 UTC
The test scripts were renamed to make them consistent with Python's automated test frameworks which search for test scripts whose name begins with "test_". Therefore all test scripts now begin with "test_". From this point forward all test scripts in python-nss will follow this convention, it was a mistake they weren't named that way from the beginning.

I don't see how this is a bug, this is a change occurring between RHEL versions which pulls in a different package version. There is no requirement that a new version of RHEL maintain the exact same set of files in a given package.


Note You need to log in before you can comment on or make changes to this bug.