On Wed, Jul 24, 2019 at 8:50 PM Matthew Miller <mattdm at mattdm.org> wrote: > On Thu, Jul 11, 2019 at 11:16:11AM +0200, Alfredo Moralejo Alonso wrote: > > > However it would mean also building against a moving target which can > be > > > difficult if EPEL policies are the same as today. > > > As EPEL 8 is also in the making it would be good to hear what SIGs > think > > > about this specific issue. > > In CloudSIG we currently are explicit about not supporting enabling EPEL > > repos to deploy OpenStack. We are rebuilding the required deps in the SIG > > repo when needed. The main reasons for this is that we want to stay with > > specific versions of dependencies for stable releases and not following > > latest builds in EPEL on every supported release. > > I'd really like to see modularity used to address this problem. This is one > of the things that it's _for_. > > > > Also, rebuilding them in > > CBS allows us to test any update before pushing it to the actual repos. > > Sorry, I'm not familiar with the process here. How does rebuilding help > with > testing? Doesn't it mean you have something _less_ tested? > > > What helps is not rebuilding packages (I'm fine with using EPEL packages if they are available) but publishing packages in SIG's managed repos instead of just enabling EPEL repos. I can test those builds (whether rebuilt or just cross-tagged) before tagging and pushing them to the actual repos. > -- > Matthew Miller > <mattdm at fedoraproject.org> > Fedora Project Leader > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20190725/2492ddb0/attachment-0008.html>