Bug 1790124 - Please build python-pytest-rerunfailures for EPEL8
Summary: Please build python-pytest-rerunfailures for EPEL8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-pytest-rerunfailures
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Scott K Logan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-12 00:30 UTC by Orion Poplawski
Modified: 2020-05-26 00:53 UTC (History)
1 user (show)

Fixed In Version: python-pytest-rerunfailures-4.2-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 00:53:20 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Pagure releng/fedora-scm-requests issue 24887 0 None None None 2020-05-09 20:39:23 UTC

Description Orion Poplawski 2020-01-12 00:30:35 UTC 
Description of problem:

Please build python-pytest-rerunfailures for EPEL8.  Needed for latest matplotlib.
Comment 1 Ben Cotton 2020-02-11 17:36:23 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.
Comment 2 Fedora Update System 2020-05-10 06:25:09 UTC 
FEDORA-EPEL-2020-16949a1a9b has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-16949a1a9b
Comment 3 Fedora Update System 2020-05-11 00:25:05 UTC 
FEDORA-EPEL-2020-16949a1a9b has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-16949a1a9b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2020-05-26 00:53:20 UTC 
FEDORA-EPEL-2020-16949a1a9b has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.