Bug 1213981 - Please branch and build for epel7
Summary: Please branch and build for epel7
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-waitress
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lorenzo Gil Sanchez
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-21 17:04 UTC by Ralph Bean
Modified: 2015-05-20 04:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-14 21:10:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ralph Bean 2015-04-21 17:04:37 UTC
Fedora Infrastructure needs python-waitress for the bodhi2 server on epel7.

I've applied for rights in pkgdb if there's anyway I can help.

Comment 1 Lorenzo Gil Sanchez 2015-04-21 17:48:31 UTC
I just approved them.

I never made a package for epel and I would be interested in learning about the details for branching and building for it.

If you can put a log of what you do in this bug that would be helpful.

Comment 2 Ralph Bean 2015-04-27 14:06:02 UTC
Thanks!  The first thing to do is click the 'request new branch' button in pkgdb:  https://admin.fedoraproject.org/pkgdb/package/python-waitress/

Comment 3 Ralph Bean 2015-04-27 16:06:08 UTC
Next, I had to patch the spec file to conditionalize the python3 subpackage (since python3 is not straightforward on epel7):  http://pkgs.fedoraproject.org/cgit/python-waitress.git/commit/?id=7d555e5d12aa4135104cf0c96b1e1c7115a8ed96

Comment 4 Fedora Update System 2015-04-27 16:17:19 UTC
python-waitress-0.8.9-5.el7 has been submitted as an update for Fedora EPEL 7.
https://admin.fedoraproject.org/updates/python-waitress-0.8.9-5.el7

Comment 5 Fedora Update System 2015-05-20 04:54:24 UTC
python-waitress-0.8.9-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.