[CentOS-devel] Community build services and EPEL8

On Thu, Jul 25, 2019 at 3:15 PM Fabian Arrotin <arrfab at centos.org> wrote:

> On 25/07/2019 15:05, Matthew Miller wrote:
> > On Thu, Jul 25, 2019 at 02:17:39PM +0200, Alfredo Moralejo Alonso wrote:
> >>> 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.
> >
> > Ah, that makes sense. I'm definitely in favor of figuring out how to do
> the
> > cross-tagging here.
> >
>
> That was basically what I proposed in that thread earlier :
> <paste>
> Just wondering : if people would like to consume epel pkgs, but still
> want to cherry-pick which version of pkgs they need/want : what about :
> - creating tag/targets for epel (but not building *any* pkg there)
> - rsync (without any delete) epel
> - use "koji import" to import all epel pkgs, and also new versions when
> new pkgs appear
>
> That would mean : nothing to build on cbs, and people can just "cbs
> tag-build" existing imported pkgs.
>
> Would that work for everybody ?
> </paste>
>
>
Yeap, that'd  work for me. The only potential issue i see is conflicting
NVRs between CBS rebuilt packages vs imported from epel. i.e. if some SIG
has rebuilt a package with same NVR from epel with some fix for any reason,
i understand that'd fail to import, right?


> We just import all EPEL pkgs, keep all versions and people can tag the
> ones they need/want/have tested :-)
>
>
I'd expect also thhis would favor contributing fixes to EPEL that we'd just
cross-tag in SIGs instead of forking.


>
> --
> Fabian Arrotin
> The CentOS Project | https://www.centos.org
> gpg key: 17F3B7A1 | twitter: @arrfab
>
> _______________________________________________
> 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/062f22f1/attachment-0004.html>