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.

Bug 1044625

Summary: cannot rebuild pyliblzma on RHEL7
Product: Red Hat Enterprise Linux 7 Reporter: jcpunk
Component: pyliblzmaAssignee: James Antill <james.antill>
Status: CLOSED CURRENTRELEASE QA Contact: Ales Zelinka <azelinka>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: azelinka, csieh, dmach, james.antill, jfeeney, jscotka, manuel.wolfshant, misterbonnie, redhatbugs, riehecky, tis
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: pyliblzma-0.5.3-10.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 12:56:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1012790, 1023810, 1055688    
Attachments:
Description Flags
mock config none

Description jcpunk 2013-12-18 17:20:12 UTC
Description of problem: %check fails for rebuilding pyliblzma-0.5.3-8.el7.src.rpm on RHEL7


Version-Release number of selected component (if applicable):pyliblzma-0.5.3-8.el7.src.rpm


How reproducible: 100%


Steps to Reproduce:
1. load RHEL7 and listed BuildRequires
2. rpmbuild --rebuild pyliblzma-0.5.3-8.el7.src.rpm
3. %check fails to run

Actual results:
Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.tE2l5u
+ umask 022
+ cd /builddir/build/BUILD
+ cd pyliblzma-0.5.3
+ /usr/bin/python setup.py test
running test
running egg_info
writing pyliblzma.egg-info/PKG-INFO
writing top-level names to pyliblzma.egg-info/top_level.txt
writing dependency_links to pyliblzma.egg-info/dependency_links.txt
reading manifest file 'pyliblzma.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'pyliblzma.egg-info/SOURCES.txt'
running build_ext
copying build/lib.linux-x86_64-2.7/lzma.so -> 
Traceback (most recent call last):
  File "setup.py", line 81, in <module>
    test_suite = 'tests',
  File "/usr/lib64/python2.7/distutils/core.py", line 152, in setup
    dist.run_commands()
  File "/usr/lib64/python2.7/distutils/dist.py", line 953, in run_commands
    self.run_command(cmd)
  File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command
    cmd_obj.run()
  File "/usr/lib/python2.7/site-packages/setuptools/command/test.py", line 138, in run
    self.with_project_on_sys_path(self.run_tests)
  File "/usr/lib/python2.7/site-packages/setuptools/command/test.py", line 118, in with_project_on_sys_path
    func()
  File "/usr/lib/python2.7/site-packages/setuptools/command/test.py", line 164, in run_tests
    testLoader = cks
  File "/usr/lib64/python2.7/unittest/main.py", line 94, in __init__
    self.parseArgs(argv)
  File "/usr/lib64/python2.7/unittest/main.py", line 149, in parseArgs
    self.createTests()
  File "/usr/lib64/python2.7/unittest/main.py", line 158, in createTests
    self.module)
  File "/usr/lib64/python2.7/unittest/loader.py", line 128, in loadTestsFromNames
    suites = [self.loadTestsFromName(name, module) for name in names]
  File "/usr/lib64/python2.7/unittest/loader.py", line 103, in loadTestsFromName
    return self.loadTestsFromModule(obj)
  File "/usr/lib/python2.7/site-packages/setuptools/command/test.py", line 35, in loadTestsFromModule
    tests.append(self.loadTestsFromName(submodule))
  File "/usr/lib64/python2.7/unittest/loader.py", line 100, in loadTestsFromName
    parent, obj = obj, getattr(obj, part)
AttributeError: 'module' object has no attribute 'test_liblzma'
error: Bad exit status from /var/tmp/rpm-tmp.tE2l5u (%check)
    Bad exit status from /var/tmp/rpm-tmp.tE2l5u (%check)

Expected results:
able to rebuild source rpm

Additional info:
Related Debian bug report of similar behavior: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614627

Comment 2 jcpunk 2014-01-06 21:56:20 UTC
Created attachment 846317 [details]
mock config

added mock config to replicate problem

Comment 3 Tuomo Soini 2014-01-18 22:57:24 UTC
Fix for thsis is very simple:

BuildRequires:    python-test

Comment 4 James Antill 2014-01-22 15:40:20 UTC
*** Bug 1048897 has been marked as a duplicate of this bug. ***

Comment 5 James Antill 2014-01-22 15:41:00 UTC
*** Bug 1028571 has been marked as a duplicate of this bug. ***

Comment 9 John Feeney 2014-03-21 21:43:38 UTC
*** Bug 1055688 has been marked as a duplicate of this bug. ***

Comment 12 Ludek Smid 2014-06-13 12:56:21 UTC
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.