On 06/06/18 03:01, Steven Ellis wrote: > Is there a formal process for testing / validating the ARM builds for EPEL? > > I'm currently using the following repository > > # more /etc/yum.repos.d/epel-arm.repo > [epel-arm] > baseurl = https://armv7.dev.centos.org/repodir/epel-pass-1/ > enabled = 1 > gpgcheck = 0 > name = CentOS EPEL for ARM > > For example > - are their EPEL packages that aren't currently in the ARM release that > need validation > - is there a process to tag a release as "end user" tested? > > Steven > Hi Steven, Currently there is no real process, as packages landing in EPEL are then (once a week) put in the build queue for armhfp, and it's so a "blind and automatic" process. I don't think we'll ever have a "release" repository (at this point) so if you don't see an EPEL pkg there that you need, it's probably better to ask on this list, and investigate why it didn't build (through the available build logs on https://armv7.dev.centos.org/rpmbuild/epel-pass-1/) and ask on the list to try a rebuild and help debugging why it didn't build. Cheers, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/arm-dev/attachments/20180606/582a5854/attachment-0006.sig>