18:00:05 #startmeeting EPEL (2019-08-28) 18:00:05 Meeting started Wed Aug 28 18:00:05 2019 UTC. 18:00:05 This meeting is logged and archived in a public location. 18:00:05 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:05 The meeting name has been set to 'epel_(2019-08-28)' 18:00:06 #meetingname epel 18:00:06 The meeting name has been set to 'epel' 18:00:06 #topic Chair and Introductions 18:00:06 #chair bstinson Evolution nirik smooge pgreco tdawson 18:00:06 Current chairs: Evolution bstinson nirik pgreco smooge tdawson 18:00:28 * bstinson waves 18:00:32 morning 18:00:40 hello 18:00:57 #topic Agenda 18:00:57 #info EPEL-7 aarch64 problems 18:02:00 hello 18:03:13 ok looks like 4 people 18:04:22 bstinson, you around? 18:04:33 yep, i'm here 18:04:47 ok and I see Evolution in channel so I will assume he is present and accounted for 18:04:58 #topic EPEL-7 aarch64 problems 18:05:32 alright we got reports that EPEL-7 builds were having issues because the RPM in 7.7 and 7.6 are different. 18:05:52 do you have an example handy to follow? 18:06:00 the root package is one... 18:06:26 due to the rpm in 7.7 subpackages appear different and the builds fail. 18:07:05 * jsmith lurks 18:08:23 more and more will hit it. 18:08:28 I don't see any failed root builds. Did they get it fixed? Or was it all scratch builds? 18:08:41 I was going to say the same thing 18:08:53 I"m looking if I can find the failed task 18:09:12 Is there a bug or something we can look at? 18:09:53 tdawson https://koji.fedoraproject.org/koji/taskinfo?taskID=37241968 18:10:39 Ouch ... so it's different on different architectures. 18:10:52 yeap, that is the base problem 18:11:16 7.6 was the last release for aarch64 18:11:18 nordugrid-arc is another one 18:11:20 https://pagure.io/releng/issue/8676 18:12:25 so since 7.6 has one version of rpm and other items and 7.7 have other .so updates.. there will be build differences 18:13:23 I guess my only question is if we might migrate it to live next to armv7 in centos land? 18:13:33 or would that work? 18:14:19 currently, epel for armv7 is built in a rather precarious old system (not even koji) 18:14:36 is centos going to do a 7.7 for aarch64? 18:14:44 but if we could create a second koji instance (in fedora or centos, same with me) 18:15:00 to build those arches together, from centos instead of from rhel 18:15:00 we actually could switch to using that if it existed... 18:15:42 i think we have 2 conversations going. let us see if we can get some answers 18:15:50 nirik, old plague system...., in process of being removed 18:16:07 ah, plague... I remember it well. 18:16:33 bstinson, pgreco are there plans to do aarch64 for EL7? I am guessing you would need to do just pure upstream kernel for that 18:16:33 * nirik gets coffee, back in a min 18:17:11 smooge, the current working theory is using same userspace as other arches and using kernel from rhel8 (4.18.x) 18:18:07 which would translate to "just a kernel upgrade from 4.14 to 4.18" 18:18:25 two would be setting up an koji mbox for epel-alt be feasible? 18:18:32 i think we should consider if EPEL proper wants to maintain aarch64 packages for 7 and let CentOS decide what we want to do (and account for the cross collaboration) 18:18:48 smooge: yes (that's where i was going), but not immediately 18:19:47 If we were to continue aarch64 for EPEL7, it looks like we would at least need a new rpm. Do we know if we would need any other packages? 18:22:38 tdawson, I don't know.. 18:22:39 ok, the other question is "what will epel7/aarch64 look like?" 18:22:58 I mean, like other arches (and centos), or like rhel? 18:26:31 tdawson, in looking at the packages rolling out.. there were 2500 packages updated between 7.6 and 7.7 and 1100 have some sort of version bump 18:27:07 Ouch 18:27:20 That sounds like a complete rebuild ... almost. 18:28:17 well that was me looking at finished packages and not srpms 18:29:50 but qt5 got a bump other things got a bump 18:30:08 I don't know how many of those are going to change dependencies 18:30:19 wheee 18:30:31 we would have to use centos 7.7 18:30:43 ok I was hoping pbrobinson would be able to come in with some tips 18:31:01 and the inclusion of python3 is the biggest change affecting us, I think 18:31:54 nirik, yeah. I was not sure how mixing the streams would do 18:32:15 well, it could break, but it's more likely to work than what we have now. ;) 18:32:48 which is basically known not to. 18:33:35 nirik, separate target but using the same koji, could it work? 18:33:49 that would be a lot of mess. 18:34:14 is there any chance of less mess?? :D 18:34:23 IMHO we should try just replacing the external rhel7 aarch64 repos with centos7.7 18:34:25 yes 18:34:42 what about noarch signature? 18:35:39 signature? you mean comparing noarch subpackages? 18:36:09 afaik, koji doesn't like when it gets the same noarch pkg with different signatures in different repos 18:36:28 OK, so tracked it down somewhat. This is not really a matter of rpm being updated (although it might be for perl packages) it's a matter of other packages being added/updated. 18:36:42 which would happen if we pull aarch64 repos from centos, and the other arches from rhel 18:37:18 So, my initial thought of "just add the packages that need to be added" is not a course of action. 18:37:20 well, koji at build time checks all the noarch subpackages and makes sure they are the same, but thats build time of the epel package, it's not checking the repos. 18:37:43 koji itself doesn't check any signatures... it assumes everything in it's store is fine. 18:37:52 nirik, I'm saying before that 18:38:17 it needs all the noarch to be the same in all repos 18:38:24 it checks also on import time, but we never import rhel either... we use external repos... 18:38:52 ok, then I love the idea 18:39:29 I mean isn't rhel7.6 alt already different from 7.6? I know kernel is... but are there other packages that are different? 18:39:56 kernel/boot and I think glibc was a bit newer 18:40:55 ok I am ok with this plan of action 18:41:01 minor fixes shouldn't generate problems, rebases (like qt) or additions (like python3) are likely to break things 18:41:52 nirik rhel7.6alt and rhel7.6 only differ in kernel (3.10 vs 4.14) 18:41:53 we will just expect packages in aarch64 to need a rebuild or break builds overall for the N time it takes for CentOS-7.x to get out 18:42:14 pgreco: are you sure? I see a number of .el7a packages... 18:42:44 maybe arch specific (additions) 18:42:49 which one do you have in mind? 18:43:34 trying to find a epel7 package that builds against a .el7a package so I can see if it's doing what I expect... 18:43:41 but will take more digging 18:44:17 looks like anaconda 18:44:27 that was for 7.5 18:44:42 they fixed anaconda after the release of 7.5 and used el7a 18:44:44 I just have a large bucket 18:44:52 then it got unified in 7.6 18:45:25 and it was done specially for power9, didn't apply to aarch64 18:45:35 iirc :D 18:46:08 so I don't know when things like rdma or binutils were replaced.. 18:46:22 ok in that case.. I think we have a plan of action 18:46:36 well, or as best of one as we can come up with... 18:47:08 I will start syncing c7 trees over and get them merged. I will need a list of them 18:47:38 well, 7.7 doesn't exist yet? 18:47:53 oh yeah 18:48:12 well, cr is in the works, which should be enough for what we need 18:48:32 we could also tell folks to exclude it for now, readd once we have 7.7 in place? 18:48:48 but some of them may forget 18:49:00 I'd rather leave it broken for a few days 18:49:10 if we can come up with a PoC fast 18:49:44 ok is there naything else on this? 18:49:56 we are nearing the end of this meeting 18:49:57 sure 18:52:08 #topic Open Floor 18:52:28 assuming nirik meant sure that we can come up with a PoC versus sure he had something else to say 18:52:55 sure. :) 18:53:05 (yes, you were correct, I have nothing to say) 18:54:31 Nothing from me 18:54:31 ok and with that.. I am going to call this a meeting. I will try to write up what we have come up with as a possible plan and see how it flies in the wind. 18:54:42 thank you all for coming and see you next week 18:54:45 #endmeeting