16:00:43 <smooge> #startmeeting EPEL
16:00:43 <zodbot> Meeting started Fri Sep 12 16:00:43 2014 UTC.  The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:43 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:01:01 <smooge> #meetingname EPEL-2014-09-12
16:01:01 <zodbot> The meeting name has been set to 'epel-2014-09-12'
16:01:21 <smooge> #topic Meets and Greets
16:01:27 <bstinson> hi all
16:01:31 <smooge> hello
16:01:51 * nirik is sort of here, but trying to catch up on things.
16:02:23 <stahnma> hello
16:02:45 * stahnma didn't find much time to respond to the mailing lists threads, but is happy to see active discussion
16:02:57 <smooge> #chair smooge nirik Evolution dgilmore bstinson
16:02:57 <zodbot> Current chairs: Evolution bstinson dgilmore nirik smooge
16:03:46 <smooge> #topic Agenda Listing
16:04:24 <smooge> #info Greetings and roll call
16:04:24 <smooge> #info Old Business?
16:04:24 <smooge> #info New Business?
16:04:24 <smooge> #info EPEL governance
16:04:25 <smooge> #info EPEL.dot proposal
16:04:25 <smooge> #info cloud-init convergence
16:04:27 <smooge> #info website cleanup
16:04:29 <smooge> #info Open Floor
16:04:38 <dgilmore> uggh I hate fridays
16:04:43 <smooge> that is a lot so I don't think we will hit it all.
16:04:58 <dgilmore> stuck in meetings all morninf
16:04:59 <smooge> #topic Old Business
16:05:11 <smooge> well we could move the meeting to mondays :)
16:06:26 <smooge> is there any old business from the last meeting. I don't think there is but wanted to put it on the agenda just in case
16:06:52 <stahnma> none from me
16:07:02 <bstinson> none here
16:07:30 <smooge> ok then
16:07:34 <smooge> #topic New Business
16:07:55 <smooge> ok then first thing.. is there a better time for these meetings.
16:08:47 <stahnma> Personally, I like this time.
16:08:56 <smooge> nirik, dgilmore any better time for your schedules?
16:09:02 <stahnma> it's a rare unoccupied hour from $DAYJOB
16:09:17 * nirik shrugs... anytime is as good as any other for me. ;)
16:09:29 <nirik> we could try doing a whenisgood thingie.
16:10:43 <dgilmore> smooge: the time works, I just have a bunch of meetinsg on fridays. if i dont get sucked into things i can get out of the house early enough
16:10:58 <dgilmore> just frustrated that more often than not im getting sucked into work and not getting out
16:11:20 <smooge> ok just wanted to make sure this slot wasn't conflicting with too many other things.
16:12:02 <Evolution> here-ish
16:12:37 * bharper is lurking
16:13:01 * smooge figures Evolution's irc lag will keep him about 15 minutes behind. So what jobs do we need him to do?
16:13:44 <bzbot> New Fedora EPEL bug 1141300 filed by rbean@redhat.com.
16:13:45 <bzbot> Bug https://bugzilla.redhat.com/show_bug.cgi?id=1141300 python-stomper, unspecified, unspecified, ---, lmacken, NEW , Update to python-stomper-0.2.9 for epel7
16:13:47 <smooge> ok is there any other new business that I should look at?
16:13:51 <dgilmore> smooge: fix all bugs
16:14:09 <smooge> yeah.. I need to put that as my monday work todo.
16:14:09 <dgilmore> smooge: not sure, that sssd issue was taken care of
16:14:16 <smooge> dgilmore, thanks
16:14:48 <smooge> I have a list of other apps which are older in EPEL than in i386/x86_64. how should I 'feed' them
16:15:08 <smooge> put the list of packages to the list? file bugs in bugzilla? tickets in releng?
16:15:36 <nirik> I'd say list first? then go from there?
16:15:42 <smooge> ok will do that
16:15:44 <dgilmore> smooge: file epel bugs
16:15:51 <smooge> and then that
16:16:05 <nirik> yeah.
16:16:37 <smooge> dgilmore, those would be in bugzilla against the package itself or somewhere else. sorry I want to make sure I am not filing them where you won't see them
16:17:17 <dgilmore> smooge: against the package itself
16:17:43 <dgilmore> smooge: in the sssd case they had not realised that hadn't retired it
16:18:05 <smooge> okie dokie.
16:19:36 <smooge> alright I should hopefully have a list of packages that we 'update' base with in x86_64/i386. EG if package-3.14 is in base and we are shipping package-3.15 somehow
16:20:00 <smooge> I don't think it will be (m)any but I wanted to do a cleanup just in case
16:20:23 <smooge> I will email the list and then do bugs against packages
16:21:25 <smooge> hopefully I will have a nice script we can run regularly but so far I am looking at a monster
16:22:10 <smooge> ok I sent out a list of package issues repoclosure issues.
16:22:37 <smooge> dgilmore, nirik file bugs against those packages or something else as they mostly are requiring packages we don't ship anymore.
16:23:27 <nirik> those packages that have the broken deps I guess.
16:23:43 <nirik> note that there are corner cases where the 'fault' isn't the package itself.
16:24:46 <smooge> i expect that is the case. a couple though like the 389 packages and the django ones I saw in el5
16:25:23 <bstinson> are there other cleanup cases we should be developing tools for?
16:28:06 <smooge> bstinson, there are probably. I know we want to make sure we don't have broken packages (repoclosure) and we don't want to have packages that don't have explicite conflicts (eg packageA and B own a file but don't have a Conflicts: line)
16:28:58 <smooge> and we want a tool which sees if we accidently update a package in the base OS
16:29:23 <smooge> dgilmore, nirik any other cases we would like tools ?
16:29:49 * nirik ponders
16:30:17 <nirik> those are the biggies I guess.
16:31:46 <smooge> ok thanks.
16:33:01 <dgilmore> smooge: we really need to get some kind of api that will let us easily query what is in RHEL
16:33:31 <dgilmore> so we can then easily do things like make sure we do not override rhel packages
16:34:11 <smooge> yeah.. I am currently basing off my stuff of what is in CentOS core as I can test that easiest
16:34:15 <dgilmore> and file bugs to make sure packages are updated in epel when they are in RHEL if tehy are in epel for limited arch support
16:35:12 <nirik> that would be ideal yeah.
16:35:28 <dgilmore> the weakest link is RHEL
16:35:42 <dgilmore> in that they are the ones doing odd things we need to work around
16:35:58 <dgilmore> they are the ones we need to do insanity checks against
16:36:09 <nirik> a while back patrick had the idea we could use bugzilla. Not sure it would work, but might.
16:36:14 <dgilmore> CentOS is sane in that regards
16:36:24 <nirik> ie, we know a component is in rhel when it has a bz component.
16:36:43 <dgilmore> not sure that will work
16:36:58 <dgilmore> and that doesnt let us know limited arch support
16:37:13 <smooge> dgilmore, are you looking for a more of a heads up than RHEL-6.6 is out time to do insane war dance?
16:37:58 <smooge> or RHEL-6.6 is out, run this script and see what is in RHEL-6.6-x86_64 and what is in RHEL-6.6-i386 and what is in RHEL-6.6-ppc
16:38:15 <smooge> and then say "these packages would be ok for PPC only."
16:38:23 <dgilmore> smooge: well im thinking we need some kind of always up api
16:38:36 <dgilmore> so that we can check when processing epel branch requests
16:38:49 <dgilmore> and write tooling to monitor limited arch packages
16:39:14 <dgilmore> and when a point release comes out we can easily work out what adjustments we need to make
16:40:37 <smooge> ok.
16:42:03 <smooge> so it could look at the repos we sink from satellite and builds its info there and be queried inside of Fedoraland.. or are we looking at neeing it to be in RH
16:42:42 <dgilmore> ideally RH provides it, but i suspect we will need to do it and have it in fedoraland
16:42:51 <dgilmore> and likely it will have to be limited to phx2
16:43:12 <dgilmore> so we don't get in trouble for leaking data
16:44:19 <smooge> yeah.
16:45:08 <smooge> ok so I don't think we are going to get to all of the other items on the agenda today. Is there any of the remaining that people want to face today or put off for email/future meeting?
16:46:12 <smooge> dgilmore, nirik bstinson Evolution ? Otherwise I would like to motion to table for next meeting and adjourn
16:46:26 <dgilmore> ive nothing else
16:46:26 <nirik> yeah, nothing is urgent IMHO.
16:47:36 <smooge> bstinson, Evolution ?
16:48:28 <smooge> smooge is for the motion. So it is +3/0/2 which I am going to say is a motion passed.
16:48:57 <smooge> meeting is adjourned til next week when I hope to have a more focused agenda.
16:49:00 <smooge> #endmeeting