Bug 1295484 - Please package for EPEL
Summary: Please package for EPEL
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: python-tornado
Version: 24
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Python SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-04 16:22 UTC by Stuart Campbell
Modified: 2016-05-16 21:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-16 21:03:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1309909 0 medium CLOSED Review Request: python3-tornado - Scalable, non-blocking web server and tools 2021-02-22 00:41:40 UTC

Internal Links: 1309909

Description Stuart Campbell 2016-01-04 16:22:15 UTC
Description of problem:

Please rebuild for EPEL.  

The current F23 SRPM rebuilds cleanly on EL7. see https://copr.fedoraproject.org/coprs/sic/backports-el7/build/151349/

Comment 1 Orion Poplawski 2016-01-04 16:39:11 UTC
python-tornado (python2) is in RHEL7, so no go there.  I'm looking to package up python3-tornado for EPEL7 hopefully soon.

Comment 2 Stuart Campbell 2016-01-04 17:01:55 UTC
Thanks for the quick response.  Is it worth me trying to raise an issue with Red Hat to upgrade their version of tornado ?  I suspect I know the answer! :)  

Cheers
Stu

Comment 3 Orion Poplawski 2016-01-04 17:06:19 UTC
Already filed (bug #1158617) with no response yet :(.

Comment 4 Stuart Campbell 2016-01-04 17:16:47 UTC
I've just submitted a support request as well! :)

Comment 5 Jan Kurik 2016-02-24 14:13:37 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase


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