RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
The version of libuv in appstream is 1.23.1:
https://mirrors.edge.kernel.org/centos/8-stream/AppStream/x86_64/os/Packages/libuv-1.23.1-1.el8.x86_64.rpm

It's too old for building Neovim >= 0.4.0 which requires libuv >= 1.28.0:
https://github.com/neovim/neovim/blob/v0.4.0/CMakeLists.txt#L369

Version-Release number of selected component (if applicable):
1.23.1-1.el8

How reproducible:
Always

Steps to Reproduce:
1. Check neovim's CMakeLists.txt

I look into building a "compat" newer version of libuv for EPEL, but upstream does not bump their soname -- both libuv 1.34.2 (Fedora 32) and libuv 1.23.1 (RHEL 8 AppStream) ships libuv.so.1.0.0.

Upstream promises backward compatibility within a major version:
https://github.com/libuv/libuv#versioning

and the ABI Laboratory seems to confirm there is no regression between 1.23.1 and 1.34.2:
https://abi-laboratory.pro/?view=timeline&l=libuv

Could we have this updated? Thanks!

I'll look into it.

(In reply to Zuzana Svetlikova from comment #4)
> I'll look into it.

awesome, thanks!

VERIFIED


version
libuv-1.38.0-1.el8


Version was upgraded to 1.38.0  (rpmbuild/BUILD/libuv-v1.38.0)

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (libuv bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:4692