[CentOS-devel] [EPEL-devel] Re: Handling packages retired in epel but not yet available in CentOS?

On Thu, May 14, 2020 at 7:44 PM Carl George <carl at redhat.com> wrote:
>
> This should normally be an edge case that only occurs during the time
> between a RHEL point release and the corresponding CentOS Linux
> rebuild.  Historically that usually takes about a month.  As more and

A few have been that fast. Some have taken up to six months: I'm
thinking of CentOS 7.2.

> Regarding using CentOS Stream for your use case, be aware that EPEL is
> built against RHEL, so it's possible to run into issues where an EPEL
> package doesn't work on CentOS Stream.  This is a known issue that we
> haven't come to a conclusion yet on how to handle.  On a related note,
> EPEL faces similar challenges when RHEL bumps a library soname.  The

It's one reason I spend some time with "mock", myself, to be able to
backport dependency chains and resolve such discrepancies at least
with an internal repository.