18:00:21 #startmeeting EPEL 18:00:21 Meeting started Wed Apr 27 18:00:21 2016 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:21 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:21 The meeting name has been set to 'epel' 18:00:21 #meetingname EPEL 18:00:21 #chair smooge nirik Evolution bstinson avij 18:00:21 #topic agenda gathering / quorum detection 18:00:21 The meeting name has been set to 'epel' 18:00:21 Current chairs: Evolution avij bstinson nirik smooge 18:00:26 who all is around? 18:00:29 for an epel meeting 18:00:31 present and-or accounted for 18:00:41 greetings 18:01:26 Who has agenda items? 18:01:45 hi all 18:01:47 I'd like to bring up the altarch builds, mostly for notice purposes. 18:02:11 ok. 18:02:31 * nirik was not sure if we were going to see a smooge today... he's still busy with moving... 18:03:20 yselkowitz: you had some agenda item? 18:03:26 or we can do it in open floor I guess... 18:03:39 nirik, I'm together with Evolution 18:03:46 ah. ok. ;) 18:04:06 #topic alternate arch builds 18:04:38 so, we've had quite a bit of user/community demand for armhfp and aarch64 epel packages 18:04:55 but getting epel set up to build these is currently slow-going. 18:05:24 yeah. 18:05:34 there are not at all enough hours in the day. ;( 18:05:35 right now we're looking at cycling the current epel srpms through the offline buildsystem but I'd like to not conflict with epel when/if it finally becomes a thing for altarch 18:06:17 doing this via our offline builders means that we won't pollute the koji community builder and impact the sigs, 18:06:32 however long-term this could be an issue for anyone using priorities or repo protection. 18:06:34 ok. Will those results be available somewhere tho? 18:07:05 yes. I'm not certain yet if we'll do it as a one-off unsigned repo... "use at your own risk" sort, or something more official. 18:07:33 but we will make them consumable in some fashion. 18:07:46 if there are ideas on how best to bridge this once epel exists, I'm all ears. 18:07:57 yselkowitz: did you have anything to add here? 18:08:36 my point was going to be wrt pushing patches necessary for building on aarch64 in as provenpackager 18:08:38 well, I think epel would do bring up just like we did for ppc64le... 18:08:53 rebuild everything scratch and import the aarch64 or whatever builds. 18:10:01 as for actually getting the srpms to build 18:10:24 the rhelsa team has been working on getting this working 18:10:30 https://bugzilla.redhat.com/showdependencytree.cgi?id=1285484&maxdepth=1&hide_resolved=0 18:10:42 cool. ;) 18:10:52 many of the patches have been committed, but many still have not 18:11:15 in order to centos to be able to rebuild epel for aarch64, these patches have to go in now 18:11:26 IMHO, i'd like to have our better builders up and running before we add aarch64 to epel... but hopefully thats not too far out 18:11:51 * nirik doesn't have any objection to pushing them in... as long as they don't break primary should be fine 18:12:08 a few will require coordination with maintainers (namely ghc) 18:12:24 otherwise they are mostly simple fixes from newer versions of fedora 18:12:44 good ol ghc. ;) 18:12:50 yep 18:12:52 yselkowitz: to your knowledge are any of them version bumps that would be problematic for epel? 18:13:24 ghc is not a version bump but it does add some patches from f21 18:13:44 but iiuc if you sneeze at ghc in the wrong direction it breaks :-) 18:13:48 I don't see that being any more of a problam than ghc already is. 18:13:51 so that will take some care 18:13:57 er, problem. spelling ftw 18:14:04 * nirik loves that ghc changes ABI based on how many cpus were used to build it (or it used to anyhow) 18:14:23 otherwise, the changes are intentionally conservative, I don't anticipate any issues 18:15:30 sounds good. 18:15:59 it's nice that someone is taking care of this, thanks 18:17:14 I might be able to commit some cycles to adding it once we get our better builders going... 18:17:32 so is that a consensus for me to proceed with provenpackager-ing these patches? 18:17:32 yselkowitz: is there anything you need from us? 18:17:44 +1 here. I want aarch64! 18:17:49 +1 from me 18:18:04 +1 18:18:15 those changes would need to be done sooner or later anyway, so go ahead. 18:18:27 yep. go forth and git push. ;) 18:18:42 and fedpkg update too 18:19:03 yep 18:19:09 ok, thank you 18:19:09 ok, anything else on this for now? 18:19:20 that covers my end. 18:19:26 cool. 18:19:27 probably follow-up next week wrt anything delicate 18:19:33 sounds good 18:19:56 #info yselkowitz will push needed aarch64 patches into epel packages and update them in prep for mass building. 18:20:03 #topic Open Floor 18:20:09 anyone have anything for open floor? 18:20:24 nope 18:20:32 nope 18:20:41 none here 18:20:54 There was a nginx thread on the list... 18:21:06 which I think we already discussed a few weeks ago... 18:21:22 the version bump ? 18:21:33 yes, 1.10.x is a better target 18:21:40 looks like they plan to go to 1.10.x instead of 1.8.x (1.10.x just came out and has a longer support life and some features that are depreciated in the older ones) 18:21:44 yeah 18:21:50 I agree, just thought I would mention it 18:22:05 wfm 18:22:08 yea 18:22:31 ok, if nothing else will close out in a minute... 18:23:45 Thanks for coming everyone. Go and use the extra 36 minutes scheduled for this meeting for good. ;) 18:23:48 #endmeeting