Bug 1735636 - Add -devel package to CodeReadyBuilder repo
Summary: Add -devel package to CodeReadyBuilder repo
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libuv
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Node.js maintainers
QA Contact: RHEL CS Apps Subsystem QE
URL:
Whiteboard:
Depends On:
Blocks: 1759510
TreeView+ depends on / blocked
 
Reported: 2019-08-01 07:50 UTC by Phil Wyett
Modified: 2020-05-11 13:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-17 11:44:58 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Phil Wyett 2019-08-01 07:50:08 UTC 
Description of problem:

Add libuv devel package to CodeReadyBuilder repo. This package is required in the stack of packages to build the very popular filezilla for EPEL.
Comment 11 Mark Stopka 2019-11-30 13:29:47 UTC 
Hi, where is the holdup? It's clearly poorly packaged libuv if you ship it without the development files, software can't be build against the OS.
Comment 12 Vít Ondruch 2019-12-02 09:33:06 UTC 
(In reply to Mark Stopka from comment #11)

Dear Mark, please take a look at bug 1759510#c9 where is a proposal to fix this issue.
Comment 13 Josh Boyer 2020-03-17 11:44:58 UTC 
Thank you for the request.  This has been resolved by the EPEL community.  At the moment, we will not be including the libuv-devel package in the CodeReady Builder repository.
Comment 14 Stephen Gallagher 2020-03-17 12:45:56 UTC 
(In reply to Josh Boyer from comment #13)
> Thank you for the request.  This has been resolved by the EPEL community. 
> At the moment, we will not be including the libuv-devel package in the
> CodeReady Builder repository.

This is not actually yet resolved in EPEL. The libuv-devel module shouldn't have gone stable yet, as it's blocked from actually working by https://bugzilla.redhat.com/show_bug.cgi?id=1809314
Note You need to log in before you can comment on or make changes to this bug.