Bug 1402199 - netty build for EPEL7
Summary: netty build for EPEL7
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: netty
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christopher Tubbs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-07 02:57 UTC by Ian Wienand
Modified: 2024-07-08 22:25 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-08 22:25:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ian Wienand 2016-12-07 02:57:09 UTC
Hi,

We would like to get zookeeper packages for EPEL7, and netty is one hard requirement for getting that to work.

---
DEBUG util.py:421:  Error: No Package found for mvn(io.netty:netty-tcnative)
DEBUG util.py:421:  Error: No Package found for mvn(log4j:log4j:12)
DEBUG util.py:421:  Error: No Package found for mvn(org.jboss.logging:jboss-logging)
DEBUG util.py:421:  Error: No Package found for mvn(org.jboss.marshalling:jboss-marshalling)
---

A COPR build [1] suggests maybe it's not too far off.  I'm filing this bug for tracking and coordination of interested parties.


[1] https://copr-be.cloud.fedoraproject.org/results/iwienand/centos7-zookeeper/epel-7-x86_64/00485587-netty3/root.log.gz

Comment 1 Severin Gehwolf 2016-12-07 15:54:50 UTC
I'm not interested in maintaining netty for epel 7. Feel free to do that yourself, though.

Comment 2 Fedora Admin XMLRPC Client 2017-03-14 10:30:41 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora Admin XMLRPC Client 2017-03-14 17:55:19 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Troy Dawson 2024-07-08 22:25:14 UTC
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.


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