Oh, and if this is done by spinning up new images, please enlarge /boot or fix update-boot. I ran out of space in the default 500Mb /boot partition. In fact, I am getting low on the servers where I increased /boot to 1Gb, so enhancing update-boot is probably the better route... On 07/29/2017 06:54 AM, Fabian Arrotin wrote: > Hi guys, > > A trend I see either on twitter, or irc, or elsewhere is a complaint > about Epel not available for CentOS 7 userland on armhfp. > > It's of course technically true (as there is nothing listed on the Epel > wiki page itself) but we covered that FAQ in our wiki : > https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32#head-f2a772703b3caa90cc284e01bc87423ce9a87bcd > > Unfortunately, it seems that people never read that wiki page. > > So I was just wondering if we could have our epel rebuild effort > (https://armv7.dev.centos.org/repodir/epel-pass-1/) available directly > for our armhfp users, without having them to do anything special. > > Now I'm wondering if we should just create a .repo (and coming from > centos-userland-release) but have it disabled by default (imho) or even > enable it by default (-1 on my side) > > Also, we should probably just rename it to something else than 'Epel' as > we can't call that epel : it's a rebuild from Epel SRPMs but it's not Epel > > Opinions, Thoughts ? please make hear your voice ! > > PS : also trying to make some noise on twitter to bring back users not > subscribed to the arm-dev list, or not hanging around in #centos-arm on > irc.freenode.net > > > > _______________________________________________ > Arm-dev mailing list > Arm-dev at centos.org > https://lists.centos.org/mailman/listinfo/arm-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/arm-dev/attachments/20170731/1ab4a3f2/attachment-0006.html>