Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at

Bug 1595366

Summary: python-testfixtures FTBFS
Product: [Fedora] Fedora Reporter: Miro Hrončok <mhroncok>
Component: python-testfixturesAssignee: Björn 'besser82' Esser <besser82>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: low    
Version: rawhideCC: besser82
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-23 14:10:23 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:
Bug Depends On:    
Bug Blocks: 1565020, 1602938    

Description Miro Hrončok 2018-06-26 18:24:27 UTC
Description of problem: python-testfixtures FTBFS.

No matching package to install: 'python-nose-cov'

Version-Release number of selected component (if applicable): python-testfixtures-4.14.3-5

Steps to Reproduce: build in rawhide

I see several ways to solve this:

 1) nothing depends on python2-testfixtures so you drop the subpackage
 2) nothing depends on pythonX-testfixtures so you retire the package as a whole
 3) you can reintroduce python2-nose-cov and change the requirement to be on that
 4) you can patch the cov parts away

This blocks the Python 3.7 rebuild, but since nothing depends on it, it's low priority.

Comment 1 Miro Hrončok 2018-07-17 12:33:17 UTC

Comment 2 Miro Hrončok 2018-07-23 14:10:23 UTC

*** This bug has been marked as a duplicate of bug 1605947 ***

Comment 3 Red Hat Bugzilla 2023-09-12 01:29:34 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days