<div dir="ltr"><div>Misc, is EPEL got recently installed on the builders? </div><div><br></div><div>Can you please resolve the 'Why EPEL on builders?'. EPEL+python3 on builders seems not a good option to have. </div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 20, 2019 at 6:37 PM Michael Scherer <<a href="mailto:mscherer@redhat.com">mscherer@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Le jeudi 20 juin 2019 à 08:38 -0400, Kaleb Keithley a écrit :<br>
> On Thu, Jun 20, 2019 at 7:39 AM Michael Scherer <<a href="mailto:mscherer@redhat.com" target="_blank">mscherer@redhat.com</a>><br>
> wrote:<br>
> <br>
> > Le jeudi 20 juin 2019 à 06:57 -0400, Kaleb Keithley a écrit :<br>
> > > AFAICT, working fine right up to when EPEL and python3 were<br>
> > > installed<br>
> > > on<br>
> > > the centos builders. If it was my decision, I'd undo that<br>
> > > change.<br>
> > <br>
> > The biggest problem is that mock do pull python3.<br>
> > <br>
> > <br>
> <br>
> That's mock on Fedora — to run a build in a centos-i386 chroot.<br>
> Fedora<br>
> already has python3. I don't see how that can affect what's running<br>
> in the<br>
> mock chroot.<br>
<br>
I am not sure we are talking about the same thing, but mock, the rpm<br>
package from EPEL 7, do pull python 3:<br>
<br>
$ cat /etc/redhat-release; rpm -q --requires mock |grep 'python(abi'<br>
Red Hat Enterprise Linux Server release 7.6 (Maipo)<br>
python(abi) = 3.6<br>
<br>
So we do have python3 installed on the Centos 7 builders (and was after<br>
a upgrade), and we are not going to remove it, because we use mock for<br>
a lot of stuff.<br>
<br>
And again, if the configure script is detecting the wrong version of<br>
python, the fix is not to remove the version of python for the<br>
builders, the fix is to detect the right version of python, or at<br>
least, permit to people to bypass the detection.<br>
<br>
> Is the build inside mock also installing EPEL and python3 somehow?<br>
> Now? If so, why?<br>
<br>
No, I doubt but then, if we are using a chroot, the package installed<br>
on the builders shouldn't matter, since that's a chroot.<br>
<br>
So I am kinda being lost.<br>
<br>
> And maybe the solution for centos regressions is to run those in<br>
> mock, with a centos-x86_64 chroot. Without EPEL or python3.<br>
<br>
That would likely requires a big refactor of the setup, since we have<br>
to get the data out of specific place, etc. We would also need to<br>
reinstall the builders to set partitions in a different way, with a<br>
bigger / and/or give more space for /var/lib/mock. <br>
<br>
I do not see that happening fast, and if my hypothesis of a issue in<br>
configure is right, then fixing seems the faster way to avoid the<br>
issue.<br>
-- <br>
Michael Scherer<br>
Sysadmin, Community Infrastructure<br>
<br>
<br>
<br>
_______________________________________________<br>
<br>
Community Meeting Calendar:<br>
<br>
APAC Schedule -<br>
Every 2nd and 4th Tuesday at 11:30 AM IST<br>
Bridge: <a href="https://bluejeans.com/836554017" rel="noreferrer" target="_blank">https://bluejeans.com/836554017</a><br>
<br>
NA/EMEA Schedule -<br>
Every 1st and 3rd Tuesday at 01:00 PM EDT<br>
Bridge: <a href="https://bluejeans.com/486278655" rel="noreferrer" target="_blank">https://bluejeans.com/486278655</a><br>
<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a><br>
<br>
</blockquote></div>