18:03:30 #startmeeting epel 18:03:30 Meeting started Fri Jul 10 18:03:30 2015 UTC. The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:03:30 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:03:38 #meetingname epel 18:03:38 The meeting name has been set to 'epel' 18:03:52 #chairs nirik dgilmore Evolution bstinson avij 18:03:59 morning everyone 18:04:02 #chair nirik dgilmore Evolution bstinson avij 18:04:02 Current chairs: Evolution avij bstinson dgilmore nirik smooge 18:04:02 hi all 18:04:11 #topic Meats and Greets 18:04:35 hi I am your majordomo for the EPSCO meeting today. 18:04:43 hello, long time no see. I was travelling for the last two weeks, back home today. 18:04:49 hi avij 18:05:11 yeah lots of folks have been out or traveling or the like 18:05:18 tis the season 18:05:58 ok current chimed in steering committee members: avij, bstinson, and nirik. We have a bare quorum 18:06:07 dgilmore, you available? 18:06:25 #topic Outstanding Issues 18:06:46 OK there has not been a meeting for a while so I am not sure what topics are currently outstanding 18:07:17 smooge: yeah 18:07:44 Oh mirrormananger 18:08:21 There were a lot of reports about bad mirrors a while ago. puiterwijk worked on a script to try and determine what mirrors and such were happening and also a script to fix broken pickles 18:08:31 smooge: ppc64le, i686, aarch64 support also 18:08:39 as far as I know we have had no server side issues since the ones a few weeks ago 18:08:56 We didn't see any last week when I was pinging people who complained on #centos. 18:09:08 and on #epel so I think the issues are better now 18:09:43 I don't know of any other issues... 18:09:48 so time for new topics 18:09:53 dgilmore: secondary arches are supported by my script and report as OK on my last daily run 18:10:02 if anyoone has mirror issues, please report them. ;) 18:10:07 #topic Secondary architectures (or whatever they should be called) 18:10:17 puiterwijk: nothing to do with mirrormanager 18:10:34 puiterwijk: my point was to do with supporting those arches in epel7 18:10:35 There have been a couple of requests for building architectures which aren't ones we cover 18:10:54 * nirik is still not sure of any good plan for some of these. 18:11:06 nirik: me either 18:11:15 aarch64 and ppc64le we could possibly have builders for. 18:11:17 #info other arches: s390, ppc64le, i386, aarch64, arm32, ppc64be 18:11:35 i686 is centos only 18:11:53 s390 we would likely have no local builders for 18:11:57 and so would be arm32 18:12:23 s/likely/definitively and absolutely/ 18:12:46 smooge: we should get a z series box in phx2 18:13:13 dgilmore, we should also get a moon base. let me tell you which one is more likely :) 18:13:22 I do not know the best way to support the different arches 18:13:26 has the hercules emulator been considered for s390 builds? 18:14:04 markwkm: it could be possible. but massively slow 18:14:04 we don't normally allow emulated builds 18:14:18 well, fedora doesn't anyhow 18:15:40 perhaps we could try and come up with a plan for these at flock? but not sure centos and other interested parties would be there I guess. 18:16:08 well someone from centos was going to be there from the releng/centos meeting that sgallagh wanted to start 18:16:10 for sure kbsingh and I will be there 18:16:18 i have access to z hardware and would like to see how i could help 18:16:33 okay lets talk at flock on how to add other arches 18:16:35 oh great.. I can't go to a fricking FLOCK and finally kbsingh can come over 18:16:55 smooge: I think you two are teh same person 18:16:59 never seen together 18:17:03 could be.. 18:17:06 ^ this is true 18:17:23 we even sound alike 18:18:19 so there are a couple of issues here that I would like to outline in this meeting so that people reading the mail later have an idea WHY it has to be put off until Flock. 18:18:30 smooge: sure 18:19:08 The first issue I see is what I would call 'Koji fragility' but probably has a better name with releng 18:19:53 If a builder/architecture is unavailable for a particular release (epel-7, etc) all builds for that release are blocked 18:20:36 So if we have an s390 builder in amsterdam that we can't get to for some reason... all of EPEL for that release are blocked 18:20:56 dgilmore, did I phrase that correctly? 18:21:17 smooge: sure, I do not see that as a big issue though 18:22:31 The second issue is that of chain of evidence. We control all our builders for primary architectures so that if a builder is tampered with we have outside control on it. 18:23:05 smooge: that would need to happen for builders for any architecture where a builder is remote 18:23:17 * nirik dislikes remote builders for that reason 18:23:17 smooge: and the only possible remote arches is s390 18:23:49 Several of the architectures would require us to trust the outside s390 isn't tampering in the builder 18:24:11 s/Several of the architectures/A remote s390/ 18:25:33 to me the trickiest thing is that the way koji does its things we need the nvrs to match up exactly 18:25:51 The third issue is koji and download disk space. The number of packages for each platform would require us to budget for more disk space than what we had 18:25:58 and if we add 32 bit x86 we may have issues with the builds CentOS has patched 18:27:04 Fourth, koji has certain NVR needs for build requirements. This may be affected by the way 32 bit x86 is patched by CentOS 18:27:26 any other issues ? 18:27:56 for rhel based ones, they may not have the same package set as x86_64 18:28:10 (this is a long ongoing issue with ppc64 and such, but worth mentioning) 18:28:26 There is another issue I just realized. 18:29:28 Sixth, CentOS does not have seperate channels like RHEL does for packages. This means that they have packages we don't have in our build root due to the mixing of Workstation/Server/Cluster/ etc while we only have Server 18:29:32 nirik: less of an issue now but yeah 18:29:48 Seventh, different arches have different package sets 18:31:24 OK I think that covers the major issues with 'secondary architectures' 18:31:50 smooge: mostly yeah 18:32:07 I expect there are other issues but those seem to be the major stoppers 18:32:13 are there others dgilmore ? 18:32:45 smooge: likely. but right now I am not thinking of any 18:32:56 ok cool. we can add them later. 18:33:30 #info There are at least 7 major problems which need to be worked through so that other architectures can be added to EPEL. 18:33:53 smooge: I do not see a lot of them as problems 18:33:55 #info there will be a meeting at FLOCK between Releng/CentOS and others to discuss how to work on these 18:33:59 but sure 18:33:59 \ 18:34:06 (CentOS hat on) I'll make sure we talk through some of these on our end before FLOCK 18:34:47 #info FLOCK is https://fedoraproject.org/wiki/Flock August 12 -> 15 in Rochester NY 18:35:11 ok any other items for the committee? 18:35:23 #topic Open Flood 18:35:48 I had a few things to mention... 18:35:55 python34 is in epel7 stable now. 18:36:06 epel-rpm-macros is in epel7 stable also. 18:36:40 There's some movement to add it to el5/el6 too to allow us to make macros more standard between fedora and epel 18:37:00 thats all I had I think 18:38:24 nirik: do we need to update comps to always include epel-rpm-macros in buildroots? 18:38:43 yes, that would be good. 18:38:50 wasn't sure the status on that 18:38:52 will get that done 18:39:17 thanks nirik. that is big news on the python34 route 18:40:37 nirik: koji is done 18:40:42 hrmm, was it not in the buildroots before? 18:40:42 dgilmore: cool. 18:41:00 bstinson: the srpm build root probibly not. 18:42:03 ah, that's probably why it didn't create the /usr/bin/python3 symlink (just noticed that a couple of days ago) 18:42:33 not sure thats related, but we can investigate. 18:42:42 nirik: it was not 18:44:22 comps is done 18:44:32 will go out in the next push started after now 18:50:44 ok I think we can close this meeting out. 18:50:47 #endmeeting