Bug 1244143 - [epel7] python-retask not built yet
Summary: [epel7] python-retask not built yet
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-retask
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Raiskup
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-17 09:54 UTC by Pavel Raiskup
Modified: 2017-01-20 15:20 UTC (History)
1 user (show)

Fixed In Version: python-retask-0.3-5.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-20 15:20:15 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Pavel Raiskup 2015-07-17 09:54:54 UTC 
Could we please build python-retask for EPEL7?  I tried to build myself in
EPEL7 mock and the build finished successfully (code merged from rawhide
branch).

Pavel
Comment 1 Pavel Raiskup 2015-12-21 00:25:12 UTC 
Ping, Kushal?  I'm able to merge && build (and help with maintenance) in EPEL7
if you are OK with that.
Comment 2 Pavel Raiskup 2015-12-21 10:07:55 UTC 
Scratch build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=12263700
Comment 3 Fedora Update System 2016-01-04 16:23:06 UTC 
python-retask-0.3-5.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-5081e42a76
Comment 4 Fedora Update System 2016-01-05 23:27:27 UTC 
python-retask-0.3-5.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-5081e42a76
Comment 5 Fedora Update System 2017-01-20 15:20:15 UTC 
python-retask-0.3-5.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, 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.