18:00:48 #startmeeting EPEL (2019-04-24) 18:00:48 Meeting started Wed Apr 24 18:00:48 2019 UTC. 18:00:48 This meeting is logged and archived in a public location. 18:00:48 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:48 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:48 The meeting name has been set to 'epel_(2019-04-24)' 18:00:48 #meetingname epel 18:00:48 The meeting name has been set to 'epel' 18:00:48 #topic Chair and Introductions 18:00:48 #chair bstinson Evolution nirik smooge pgreco tdawson 18:00:48 Current chairs: Evolution bstinson nirik pgreco smooge tdawson 18:00:49 #topic Agenda 18:01:11 morning 18:01:12 hello 18:01:18 #info https://pagure.io/epel/issue/54 18:01:18 * nirik goes to get some more coffe, back in a min 18:01:22 Hi 18:01:26 no probklem 18:02:45 * bstinson waves 18:03:10 smooge, as nirik said in the issue, if it is build only dep, I'm ok 18:03:30 it is work for you... 18:03:58 it is all work for me 18:04:15 smoogo is just a pawn in the great game of EPEL 18:04:48 #topic Adding another buildtime dep scl 18:05:03 so this was ticket 54 and we have 2 +1 in the ticket and 1 here 18:05:38 My question is this ... do we already do this for other SCL based packages? Or is this the first one? 18:05:49 devtoolset was our previous one 18:05:53 tdawson, dts-6 and 7 18:05:56 that I know of 18:06:22 OK, if we have a precidence, so we know what we're doing (and by "we", I mean someone other than me), then I'm ok with it. 18:06:25 \o 18:06:28 sorry I'm late. 18:06:35 pgreco, it is just devtoolset so it is dts-6/7 and now 8 18:06:52 a corollary to this is that we only did this for EL-7 18:07:01 Oh, I tend to forget dts-8 because I haven't backported it to armhfp yet 18:07:11 we had 2 requests for EL6 last week for things 18:07:15 hello Evolution 18:07:22 dts-8 is for chromium, right? 18:08:51 pgreco, so what we get is the repository rhel-server-rhscl-7-rpms and dts-N shows up in it 18:09:24 what i will need to do is another couple of repositories for the llvm 18:09:46 then have releng add in whatever configs are needed to make koji work with it 18:10:52 then we should be able to have packages build against it 18:12:09 nirik, I think that is all .. I expect there is a step like 'nirik does this thing we all forgot' 18:12:46 so please log into https://pagure.io/epel/issue/54 and add your +1/-1 to that and next week we will close this 18:12:54 * nirik finally gets back 18:13:33 will let nirik inhale some coffee and respond befoe changing topics 18:13:47 yeah, I was already inn favor of this one in ticket 18:14:18 well I just wanted to make sure I had not left out any special work needing to be done other than what I outlined above? 18:15:26 yeah, we need to sync the repo and add it as a new external to the koji tag... and they need to enable it in their spec 18:23:19 * tdawson checks to see if everyone is still here, or if his cat did something to his IRC client again. 18:23:52 tdawson: We read you loud and clear 18:24:09 :) Good to know. 18:24:25 hey look my internet froze 18:24:38 #topic Open Flor 18:24:50 I am going to spell this right someday 18:25:03 Are there any other issues that need to be done? 18:25:17 My old EPEL updated in Bodhi 18:25:27 Well ... not mine ... but "the" old updates in Bodhi. 18:25:48 rm -rf ? 18:25:50 :-P 18:25:57 I'm fine with that 18:26:19 But I'm wondering what people feel is "too old", so that I can remove them. 18:26:26 oh .. the really old ones 18:26:35 sorry I was having a hard time getting context 18:26:50 tdawson, just about anything you feel is too old is ok 18:26:56 There are over 500 Bodhi issues that are over 2 years old 18:27:02 if someone wants it back, it can be rebuilt 18:27:17 tdawson: oh, I was just looking at the updates-testing report 18:27:28 Which doesn't show any of these 18:27:29 it may also help to "wake up" those who want it 18:27:39 perhaps we could get the report improved to show them? 18:27:49 or I guess just unpush them all. 18:27:55 Well, I could start with the really really old ones (9 years old) 18:28:05 is this also a problem on the fedora side? 18:28:10 tdawson, wow!! 18:28:27 I guess not since fedora eol's old releases... and the updates with them 18:28:42 nirik: No, the fedora ones get closed (or something) once they are no longer supported 18:28:48 tdawson, can you put a ticket with that email? We can vote on it next month. 18:28:50 So, F26 and old are all gone. 18:28:50 week 18:29:06 smooge: OK, will do. 18:29:07 right 18:29:19 personally, if it's older than 6 months, burn it down. 18:29:35 but yeah, lets vote once we know what they are/next week. 18:29:36 So here is my policy idea.. when a minor release happens, any updates which are not finalized.. get unpublished 18:29:57 well, all of these are ones with -karma right? 18:29:59 smooge: Yep ... and once we start doing those releases, it will be easy to know. 18:30:15 I'm fine unpushing those at minor releases. 18:30:17 nirik: Nope ... one or two are, but most have 0 karma 18:30:31 tdawson: oh? they just aren't set to autopush? 18:31:12 nirik: I guess not ... and at this point, I wouldn't want them pushed. 18:31:25 I think anything older than X time didn't have autopush as an option 18:31:35 odd. Someone unset that deliberately on them and then didn't push them. 18:31:44 as far as I know it's always been default 18:32:02 we talked about it when we started doing that and decided that we wanted any old packages to be tested versus auto-pushed 18:32:04 anyhow, we should do something to them 18:32:24 Really? none of mine have done autopush ... I thought it's always been off by default. 18:32:32 yeah. 18:32:48 ok. perhaps I am confused. 18:33:23 Well, none of them have +3 karma ... so maybe there is a difference between 2 week autopush vs 3 karma autopush 18:33:25 so 1. do we want autopush? 18:33:39 after X weeks? 18:34:16 ah yes, we decided for epel all should be +3... 18:34:31 dunno... 18:35:34 Well ... if it currently is karma only autopush ... I'd say we ait and change it to X week autopush when we start doing the releases. 18:36:53 hum, that version of autopush isn't implemented yet... I was thinking of the karma based ones. 18:37:10 ah ok 18:37:21 well then 18:37:53 ok tdawson can you put in a ticket on this and we will discuss it there for next meeting 18:38:02 smooge: Yep, writting it right now. 18:38:25 thanks 18:38:38 ok my network is getting funky again 18:39:03 anything else for today? 18:39:35 do we have anything on the rhel7/python3 ? 18:40:04 well other than it might show up in the next release.. but no idea yet since a beta isn't out 18:40:23 right, that is what I meant, anything related to what it might be 18:40:29 and what we'll need to adapt 18:42:17 nothing other than what was in that meail 18:43:02 sorry 18:43:36 np, I was just optimistic ;) 18:45:00 okie dokie then 18:45:19 I am going to close this out. Thank you all for coming. Next week we can get some things done I hope 18:45:34 and thanks to everyone who helps on #epel I really appreciate it 18:45:35 https://pagure.io/epel/issue/55 18:46:01 You can close out, just wanted to get that in the meeting. 18:46:11 #info https://pagure.io/epel/issue/55 WHat to do with old packages 18:46:11 #endmeeting