15:00:08 <jednorozec> #startmeeting RELENG (2021-10-19)
15:00:08 <zodbot> Meeting started Tue Oct 19 15:00:08 2021 UTC.
15:00:08 <zodbot> This meeting is logged and archived in a public location.
15:00:08 <zodbot> The chair is jednorozec. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:00:08 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:08 <zodbot> The meeting name has been set to 'releng_(2021-10-19)'
15:00:08 <jednorozec> #meetingname releng
15:00:08 <zodbot> The meeting name has been set to 'releng'
15:00:08 <jednorozec> #chair nirik sharkcz pbrobinson pingou mboddu dustymabe ksinny jednorozec
15:00:08 <jednorozec> #topic init process
15:00:08 <zodbot> Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou sharkcz
15:00:18 <nirik> morning
15:02:51 <jednorozec> good morning
15:04:57 <jednorozec> so
15:05:17 <jednorozec> .releng 10339
15:05:18 <zodbot> jednorozec: Issue #10339: Create empty `/epel/9` structure - releng - Pagure.io - https://pagure.io/releng/issue/10339
15:05:43 <jednorozec> do we have SOP for such things?
15:05:48 <jednorozec> Where is should be created?
15:06:56 <nirik> it needs added to new-updates-sync and a link to the empty repo added in /mnt/koji/compose/updates/epel9
15:07:42 <nirik> but... not sure it's a super great idea...
15:08:14 <nirik> it's going to cause people to start asking when it will be populated...
15:08:52 <jednorozec> right
15:09:09 <nirik> I can bring this up in the next epel meeting... see what people think?
15:09:17 <jednorozec> +1
15:09:19 <nirik> or we can cc some folks there in the ticket for comment
15:09:22 <nirik> or both!
15:09:27 <jednorozec> Haha!
15:09:41 <mboddu> I dont want to create it, but I would like to leave it as is for now unless we need to create it for epel9 next for any particular reason
15:10:10 <nirik> hey mboddu
15:11:42 <nirik> So, should we ask folks? just close this?
15:12:28 <mboddu> Ask EPEL folks and then close it
15:13:37 <nirik> ok
15:14:10 <nirik> added comment.
15:14:29 <jednorozec> thnaks nirik
15:16:59 <jednorozec> i will close this
15:17:01 <jednorozec> .releng 10116
15:17:03 <zodbot> jednorozec: Issue #10116: Fedora Media Writer 4.2.2 released - releng - Pagure.io - https://pagure.io/releng/issue/10116
15:17:32 <nirik> ok
15:17:42 <nirik> I'm working on notorization, but it's a new ticket.
15:17:55 <jednorozec> yup I have noticed
15:18:04 * nirik is not a macos fan.
15:18:27 <jednorozec> I was unable to use it
15:21:27 <jednorozec> so I was reading through
15:21:29 <jednorozec> .releng 9801
15:21:30 <zodbot> jednorozec: Issue #9801: Allow build_from_srpm for fNN-coreos-continuous Koji target - releng - Pagure.io - https://pagure.io/releng/issue/9801
15:24:05 * nirik re-reads to recall the issue
15:24:11 <jednorozec> So they require disttag filer in bodhi
15:24:25 * jednorozec checks bodhi for such conditions
15:25:18 <nirik> they want to build some packages from src.rpm for us in CI/automation... but never have those leak out to users.
15:28:19 <jednorozec> Ah so its the same build in fNN-coreos-continuous and fNN
15:29:30 <jednorozec> We actually can filter it in bodhi, I am starting to understand it better.
15:29:44 <nirik> no, I don't think so... but I might be misunderstanding the workflow
15:30:54 <nirik> ie, the initial comment has them trying to build: ostree-v2020.6-4.20201007193711329564.master.74.gcc1c26f5.fc31
15:31:10 <nirik> which they want to tag into fNN-coreos-continuous and run thru ci...
15:31:59 <nirik> so what we need is some way to id those things and make sure bodhi rejects them so someone can't accidentally tag them into fNN
15:33:14 <nirik> at least I think thats it. ;)
15:34:24 <jednorozec> so If we disable the fNN-coreos-continuous in bodhi?
15:36:03 <jednorozec> but for identification the dist tag proposal may be solution
15:36:48 <nirik> perhaps both?
15:37:16 <nirik> if we can disable that in bodhi and provide a dist tag that we can match on in koji hub to prevent non admin users from tagging those...
15:41:12 <jednorozec> We should be able to do it
15:41:59 <jednorozec> I am not sure if in the current version, but this sounds like doable thing.
15:42:34 <jednorozec> There is a bunch of filters in the Update model in bodhi
15:44:45 <jednorozec> so
15:44:47 <jednorozec> .releng 7523
15:44:48 <zodbot> jednorozec: Issue #7523: rubygem-connection_pool mess - releng - Pagure.io - https://pagure.io/releng/issue/7523
15:45:01 <jednorozec> There are two thing nirik suggested.
15:45:13 <jednorozec> the fedscm-admin part is implemented
15:45:27 * jednorozec check fedpkg
15:47:51 <nirik> yeah, I meant to circle back on this, but didn't get there
15:52:19 <jednorozec> so the import is handled by pyrpkg
15:54:54 <jednorozec> Anyway it is getting late
15:55:01 <jednorozec> #topic Open Floor
15:55:03 <nirik> I don't think I ever filed the issue...
15:55:12 <nirik> I can try and do so... or you can if you like? :)
15:55:22 <jednorozec> nirik, I will do it
15:55:33 <jednorozec> it needs to be in pyrpkg
15:55:38 <nirik> awesome.
15:55:40 <nirik> jednorozec++
15:55:41 <jednorozec> Maybe i will even submit PR
15:55:57 <jednorozec> it might not be that complex to compare 2 strings :)
15:56:19 <nirik> something computers are good at. :)
15:57:49 <jednorozec> so if there is nothing more for this week I will close the meeting
15:59:55 <jednorozec> #endmeeting