Hi,
It looks like the 'PowerTools' repository is missing the 'virt-devel' module. I can see it in RHEL 8 CodeReady repository but not in PowerTools. See below for examples. Is this intentional or rather something that is missing?
The only package I'm interested in from this 'virt-devel' repository is 'libssh2-devel' which I can see that was build in this link - https://koji.mbox.centos.org/koji/buildinfo?buildID=3832 for x86_64 that I use. As I can rebuild this missing package by myself consider this to be 'low priority' request/question. Thank you.
# yum module list ... Red Hat CodeReady Linux Builder for RHEL 8 x86_64 (RPMs) Name Stream Profiles Summary javapackages-tools 201801 common Tools and macros for Java packaging support virt-devel rhel Virtualization module =========
# yum module list ... CentOS-8 - PowerTools Name Stream Profiles Summary javapackages-tools 201801 common Tools and macros for Java packaging support =========
On 9/29/19 2:54 AM, Ondrej Famera (centos-devel) wrote:
Hi,
It looks like the 'PowerTools' repository is missing the 'virt-devel' module. I can see it in RHEL 8 CodeReady repository but not in PowerTools. See below for examples. Is this intentional or rather something that is missing?
The only package I'm interested in from this 'virt-devel' repository is 'libssh2-devel' which I can see that was build in this link - https://koji.mbox.centos.org/koji/buildinfo?buildID=3832 for x86_64 that I use. As I can rebuild this missing package by myself consider this to be 'low priority' request/question. Thank you.
# yum module list ... Red Hat CodeReady Linux Builder for RHEL 8 x86_64 (RPMs) Name Stream Profiles Summary javapackages-tools 201801 common Tools and macros for Java packaging support virt-devel rhel Virtualization module =========
# yum module list ... CentOS-8 - PowerTools Name Stream Profiles Summary javapackages-tools 201801 common Tools and macros for Java packaging support =========
I know until recently with the advent of version 8000020190828150510 the virt and virt-devel modules were out of sync in RHEL8.0. Perhaps that lead to this? Are we just waiting for updates to CentOS 8.0 to be released?
On 9/30/19 4:00 AM, Orion Poplawski wrote:
On 9/29/19 2:54 AM, Ondrej Famera (centos-devel) wrote:
Hi,
It looks like the 'PowerTools' repository is missing the 'virt-devel' module. I can see it in RHEL 8 CodeReady repository but not in PowerTools. See below for examples. Is this intentional or rather something that is missing?
The only package I'm interested in from this 'virt-devel' repository is 'libssh2-devel' which I can see that was build in this link - https://koji.mbox.centos.org/koji/buildinfo?buildID=3832 for x86_64 that I use. As I can rebuild this missing package by myself consider this to be 'low priority' request/question. Thank you.
# yum module list ... Red Hat CodeReady Linux Builder for RHEL 8 x86_64 (RPMs) Name Stream Profiles Summary javapackages-tools 201801 common Tools and macros for Java packaging support virt-devel rhel Virtualization module =========
# yum module list ... CentOS-8 - PowerTools Name Stream Profiles Summary javapackages-tools 201801 common Tools and macros for Java packaging support =========
I know until recently with the advent of version 8000020190828150510 the virt and virt-devel modules were out of sync in RHEL8.0. Perhaps that lead to this? Are we just waiting for updates to CentOS 8.0 to be released?
Hi Orion, Thanks for the reply. I'm not sure how much out of sync the modules were honestly in case you mention. Last time I was doing some testing I was able to use 'virt-devel' in RHEL 8.0. I remember well because of discussion about "where the libssh2-devel package is" that I started - https://access.redhat.com/discussions/4342891
But I'm not sure if the CentOS 8 should just catch up on some previous updates or if those modules are rather missing. As of now I can only see that package is being build (link posted in originaly), but I don't see it in PowerTools repo anywhere - http://mirror.centos.org/centos/8/PowerTools/x86_64/os/Packages/
Lets see if the updates for CentOS 8.0 would fix this.