On Mon, Feb 3, 2020 at 2:36 PM Stephen John Smoogen <smooge@xxxxxxxxx> wrote: > > > My main job is working with Fedora Infrastructure, and we are trying to work out how to handle: > > https://pagure.io/fedora-infrastructure/issue/8558 > > The problem is that various tools filter what packages can be branched into Fedora see that libssh2 was in a module that RHEL shipped in 8.0 but it is no longer in the release with 8.1. > > Do we need to make libssh2 a module? > Should we allow libssh2 be branched as a 'bare' package in EPEL proper? > Other? > Since libssh2 is being dropped from RHEL, I think we should just permit it as a regular package in EPEL proper. That maximizes its usefulness to everyone. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
