18:01:13 <smooge> #startmeeting EPEL (2019-06-19)
18:01:13 <zodbot> Meeting started Wed Jun 19 18:01:13 2019 UTC.
18:01:13 <zodbot> This meeting is logged and archived in a public location.
18:01:13 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:13 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:01:13 <zodbot> The meeting name has been set to 'epel_(2019-06-19)'
18:01:13 <smooge> #meetingname epel
18:01:13 <zodbot> The meeting name has been set to 'epel'
18:01:13 <smooge> #topic Chair and Introductions
18:01:13 <smooge> #chair bstinson Evolution nirik smooge pgreco tdawson
18:01:13 <zodbot> Current chairs: Evolution bstinson nirik pgreco smooge tdawson
18:01:23 * tdawson is here.
18:01:23 <smooge> OK now I am doing this meeting right this time
18:01:36 * bstinson waves
18:01:40 <nirik> morning
18:01:42 <pgreco> hello
18:02:26 <smooge> hello all again\
18:02:51 <smooge> So this will be an open floor meeting as I pretty much have been bogged down on other things
18:03:34 <pgreco> ok, I have 1 thing in mind
18:03:34 <smooge> The topics from last meeting were sgallagh's EPEL rawhide/wagonwheel concept #topic EPEL Rawhide (take 2)
18:03:34 <smooge> #info https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/FYOOSAJOTDNCE4RLF32ORFO6WL2M5WD5/
18:03:51 <smooge> and EPEL-8 status
18:03:59 <smooge> pgreco, you can go first
18:04:05 <smooge> #topic Open Floorish
18:04:15 <pgreco> just note it for later, 7.7beta/python 3.6
18:04:26 <pgreco> let's start with epel-8
18:04:28 <sgallagh> .hello2
18:04:30 <zodbot> sgallagh: sgallagh 'Stephen Gallagher' <sgallagh@redhat.com>
18:05:47 <smooge> #topic EPEL-8 status
18:06:29 <smooge> from last week, We have grobisplitter splitting out repos daily and staging koji pointed to it
18:07:36 <smooge> mboddu, got all the items for building working in staging koji and we were able to build a couple of pakcages
18:08:07 <smooge> tdawson, discovered a problem where koji was kicking out some packages from the buildroot due to mergerepo
18:08:48 <smooge> mboddu, reset the rhel-8 to be seen as a bare mode versus other merge modes, then discovered a problem in koji where it was applying blockers and failing if we were in bare mode.
18:09:12 <smooge> mikem then worked out a patch and we need to apply the patch to koji and see if that fixes the issue
18:09:23 <smooge> nirik, does that sound about right?
18:09:27 <pgreco> oh, fun days.....
18:09:59 <nirik> yep. sounds right. I am building that patched koji now.
18:10:29 <smooge> we will be working through these for the next couple of days and hope to get a set of test builds done and then a 'compose' out the door
18:10:52 <nirik> well, a compose tested... not sure we want to push the stg composes anywhere public
18:12:14 <smooge> yeah sorry.. we won't be pushing it but I will be pointing out the builds on list so people can 'test' things out of koji.stg.fedoraproject.org
18:13:01 <mboddu> smooge: That sounds about right, more fun stuff to do :D
18:14:14 <smooge> So in the past with many different ways we branch and compose.. we used to put up a web page where developers would put up what packages they wanted branched.
18:15:11 <smooge> With the current ways we branch etc.. is that still needed or is there a better mechanism to follow?
18:15:56 <nirik> yeah, not sure. I think the normal process won't scale well to people branching a lot...
18:16:09 <nirik> but I guess we could do them as releng tickets? or we could do a wiki page I suppose
18:16:49 <smooge> I am ok with whatever works better for the releng team?
18:17:28 <mboddu> smooge: Question (lack of historical knowledge): Is it for maintainers who wants a epel-8 branch in dist-git?
18:17:43 <smooge> From looking at the old pages this was for maintainers
18:17:49 <smooge> Not for end users
18:18:08 <nirik> mboddu: yes.
18:18:16 <smooge> it was so a large mass branch could be done by releng vs 1 by 1 by 1
18:18:38 <nirik> so, say I want to branch the Xfce desktop... I could file 25 tickets one for each package, or I could put them all in a list and just say 'do all these'
18:18:52 <smooge> I was wondering if a master ticket in releng would work where we say if you want packages processed on YYYY-MM-DD please add your package to this ticket.
18:19:16 <mboddu> smooge: Okay, if we know all of them or bunch of them, then wiki is okay with me or if its 1 by 1 then releng ticket, and I can update the wiki once I processed the tickets for infomational purposes
18:19:17 <smooge> Then on YYYY-MM-DD all of those are done and we close the ticket and do another one
18:19:21 <nirik> we do want a record and make sure it's authenticated so we know the maintainer(s) really wanted it
18:19:40 <smooge> Would the ticket allow for authentication?
18:19:51 <mboddu> nirik: I guess one ticket per request, doesn't matter if they had 1 or 100
18:19:52 <nirik> yes, they would have to login to comment
18:19:52 <smooge> The wiki last time had a bunch of people using it as a wishlist
18:20:11 <nirik> mboddu: well, for maintainers it kinda does...
18:20:20 <nirik> I don't want to spend an hour filing tickets...
18:20:38 <smooge> would 1 ticket per set of requests work?
18:20:52 <smooge> if you have 30 packages just put them in one ticket?
18:20:54 <mboddu> nirik: Right, they can put 100 packages in a request or 1 package in a request, thats what I meant
18:21:00 <sgallagh> Wouldit make more sense to default to branching, then let people dead.package it if they don't want it?
18:21:11 <nirik> no.
18:21:20 <nirik> mboddu: the fedscm tool will kick all those out?
18:21:51 <nirik> sgallagh: branching from what? epel7? 5 years ago you wanted to maintain this package... thats a long ass time to assume
18:22:05 <mboddu> nirik: I think we can update fedscm-admin to handle epel-8 branch requests, which might be much easier for people
18:22:17 <sgallagh> ok
18:22:33 <nirik> mboddu: but it can only do one per ticket right?
18:22:39 <mboddu> nirik: yes
18:23:04 <nirik> so, that doesn't solve the problem of maintainers that want to branch 100 of their packages...
18:23:06 <smooge> ok sounds like a wiki page still sounds like the right thing to do again
18:23:35 <smooge> or putting tickets in EPEL ticket tracker and we feed that to releng
18:23:45 <sgallagh> nirik: We can provide a simple script to pass a one-per-line text file that calls fedscm
18:23:53 <mboddu> nirik: I guess people can write a shell script which will clone and request the branches, but not sure if everyone can do that
18:24:15 <nirik> yeah, just so long as we have a simple answer...
18:24:24 <smooge> does fedscm do the branching or does it just request to releng to do the branching
18:24:24 * nirik doesn't much care what it is.
18:24:39 <smooge> aka it just files a ticket
18:24:48 <mboddu> smooge: fedpkg does the requesting and fedscm-admin processes them
18:25:01 * nirik wonders how far we are from replacing the tickets setup, but likely further than we can wait for
18:25:35 <smooge> so what needs to be made so that fedpkg requests would work
18:25:45 <sgallagh> right, ok. So a simple script to call fedpkg doesn't seem too hard
18:25:57 <mboddu> smooge: General workflow is "fedpkg request-branch epel-8" which files a ticket at pagure.io/releng/fedscm-requests and then fedscm-admin tool is used to process the requests by using "fedscm-admin process all" which will process all the open tickets
18:26:19 <mboddu> smooge, sgallagh : right
18:27:07 <pgreco> for i in xfce*;do pushd $i;fedpkg request-branch epel-8;done
18:27:17 <mboddu> smooge: I can create the script for you
18:27:20 <pgreco> of course there is a popd missing ;)
18:27:26 <nirik> well, of course they aren't all named xfce* ;)
18:27:32 <mboddu> pgreco: Not exactly, what if the repo isn't cloned
18:27:37 <smooge> cd EPEL-sources
18:28:12 <pgreco> nirik, well, we were using xfce as the multi-package example ;)
18:28:46 <smooge> ok I think we are ratholing here.. I think we have a  couple of solutions we can deal with on the list?
18:29:09 <nirik> yes, but my point is that the list of packages I would branch for xfce isn't named like that. ;) xfdesktop, xfce4-session, Thunar, they have all kinds of names.
18:29:18 <nirik> yeah, we don't need to decide this today
18:30:42 <smooge> OK next up
18:30:49 <smooge> #topic RHEL-7.7 changes
18:30:57 <smooge> #info RHEL-7.7 beta is out
18:31:15 <smooge> #info RHEL-7.7 ships with python36
18:31:29 <smooge> #info wheeeeeeeeeeeeeeee
18:31:41 <smooge> pgreco, does that cover it :)
18:31:58 <pgreco> yeap, exactly that
18:32:11 <tdawson> Will we have to rebuild all the python36 based packages?  Or should they "just work" ?
18:32:34 <pgreco> my guess is that it will be more of a remove than a rebuild job
18:32:45 <smooge> I expect most should just work after we remove the conflicts
18:32:59 <pgreco> but it would be good to coordinate the version they will release
18:33:03 <tdawson> OK
18:33:15 <pgreco> so epel doesn't have a bigger ENVR
18:33:39 <smooge> thankfully the same developer is doing both builds...
18:34:47 <pgreco> that simplifies things a lot :D
18:35:06 <smooge> so if they do... they only have themselves to blame :P
18:35:37 <smooge> pgreco, did you see anything else? I have not had time to blow up 7.7b to see if there are other changes
18:36:14 <pgreco> I don't think so
18:36:21 <pgreco> that was more than enough
18:36:26 <smooge> yeah :)
18:36:50 <smooge> ok so anything else for this meeting or should I let you find people have 20 minutes before the next meeting or 2-3 for the day?
18:36:57 <nirik> glad epel could proof of concept a python3 stack for rhel. ;)
18:37:10 * smooge puts that as another win for EPEL :P
18:37:14 <pgreco> yeap
18:38:58 <smooge> Was there anything people wanted to discuss on the sgallagh proposal? Should I tap it on the mailing list for review again and we 'vote' on it next week?
18:40:20 <smooge> ok I will tap it on the list and we will try to vote it up/down/concensus next week
18:40:25 <smooge> #topic open floor
18:41:24 <smooge> thank you all for coming... see you next week
18:41:27 <smooge> #endmeeting