15:02:08 <mboddu> #startmeeting RELENG (2020-10-13)
15:02:08 <zodbot> Meeting started Tue Oct 13 15:02:08 2020 UTC.
15:02:08 <zodbot> This meeting is logged and archived in a public location.
15:02:08 <zodbot> The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:08 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:02:08 <zodbot> The meeting name has been set to 'releng_(2020-10-13)'
15:02:08 <mboddu> #meetingname releng
15:02:08 <zodbot> The meeting name has been set to 'releng'
15:02:08 <mboddu> #chair nirik sharkcz pbrobinson pingou mboddu dustymabe ksinny jednorozec
15:02:08 <zodbot> Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou sharkcz
15:02:08 <mboddu> #topic init process
15:02:14 <mboddu> Lets see who is around
15:02:23 <jednorozec> hello
15:02:23 <sharkcz> hi, I am here
15:02:25 <nirik> morning
15:02:30 <gchang> Hi!
15:03:27 <mboddu> Hello guys
15:04:06 <mboddu> I am in multiple meetings, so this meeting might go slow
15:04:10 <mboddu> To start with
15:04:56 <mboddu> gchang is an intern with Red Hat and she is going to help us out with some of the releng/infra work
15:05:13 <mboddu> #topic New Introductions
15:05:22 <nirik> welcome gchang!
15:05:25 <mboddu> gchang: Do you wanna add something here?
15:05:26 <gchang> Yeah! I'll be here until the end of April
15:05:42 <jednorozec> welcome gchang!
15:05:46 <gchang> Hm, I'm just excited to be here haha
15:06:26 <mboddu> Thanks gchang :)
15:07:05 <mboddu> #topic Automate Unretirement
15:07:22 <mboddu> This is something we wanted to do for a long time and we would like gchang to pick it up for us
15:07:34 <mboddu> Last week, jednorozec and I discussed about it
15:08:08 <mboddu> For now, gchang will help us to automate the unretirement process detailed in https://docs.pagure.org/releng/sop_unretire.html
15:08:27 <gchang> Sounds like a plan
15:08:46 <mboddu> But once its done, we will look at incorporating that work into fedpkg and fedscm-admin
15:09:17 <mboddu> The final plan is that, people can request unretirement through fedpkg and fedscm-admin will process the unretirement
15:09:43 <mboddu> what do you guys think of the idea adding it to fedpkg and fedscm-admin?
15:11:07 <nirik> sure I guess.
15:11:23 <jednorozec> +1
15:11:33 <sharkcz> good plan
15:14:15 <mboddu> Okay, moving on
15:14:50 <mboddu> #topic #9804 Orphan kyotocabinet package only on Rawhide
15:14:55 <mboddu> #link https://pagure.io/releng/issue/9804
15:15:09 <mboddu> This is a weird request and one of them makes me miss pkgdb
15:15:26 <nirik> ha. yeah.
15:15:34 <mboddu> Anyway, other than https://pagure.io/releng/issue/9804#comment-695475, the only other way that I can think of is
15:16:21 <nirik> well, they can change the bugzilla assignee for fedora bugs to orphan.
15:16:32 <mboddu> Orphan the package and make the reporter "Collaborator" with access to epel branches, but if orphaned, it might get retired eventually
15:16:36 <nirik> but they still would be maintaing it
15:16:44 <nirik> yeah
15:17:32 <mboddu> From what I understand, its more like he dont want to maintain them rather than just bz
15:18:24 <nirik> so, give them the options we have... can't do much more than that
15:22:28 * nirik has an item for later after other topics.
15:22:55 <mboddu> Okay, I will update the ticket
15:24:21 <mboddu> #topic #9801 Allow build_from_srpm for fNN-coreos-continuous Koji target
15:24:26 <mboddu> #link https://pagure.io/releng/issue/9801
15:24:41 <mboddu> I think we should enable this just like the infra tags
15:24:45 <mboddu> nirik: Wdyt?
15:26:04 <nirik> as long as we are 100% sure that it never will get pushed into the real releases...
15:28:36 <mboddu> nirik: Is there anyway that we can block it?
15:28:38 <mboddu> nirik: Is there anyway that we can block it?
15:28:51 <sharkcz> can a policy be set up to ensure that?
15:28:58 <mboddu> Sorry for the double ping, my irc client is acting up
15:29:27 <nirik> I don't think so... we could make policy refuse to tag things from one to the other, but I don't think it knows 'built from src rpm'
15:31:17 <nirik> at least I don't think so. I can look more if you want...
15:32:25 <mboddu> We can ask koji folks for help on creating a policy like that
15:32:56 <nirik> let me look at policy again and I can update the ticket.
15:34:35 <mboddu> Okay, thanks nirik
15:34:44 <mboddu> I will also take a look if I can find anything
15:40:22 <mboddu> #topic #9746 Please provide the src repo of eln-build
15:40:45 <mboddu> #link https://pagure.io/releng/issue/9746
15:41:04 <mboddu> nirik: We have to make a decision on storage
15:41:12 <nirik> storage isn't the problem really.
15:41:31 <nirik> it's more cpu every single time a newrepo is done...
15:42:42 <nirik> anyhow, I guess we can enable it...
15:45:03 <mboddu> Okay, I will enable it
15:46:12 <nirik> it should be a much smaller set than rawhide say
15:46:51 <mboddu> Definitely
15:46:56 <mboddu> #topic Open Floor
15:47:00 <mboddu> nirik: You are up
15:47:05 <nirik> I have 2 things actually...
15:47:38 <nirik> first: we have a lot of side tags... shall we set some policy around them? like:
15:48:09 <nirik> sidetags older than 60 days will be removed. sidetags with 0 builds in them will be deleted after two weeks.
15:48:29 <sharkcz> +1
15:48:37 <jednorozec> +1
15:48:51 <mboddu> I am not sure about 60days older one, since KDE and gnome side tags definitely take more time
15:49:02 <nirik> We would need a freeze break or waiting until after to implement it of course.
15:49:09 <jednorozec> I would say if no new build in for 60days delete.
15:49:13 <nirik> no, named sidetags wouldn't be affected.
15:49:24 <nirik> here's the current list:
15:49:38 <mboddu> We asked them to start using bodhi side tags as it doesn't require releng help
15:50:12 <nirik> https://paste.centos.org/view/3938b34c
15:50:37 <nirik> those are the ones that would be deleted currently using the above policy
15:51:55 <jednorozec> I would say last build date + N days as condition for deletion.
15:51:56 <nirik> 60 days is likely too long... perhaps 30 would be better, or less.
15:52:20 <nirik> well, I am using the already implemented and existing script... :)
15:52:26 <Southern_Gentlem> start with 60 and see
15:52:28 <sharkcz> as the releng provides side tags won't be affected, then I would say go with the plan
15:52:38 <sharkcz> makes a lot of sense
15:53:12 <mboddu> nirik: I guess last build + 60 days is fine
15:53:15 <nirik> I'll file a ticket on it and we can track announcing/implementing.
15:53:21 <mboddu> Ack
15:53:35 <nirik> well, I am not sure the script does that...
15:54:11 <jednorozec> just the date of creation of the side tag is not really useful.
15:54:16 <nirik> empty ones are likely made and never used.
15:54:31 <nirik> because koji should be deleting them when there are no more builds in them
15:54:50 <nirik> jednorozec: yeah, so perhaps we should get koji folks to adjust the script?
15:55:01 <mboddu> Yeah, lets do that
15:55:32 <nirik> I might be misreading it too...
15:55:56 <mboddu> Lets create a ticket and track it
15:56:01 <jednorozec> +1
15:56:11 <mboddu> nirik: You got a 2nd thing to discuss?
15:56:15 <nirik> oh yeah.
15:56:39 <nirik> So, we talked a while back about renaming the master branch in places... we created a doc, and then we got busy and didn't do anything more. ;(
15:56:49 <mboddu> Yup
15:57:00 <nirik> I was wondering if folks are ok with me making a f34 change on it...
15:57:11 <nirik> and updating the docs more
15:57:33 <mboddu> Sure, if you want, I can help you with the change and you can add me to that change as well
15:57:35 <nirik> I can update things and ask for review? but I'd like to start moving it forward again
15:57:43 <mboddu> +1
15:57:44 <nirik> mboddu: that would be great!
15:58:31 <nirik> ok, thats it... ;)
15:58:40 <jednorozec> I have one as well, do we have a plan to replace pdc?
15:58:54 * jednorozec is digging into pdc and import armhfp
15:59:07 <mboddu> jednorozec: We do, but I dont think we will do it anytime soon
15:59:25 <jednorozec> mboddu, ok I will try to update PDC
16:00:22 <jednorozec> but it is complex
16:00:34 <nirik> yeah, we have had several plans...
16:00:41 <nirik> but none of them went anywhere. :(
16:00:53 <nirik> The last one I think was to try and use...
16:00:59 <jednorozec> Can I drive this than?
16:01:13 <mboddu> Its a complex system which we got tied into and we dont have a replacement plan
16:01:22 <mboddu> jednorozec: Sure
16:01:31 <jednorozec> mboddu, do we have requirements?
16:01:34 <nirik> ack. I can't recall the thing... will have to look it up
16:02:12 <mboddu> jednorozec: Not exactly :(
16:02:39 <jednorozec> ok, I will create one
16:02:47 <nirik> anyhow, sure! if you want to look at this, please do
16:03:05 <nirik> right now pdc is... old and not good.
16:03:15 <mboddu> Yup
16:03:23 <jednorozec> yeah, from what I have seen. We dont need this kind of complex system
16:03:25 <mboddu> Anyway, thats all I got
16:03:28 <nirik> the first try at replacing it was fpdc
16:04:08 * jednorozec magically resurrect fpdc
16:04:17 <mboddu> Haha
16:04:29 <mboddu> Okay, its over time
16:04:30 <nirik> but I think fpdc was just a reimplementation in flask? not sure...
16:04:55 <jednorozec> thanks!
16:05:12 <mboddu> We thought about postgrest or something like that which is a rest implementation over postgres db
16:06:05 <mboddu> Then there was kinto
16:06:09 <mboddu> Anyway
16:06:12 <mboddu> We are over time
16:06:34 <mboddu> Thanks everyone for joining
16:06:37 <mboddu> #endmeeting