Description of problem:
libudisks2 is an available package, however development headers for the library are not available in codeready-builder-for-rhel-8-x86_64-rpms.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. subscription-manager repo --enable codeready-builder-for-rhel-8-x86_64-rpms
2. dnf install libudisks2-devel
Updating Subscription Management repositories.
Extra Packages for Enterprise Linux Modular 8 - 121 kB/s | 17 kB 00:00
Extra Packages for Enterprise Linux 8 - x86_64 6.8 kB/s | 19 kB 00:02
Red Hat Enterprise Linux 8 for x86_64 - AppStre 17 kB/s | 4.5 kB 00:00
Red Hat CodeReady Linux Builder for RHEL 8 x86_ 18 kB/s | 4.5 kB 00:00
Red Hat Enterprise Linux 8 for x86_64 - Supplem 15 kB/s | 3.8 kB 00:00
Red Hat Enterprise Linux 8 for x86_64 - BaseOS 16 kB/s | 4.1 kB 00:00
No match for argument: libudisks2-devel
libudisks2-devel is installed
While I cannot speak for Red Hat Product Management, I can only say this is on purpose. We don't ship all -devel packages by default. Please contact your support representative for clarification.
Would you mind sharing your specific use case please? As a side question and out of curiosity from the upstream udisks maintainer point of view, we'd be interested to learn more about projects that build on top of UDisks and the way it is used.
Sure, I work on a product which uses udisks2 for its block device enumeration. The library it provides is helpful as much as the module system will be for future development.
# yum list | grep libudisks2-devel
Failed to set locale, defaulting to C.UTF-8
libudisks2-devel.x86_64 2.9.0-1.el8 @beaker-CRB
libudisks2-devel.i686 2.9.0-1.el8 beaker-CRB
the package have been added to repo, so move to verified
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 (udisks2 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.