On Mon, 26 Nov 2018 at 11:00, Christopher <ctubbsii(a)fedoraproject.org> wrote:
On Mon, Nov 26, 2018 at 7:12 AM Stephen John Smoogen <smooge(a)gmail.com> wrote:
>
> On Mon, 26 Nov 2018 at 01:03, Christopher <ctubbsii(a)fedoraproject.org> wrote:
> >
> > Anybody know what's going on with Centos 7.6-1810?
> > Some packages in EPEL depend on it, but it is apparently not yet available.
> > This discrepancy is breaking yum updates for me.
> >
>
> This isn't a Fedora development issue. Please refer this to the CentOS
> or EPEL lists.
>
EPEL is a Fedora project. My question wasn't really about CentOS, but
rather, about maintainer best practices for EPEL branches. To clarify,
my question is whether package maintainers are expected to ensure
their EPEL branch for their packages works against the latest CentOS
release (without enabling 'cr' repo) or whether it is expected that
packages will work as soon as the corresponding RHEL release is
available (which is usually available about 3-4 weeks earlier). What
do we use for the EPEL buildroot in koji?
Even though EPEL is a Fedora project, the main development and work is
done on the epel-devel(a)lists.fedoraproject.org mailing list.
EPEL is built from the 'current' state of Red Hat Enterprise Linux as
synced from 'rhn (or whatever they call it these days)' every 12
hours. This means that CentOS users must use CR during the
intermediate time.
> > For example, xorgxrdp-0.2.8-3.el7 depends on
xorg-x11-server-Xorg
> > 1.20.1, which isn't yet available (rather, available on in the cr
> > repo, not in CentOS updates yet).
>
> --
> Stephen J Smoogen.
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
--
Stephen J Smoogen.