View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0016492||CentOS-8||libssh2||public||2019-09-30 09:21||2019-10-21 14:19|
|Target Version||Fixed in Version|
|Summary||0016492: No libssh2-devel package|
|Description||There seems to be no libssh2-devel package in CentOS 8 repos. I found this from upstream:|
but that didn't help, 'dnf module enable virt-devel' gives 'missing groups or modules: virt-devel' error.
|Steps To Reproduce||dnf list libssh2-devel|
|Tags||No tags attached.|
Any news on this? It seems like this package should be in PowerTools?
It seems to have been built with the libssh2 package on koji https://koji.mbox.centos.org/koji/buildinfo?buildID=4650
Not only is libssh2-devel missing, but there is also no qemu-system-x86, which I tried to build. qemu-3.0.1 still has a libssh2-devel depends, but qemu-4.1.0 does not. Upstream qemu.git took it out, I believe the responsible developer is from Redhat.
I'm currently packaging upstream xen-4.12.1 and xen-4.13~rc1 for CentOS 8. This is where I ran into this bug report.
|This is blocking my Copr build of zabbix as well.|
|So. . .how will that impact the availability of libssh2-devel?|
|It should be pretty clear: Starting with RHEL 8.1 it won't be shipped by Red Hat. I guess the reason it's missing now is a screw-up related to this.|
|Thanks. it wasn't clear. So do you think they'll fix it for 8.0, or do we have to wait until 8.1 and add it to EPEL? And people who need it just don't use EL-8 for an entire point release?|
|I found the build for libssh2 so I know there is a devel package that could be published? is there any reason to not publish this to powertools for the point release as it is published in RHEL? otherwise is there any reason not to go ask for the epel package at this time?|
|I don't know, guess you'll have to ask Red Hat's RCM team.|
|2019-09-30 09:21||eesau||New Issue|
|2019-10-12 02:47||AlphaCluster||Note Added: 0035448|
|2019-10-19 21:44||PryMar56||Note Added: 0035529|
|2019-10-20 15:19||toracat||Relationship added||has duplicate 0016625|
|2019-10-20 15:20||toracat||Relationship added||related to 0016626|
|2019-10-20 15:24||limburgher||Note Added: 0035531|
|2019-10-21 13:45||Richard Jones||Note Added: 0035539|
|2019-10-21 13:50||limburgher||Note Added: 0035540|
|2019-10-21 13:56||Richard Jones||Note Added: 0035541|
|2019-10-21 13:58||limburgher||Note Added: 0035542|
|2019-10-21 14:03||AlphaCluster||Note Added: 0035543|
|2019-10-21 14:19||Richard Jones||Note Added: 0035544|