libuv is part of RHEL 8 already. Is something missing?

Wired...Koji is complaining that libuv-devel is missing.


[...]
DEBUG util.py:595:  Package gcc-8.2.1-3.5.el8.x86_64 is already installed.
DEBUG util.py:593:  No matching package to install: 'libuv-devel'
DEBUG util.py:593:  Not all dependencies satisfied
DEBUG util.py:593:  Error: Some packages could not be found.
[...]

Ahh, libuv-devel may not be available. I need to check with people about how we're handling that in EPEL 8...

Thanks

*** Bug 1767123 has been marked as a duplicate of this bug. ***

You can find the libuv-devel rpm package with the correct version following this link provided by redhat.com officially:

http://downloads.redhat.com/redhat/rhel/rhel-8-beta/appstream/x86_64/Packages/libuv-1.23.1-1.el8.x86_64.rpm

(In reply to Xia Hao from comment #6)
> You can find the libuv-devel rpm package with the correct version following
> this link provided by redhat.com officially:
> 
> http://downloads.redhat.com/redhat/rhel/rhel-8-beta/appstream/x86_64/
> Packages/libuv-1.23.1-1.el8.x86_64.rpm

sorry, the link should be  http://downloads.redhat.com/redhat/rhel/rhel-8-beta/appstream/x86_64/Packages/libuv-devel-1.23.1-1.el8.x86_64.rpm

(In reply to Xia Hao from comment #6)
> You can find the libuv-devel rpm package with the correct version following
> this link provided by redhat.com officially:
> 
> http://downloads.redhat.com/redhat/rhel/rhel-8-beta/appstream/x86_64/
> Packages/libuv-1.23.1-1.el8.x86_64.rpm

Doesn't really help as libuv-devel has to be available in EPEL to build packages.

We are close to being able to enable modules in EPEL 8 (it's working in the staging environment and I expect we will get it working in the production environment before the end of the month).

My current plan is to create a libuv module stream that builds from the RHEL SRPM and produces the libuv-devel subpackages (but not the libuv main package; we want that to always remain coming from the official versions). We will then tag the libuv-devel subpackage from this build into the buildroot for EPEL 8. Any builds done in Koji will have it available.

For building locally, the developer will need to run `yum module install libuv:epel8-buildroot` (or whatever we ultimately name it) and they will get the libuv-devel package.

We're using libuv as the proof-of-concept for this approach to dealing with missing subpackages.

Any progress to make the devel package available?

(In reply to Fabian Affolter from comment #10)
> Any progress to make the devel package available?

I didn't get a chance to work on this before the end of the year. It's on my TODO list for January.

Hi there.

Is there any change to make the devel package available any time soon?
I would like to have an answer for users who ask us about missing EPEL 8 packages.

Thanks!

FEDORA-EPEL-MODULAR-2020-93b8ffa981 has been submitted as an update to Fedora Epel 8 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-MODULAR-2020-93b8ffa981

libuv-epel8_buildroot-820200224200346.9edba152 has been pushed to the Fedora Epel 8 Modular 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-MODULAR-2020-93b8ffa981

Thank you! We will give it a try once we find out who are buildroot modules supposed to be used ...

libuv-epel8_buildroot-820200228154227.9edba152 has been pushed to the Fedora Epel 8 Modular 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-MODULAR-2020-93b8ffa981

This is currently blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1809314

libuv-epel8_buildroot-820200228154227.9edba152 has been pushed to the Fedora Epel 8 Modular stable repository. If problems still persist, please make note of it in this bug report.

I just wonder, what is the relation to:

https://lists.centos.org/pipermail/centos-devel/2020-March/036644.html

Is the package in build root still unavailable due to bug 1809314, or is there something that has to be added to spec file to use the modular buildroot?

When using: "BuildRequires:  pkgconfig(libuv)" in the spec, I still get "No matching package to install: 'pkgconfig(libuv)'" during build - https://kojipkgs.fedoraproject.org//work/tasks/7935/42557935/root.log

(In reply to Tomas Krizek from comment #20)
> Is the package in build root still unavailable due to bug 1809314, or is
> there something that has to be added to spec file to use the modular
> buildroot?
> 
> When using: "BuildRequires:  pkgconfig(libuv)" in the spec, I still get "No
> matching package to install: 'pkgconfig(libuv)'" during build -
> https://kojipkgs.fedoraproject.org//work/tasks/7935/42557935/root.log

This wasn't actually supposed to go to stable until #1809314 is fixed. I thought I'd unchecked that box in Bodhi, but I guess not. In any case, no it won't work yet. Reopening this to keep it tracked.

I also need ordinary libuv-devel to build package in rpmfusion.

Stephen, any ETA on this? Thanks!

(In reply to Michel Alexandre Salim from comment #23)
> Stephen, any ETA on this? Thanks!

I've done all the work on my end for this, but it won't actually *work* until #1809314 is resolved. Until then, this is blocked.

FEDORA-EPEL-MODULAR-2020-2c76e38f8c has been submitted as an update to Fedora Epel 8 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-MODULAR-2020-2c76e38f8c

Non modular libuv-devel for epel8 will be available?

(In reply to Vasiliy Glazov from comment #26)
> Non modular libuv-devel for epel8 will be available?

I noticed a bug in my dependency specification. I don't think it will help until #1809314 is fixed.

Also, libuv-devel will be visible to the non-modular buildroot.

In rpmfusion it will be visible too.

(In reply to Vít Ondruch from comment #19)
> I just wonder, what is the relation to:
> 
> https://lists.centos.org/pipermail/centos-devel/2020-March/036644.html

+1 to this. Would it be possible to enable the Devel repo temporarily in our EPEL builders?

The CentOS Devel repository has been enabled in the EPEL buildroots since 2020-04-01.

https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/O4JISZYIVXXPIB6OZIE2TNKR2EIQZWBL/

https://fedoraproject.org/wiki/EPEL/FAQ#RHEL_8.2B_has_binaries_in_the_release.2C_but_is_missing_some_corresponding_-devel_package._How_do_I_build_a_package_that_needs_that_missing_-devel_package.3F

It contains a non-modular libuv-devel package.

Name         : libuv-devel
Epoch        : 1
Version      : 1.23.1
Release      : 1.el8
Architecture : x86_64
Size         : 34 k
Source       : libuv-1.23.1-1.el8.src.rpm
Repository   : Devel
Summary      : Development libraries for libuv
URL          : http://libuv.org/
License      : MIT and BSD and ISC
Description  : Development libraries for libuv

EPEL packages that were waiting on this to build should be able to proceed.

FEDORA-EPEL-MODULAR-2020-2c76e38f8c has been pushed to the Fedora Epel 8 Modular testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-MODULAR-2020-2c76e38f8c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-EPEL-MODULAR-2020-2c76e38f8c has been pushed to the Fedora Epel 8 Modular stable repository.
If problem still persists, please make note of it in this bug report.

Looks like I'm running into libuv-devel deployment problems when trying to do a `dnf builddep cmake` in CentOS 8.2 with EPEL8 enabled:
```
# dnf builddep cmake
...
Error:
 Problem: conflicting requests
  - package libuv-devel-1:1.23.1-2.module_el8+8698+518af944.x86_64 is filtered out by modular filtering
  - package libuv-devel-1:1.36.0-3.module_el8+8692+52300fb6.x86_64 is filtered out by modular filtering
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
# dnf repolist
repo id                                repo name
AppStream                              CentOS-8 - AppStream
BaseOS                                 CentOS-8 - Base
PowerTools                             CentOS-8 - PowerTools
epel                                   Extra Packages for Enterprise Linux 8 - x86_64
epel-modular                           Extra Packages for Enterprise Linux Modular 8 - x86_64
extras                                 CentOS-8 - Extras
# dnf info libuv-devel
Last metadata expiration check: 0:10:03 ago on Tue 14 Jul 2020 12:10:03 PM EDT.
Error: No matching Packages to list
```

libuv-devel is planned to be added to the CRB repository in RHEL 8.4, and is already available in CentOS Stream 8's PowerTools repository.  We've also added it to the Devel repository in CentOS Linux 8 so that it is available for EPEL8 builds now.

CL8:
# dnf config-manager --enable devel
# repoquery -q --nvr libuv-devel
libuv-devel-1.38.0-2.el8

CS8:
# dnf config-manager --enable powertools
# repoquery -q --nvr libuv-devel
libuv-devel-1.40.0-1.el8

libuv-devel packages from CentOs are in EPEL8 koji build system. 
There is issue that packages for the EPEL8 s390x architecture are not available.

Michal, EPEL8 builds against RHEL8 + CentOS 8 Devel repo.  When the CentOS 8 Devel repo was added to the buildroot, it was a known limitation that CentOS doesn't build for s390x.  EPEL 8 packages that have build requirements from CentOS 8 Devel must excludearch s390x.

This all goes away once RHEL 8.4 is released, which includes libuv-devel built for s390x.