#9848 libuv appears to be missing from epel8-playground buildroot
Closed: Fixed 3 years ago by pingou. Opened 3 years ago by carlwgeorge.

  • Describe the issue

EPEL playground packages that build require libuv-devel (from CentOS Devel repo) are failing because it can't be installed. At first glance it appears to be because libuv (from RHEL appstream (non-modular)) is missing.

DEBUG util.py:634:  Error: 
DEBUG util.py:634:   Problem: conflicting requests
DEBUG util.py:634:    - nothing provides libuv.so.1 needed by libuv-devel-1:1.23.1-1.el8.i686
DEBUG util.py:634:    - nothing provides libuv(x86-32) = 1:1.23.1-1.el8 needed by libuv-devel-1:1.23.1-1.el8.i686
DEBUG util.py:634:    - nothing provides libuv(x86-64) = 1:1.23.1-1.el8 needed by libuv-devel-1:1.23.1-1.el8.x86_64
DEBUG util.py:636:  (try to add '--skip-broken' to skip uninstallable packages)

This was first reported in rhbz#1895872. Some scratch builds are linked in the bugzilla if the full log is desired.

  • When do you need this? (YYYY/MM/DD)

Non-emergency ASAP.

  • When is this no longer needed or useful? (YYYY/MM/DD)

2029/05/31 (RHEL 8 EOL)

  • If we cannot complete your request, what is the impact?

EPEL playground packages that build require libuv-devel are not able to build. This is also blocking new packages that build require libuv-devel from being added to EPEL playground.


Metadata Update from @mohanboddu:
- Issue tagged with: medium-gain, medium-trouble, ops

3 years ago

Problem is that RHEL8.3 has libuv-1.38.0-2.el8.x86_64.rpm which supersedes libuv-devel-1.23.1-1.el8.x86_64.rpm so they can not both be installed. A fix will need to wait until CentOS-8 builds a newer version of the package and ships it.

Ahh, good catch. What threw me off was that a RHEL 8 system with the CentOS devel repo can install libuv-devel by resolving the older libuv package.

[root@el8-container:~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.3 (Ootpa)
[root@el8-container:~]# dnf repolist
repo id            repo name
appstream          Red Hat Enterprise Linux 8 (RPMs) - AppStream
baseos             Red Hat Enterprise Linux 8 (RPMs) - BaseOS
centos-devel       CentOS Linux 8 - Devel
codeready-builder  Red Hat Enterprise Linux 8 (RPMs) - CodeReady Linux Builder
[root@el8-container:~]# dnf list available --showduplicates libuv
Last metadata expiration check: 0:02:58 ago on Tue Nov 10 19:38:44 2020.
Available Packages
libuv.i686                        1:1.23.1-1.el8                      appstream
libuv.x86_64                      1:1.23.1-1.el8                      appstream
libuv.i686                        1:1.38.0-2.el8                      appstream
libuv.x86_64                      1:1.38.0-2.el8                      appstream
[root@el8-container:~]# dnf install libuv-devel
Last metadata expiration check: 0:03:05 ago on Tue Nov 10 19:38:44 2020.
Dependencies resolved.
===============================================================================
 Package           Architecture Version               Repository          Size
===============================================================================
Installing:
 libuv-devel       x86_64       1:1.23.1-1.el8        centos-devel        34 k
Installing dependencies:
 libuv             x86_64       1:1.23.1-1.el8        appstream          134 k

Transaction Summary
===============================================================================
Install  2 Packages

Total download size: 169 k
Installed size: 438 k
Is this ok [y/N]: 

I take it this means that the EPEL 8 buildroot sync only gets the latest version of each package?

I confirmed that the EPEL 8 buildroot only sees the latest version of each package. There is nothing releng can fix here, it just has to wait for the CentOS Linux 8.3 rebuild to complete, and then the devel repo can be synced up.

Metadata Update from @carlwgeorge:
- Issue close_status updated to: Can't Fix
- Issue status updated to: Closed (was: Open)

3 years ago

Issue status updated to: Open (was: Closed)

3 years ago

Issue status updated to: Closed (was: Open)
Issue close_status updated to: Fixed

3 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Done