Bug 1274846 - [RFE] EPEL7 branch of zopfli
Summary: [RFE] EPEL7 branch of zopfli
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: zopfli
Version: epel7
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Christopher Meng
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-23 16:08 UTC by Pat Riehecky
Modified: 2016-02-28 20:24 UTC (History)
2 users (show)

Fixed In Version: zopfli-1.0.1-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-28 20:24:42 UTC
Type: Bug


Attachments (Terms of Use)

Description Pat Riehecky 2015-10-23 16:08:00 UTC
Description of problem:
Can zopfli be branched for EPEL7?

I'd like to utilize zopfli on an EL7 box and an EPEL branch would simplify the deployment.

Version-Release number of selected component (if applicable): Based on whatever currently is in Fedora.


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ville Skyttä 2016-02-03 21:51:07 UTC
Branch requested: https://admin.fedoraproject.org/pkgdb/package/requests/3643

Comment 2 Fedora Update System 2016-02-11 15:27:06 UTC
zopfli-1.0.1-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-c259875b2e

Comment 3 Fedora Update System 2016-02-12 17:21:06 UTC
zopfli-1.0.1-1.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-c259875b2e

Comment 4 Fedora Update System 2016-02-28 20:24:39 UTC
zopfli-1.0.1-1.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.