<html><body>
<p><tt><font size="2">Dan Horák <dan@danny.cz> wrote on 2015-06-24 08:53:24 AM:<br>
<br>
> yeah, I mean zPDT and Hercules. I haven't tried F-22 on Hercules yet,<br>
> but F-21 worked fine there. And I suppose zPDT won't have issues as<br>
> well. For the Fedora builds we use native builders on a LPAR from the<br>
> Red Hat zEC12.</font></tt><br>
<br>
<tt><font size="2">Good to hear. These are certainly possibilities if there isn't enough</font></tt><br>
<tt><font size="2">native capacity.</font></tt><br>
<tt><font size="2"><br>
> One of the first steps towards EPEL should taking the current source<br>
> RPMs and start building them using mock (which is one level below the<br>
> koji build system for proper EPEL) and publish the results. This step<br>
> is important even when there won't be an agreement to merge s390x into<br>
> EPEL, because the other options like "secondary EPEL", where the builds<br>
> will cloned in similar way as being done for Fedora, or maybe even using<br>
> COPR [1] for the builds will profit from it. Or rather it is the<br>
> necessary first step for any solution.</font></tt><br>
<br>
<tt><font size="2">I have set up mock on one of my z test systems, but I ran into a snag;</font></tt><br>
<tt><font size="2">I couldn't get a working mock configuration for epel-7-s390x. I tried</font></tt><br>
<tt><font size="2">copying epel-7-x86_64.cfg and changing the repo URLs, but it failed to</font></tt><br>
<tt><font size="2">set up the chroot jail because it couldn't find @buildsys-build. I also</font></tt><br>
<tt><font size="2">tried to change the chroot_setup_cmd to use another package group; no</font></tt><br>
<tt><font size="2">luck either. Could you help me out on that front?</font></tt><br>
<br>
<tt><font size="2">Could you elaborate on "secondary EPEL" and cloning builds? I am not</font></tt><br>
<tt><font size="2">familiar with those concepts.</font></tt><br>
<tt><font size="2"><br>
Bryan</font></tt></body></html>