15:00:14 <jednorozec> #startmeeting RELENG (2021-09-07)
15:00:14 <zodbot> Meeting started Tue Sep  7 15:00:14 2021 UTC.
15:00:14 <zodbot> This meeting is logged and archived in a public location.
15:00:14 <zodbot> The chair is jednorozec. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:14 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:14 <zodbot> The meeting name has been set to 'releng_(2021-09-07)'
15:00:14 <jednorozec> #meetingname releng
15:00:14 <zodbot> The meeting name has been set to 'releng'
15:00:21 <jednorozec> #chair nirik sharkcz pbrobinson pingou mboddu dustymabe ksinny jednorozec
15:00:21 <zodbot> Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou sharkcz
15:00:22 <jednorozec> #topic init process
15:00:33 <nirik> morning
15:00:52 <sharkcz> hi everyone
15:01:13 <mboddu> Morning
15:01:43 <jednorozec> good morning/evening
15:03:49 <Southern_Gentlem> howdy
15:05:02 <lenkaseg> hello
15:05:46 <jednorozec> so lets have a look at the tracker
15:08:12 <jednorozec> hmm this relic
15:08:14 <jednorozec> .releng 8026
15:08:15 <zodbot> jednorozec: An error has occurred and has been logged. Please contact this bot's administrator for more information.
15:08:49 <jednorozec> .releng 8026
15:08:52 <zodbot> jednorozec: Issue #8026: Packages are not retired entirely - releng - Pagure.io - https://pagure.io/releng/issue/8026
15:09:17 <jednorozec> it is a relic and it seems to be fixed
15:10:12 <nirik> ok, close? or ask reporter to check for anything left to do?
15:10:30 <jednorozec> I will close it with comment
15:10:37 <nirik> ack
15:12:38 <jednorozec> .releng 8948
15:12:39 <zodbot> jednorozec: Issue #8948: Update list of critpath packages - releng - Pagure.io - https://pagure.io/releng/issue/8948
15:12:58 <jednorozec> I found this by chance when looking into bodhi
15:13:13 <jednorozec> there is a PR to update critpath
15:13:24 <mboddu> We updated it in PDC, but this should be moved to bodhi eventually
15:13:34 <nirik> well I thought it was moving to a toddler?
15:14:27 <nirik> but I don't know the status. would need to ask pingou on that one
15:16:25 <nirik> I guess yeah, thats short term... longer term hopefully bodhi does it itself (which we probibly need some bodhi maintainers to do)
15:17:05 <jednorozec> ha
15:17:06 <jednorozec> https://pagure.io/fedora-infra/toddlers/blob/main/f/toddlers/plugins/pdc_update_critpath.py
15:17:57 <jednorozec> but we will need to move this to bodhi to get rid of PDC
15:18:03 <jednorozec> eventually
15:19:42 <jednorozec> left comment there
15:21:27 <jednorozec> .releng 10141
15:21:28 <zodbot> jednorozec: Issue #10141: Improve the SCM request process to let the current maintainers confirm the EPEL branches. - releng - Pagure.io - https://pagure.io/releng/issue/10141
15:23:01 <jednorozec> so do you think we can close it?
15:23:07 <mboddu> I think we should
15:23:25 * nirik is reading and looking for any action we can actually take.
15:23:25 <mboddu> But I have seen couple of issues with it as it didn't process properly
15:24:41 <nirik> I think this could be punted to the epel sig... if they want to make changes in the workflow we could try and do that... but we don't know if they do, or what.
15:24:59 <nirik> perhaps close and ask them to file a epel ticket if they want to change the workflow?
15:25:15 <nirik> the problem is that none of those fits all cases...
15:25:16 <jednorozec> is there epel tracker?
15:25:25 <nirik> yes. https://pagure.io/epel
15:26:39 <nirik> some people don't want epel branches made of some of there packages (for good reasons). Others are fine with maintaining epel branches if asked, they would prefer to do that over someone asking taking over.
15:27:02 <nirik> just blindly allowing only works for some subset of packages.
15:27:15 <jednorozec> yeah
15:27:44 <jednorozec> I personally don't want to maintain epel packages
15:28:29 <nirik> In the pkgdb days you could request an epel branch and the maintainer had 2 weeks I think to either approve or deny...
15:30:41 <mboddu> I am not sure what is remaining in this ticket? Once the maintainer add a person as a colloborator for epel* branches, they can request the epel branch and fedscm-admin correctly processes them
15:30:55 <jednorozec> mboddu, yes
15:31:05 <nirik> yeah.
15:31:13 <jednorozec> there is nothing, they want to do it differently
15:31:27 <jednorozec> it is closed
15:31:37 <mboddu> Okay
15:31:39 <nirik> I think what was wanted was anyone requesting a epel branch would then be added as collaborator and get the branch... but that really doesn't work globally
15:31:52 <jednorozec> nope
15:31:57 <jednorozec> that is not a good idea
15:32:26 <mboddu> Yeah, that is really bad as it doesn't involve maintainer's concern
15:32:49 <nirik> right. anyhow, lets move on then. :)
15:33:14 <jednorozec> what about this
15:33:16 <jednorozec> .releng 10112\
15:33:16 <zodbot> jednorozec: Error: '10112\\' is not a valid integer.
15:33:19 <jednorozec> .releng 10112
15:33:20 <zodbot> jednorozec: Issue #10112: Fedora Python Classroom Lab: Switch from armhfp to aarch64 - releng - Pagure.io - https://pagure.io/releng/issue/10112
15:35:45 <nirik> so, we fixed the aarch64 one, but did we remove the 32bit arm one?
15:36:58 <jednorozec> nope the armhfp is there
15:38:20 <nirik> so, we should drop it now... ;)
15:38:31 <nirik> then we can close this. Or I guess we can ask?
15:39:06 <jednorozec> so is removing it from arches in fedora-variants.xml enough?
15:39:33 <mboddu> jednorozec: Nope, we need to remove it from fedora.conf as well
15:39:41 <mboddu> And both in f35 and main branches
15:40:31 <jednorozec> ok, post freeze?
15:40:58 <mboddu> But check with churchyard in the ticket before removing it, so ping in the ticket
15:41:00 <nirik> yep
15:41:07 <jednorozec> ack.
15:42:02 <nirik> IMHO we could look at dropping a number of the 32bit images... not all, but many seem like they wouldn't get too much use
15:42:16 <nirik> but thats a side discussion.
15:43:29 <jednorozec> I have to leave earlier today
15:43:56 <jednorozec> mboddu, nirik can one of you take over?
15:44:16 <mboddu> Sure
15:44:20 <nirik> sure
15:44:24 <jednorozec> thanks
15:44:30 * jednorozec off
15:45:26 <nirik> thanks jednorozec!
15:46:10 <mboddu> Thanks jednorozec
15:47:54 <nirik> what else do we have?
15:47:58 <mboddu> .releng 10293
15:47:59 <zodbot> mboddu: Issue #10293: *-bootstrap modules are in F35 compose in spite of Pungi configuration - releng - Pagure.io - https://pagure.io/releng/issue/10293
15:47:59 <nirik> f35 status?
15:48:14 <mboddu> We should check with pungi folks again about this
15:48:29 <mboddu> The config still has filter_modules but its not filtering them out
15:48:59 <nirik> oh... hang on
15:49:59 <nirik> we need to adjust the bodhi pungi config? if those are in modular test?
15:51:01 <mboddu> True, but I think he is mentioning in the f35 compose, we dont have bodhi really working there
15:51:41 <mboddu> I mean, we enabled testing repos for f35 and immediately froze it, so whatever in f35 compose is coming from pungi-fedora configs itself
15:51:50 <nirik> f35-modular-updates-testing is a thing
15:52:21 <mboddu> nirik: Oh, you pushed the updates in f35 modular testing during the freeze?
15:52:52 <nirik> no
15:53:07 <nirik> but it has some content, did we push it before freeze?
15:53:27 <nirik> but it's unclear to me where these modules are... what repo
15:54:14 <mboddu> Huh
15:54:16 * mboddu checking
15:54:58 <nirik> I don't have a f35 box here.
15:56:01 <nirik> and of course since it's a module you cna't just look... it's in the repodata
15:57:16 <mboddu> I am totally confused, I am seeing f35 modular testing compose in updates dir on /mnt/koji/compose/
15:57:46 <mboddu> One from 09/03 and one from 09/06
15:58:20 <mboddu> But on mirrors, they are still empty repos
15:58:22 * mboddu is confused
15:58:36 <nirik> oh, perhaps I did push them then?
15:58:48 <nirik> but yeah, should be synced?
15:59:41 <nirik> ok, yeah, looks like I did push M instead of C. whoops. ;( But I would think modular-testing would be fine to push in freeze? it's like updates-testing no?
16:00:57 <mboddu> Yeah, right
16:01:11 <mboddu> But why didn't it sync is still the question
16:01:26 <nirik> unclear. So, IMHO, lets ask in ticket what repos they are seeing it in?
16:01:39 <mboddu> ack
16:01:43 <nirik> if it's updates-testing, then it's bodhi's pungi config.
16:02:21 <mboddu> Yes
16:02:31 <mboddu> Lets do quick open floor
16:04:33 <nirik> k
16:08:22 <nirik> shall we close?
16:30:43 <mboddu> #endmeeting