On Thu, May 30, 2019 at 4:25 PM James Cassell
<fedoraproject(a)cyberpear.com> wrote:
> >
> > Historical composes are intended to be frozen and unchanging, but this
> > approach leaves open the possibility of tagging other builds into
> > epel8-8.Y and regenerating the compose if the need arises. It will
> > need to be communicated that these repositories will not receive
> > updates and are intended to be only a snapshot of the past that is
> > known to work with a particular RHEL 8.Y base.
>
This will be very helpful, especially if the epel-release .repo file honors the
$releasever variable.
Can you explain what behavior you see here? I can't really parse from
your reply what you think/expect to have happen here, and I'd like to
make sure we address it properly.