On Tue, Apr 29, 2014 at 05:30:14AM +0100, Justin Clift wrote: > Hi Kaleb, > > Investigating a failure in rpm.t on Rackspace, in release-3.5 > branch (but not master). > > Noticed something interesting while looking. (May not be related > to the problem). In rpm.t there's this: > > # build for the last two Fedora EPEL releases (x86_64 only) > for MOCK_CONF in $(ls -x1 /etc/mock/*.cfg | egrep -e 'epel-[0-9]+-x86_64.cfg$' | tail -n2) > > Is that trying to target EPEL 5 & 6? It is trying to target "the last two Fedora EPEL releases" :) > It seems to be getting EPEL 6 & 7: > > $ ls -x1 /etc/mock/*.cfg | egrep -e 'epel-[0-9]+-x86_64.cfg$' | tail -n2 > /etc/mock/epel-6-x86_64.cfg > /etc/mock/epel-7-x86_64.cfg > > Weird failure that I'm seeing aside, should this be updated to > target EPEL 5-7 instead of "last two" EPEL releases? Currently, we should probably target the last 3 EPEL-releases. There is a patch in master that makes building on EPEL-7 work, this is not part of release-3.5 yet (http://review.gluster.org/7564). And I did not spot a fix for building release-3.4 on EPEL-7. Until those fixes are in, just 'mv /etc/mock/epel-7-x86_64.cfg{,_}' on the Rackspace builders? Niels