On Tue, 13 Dec 2022 at 10:47, Leon Fauster via epel-devel <
epel-devel(a)lists.fedoraproject.org> wrote:
I noticed that on a RHEL8 workstation the deprecated and removed
package
from EL8.0 - libssh2, does not get substituted by the package from epel:
libssh2-1.8.0-8.module+el8.0.0+4084+cceb9f44.1.x86_64
vs
libssh2-1.9.0-5.el8.x86_64
only possible with
yum update libssh2 --disablerepo=rhel-8-for-x86_64-appst*
is this intentional?
yum distrosync
tries to install the obsolete version 1.8.0 again.
How to solve this conflict? Its seems not to be a "module" problem
otherwise it would not install the epel version at all, right?
The package was in 2 module releases
virt-devel:rhel:8000020190828150510:f8e95b4e:x86_64
virt-devel:rhel:820190226174025:9edba152:x86_64
and then removed from all later modules:
virt-devel:rhel:8010020190916153839:cdc1202b:x86_64
so by October of 2019, it was no longer in the OS. So I would assume a
distrosync would remove it for that reason. The libssh2-1.9.0 was added to
EPEL because of the removal of 1.8.0 in RHEL and 1.9.0 being supportable.
--
Leon
_______________________________________________
epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproj...
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren