16:00:13 #startmeeting RELENG (2021-11-09) 16:00:13 Meeting started Tue Nov 9 16:00:13 2021 UTC. 16:00:13 This meeting is logged and archived in a public location. 16:00:13 The chair is jednorozec. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:13 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:13 The meeting name has been set to 'releng_(2021-11-09)' 16:00:13 #meetingname releng 16:00:13 The meeting name has been set to 'releng' 16:00:13 #chair nirik sharkcz pbrobinson pingou mboddu dustymabe ksinny jednorozec 16:00:13 #topic init process 16:00:13 Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou sharkcz 16:00:29 morning 16:00:51 morning 16:01:25 Morning everyone 16:01:39 morning 16:01:47 hm 16:02:13 where is this humaton[m] running? I have no client running and no tab in browser :/ 16:02:46 jednorozec: matrix is persistent, you don't need to be connected to it. 16:03:14 hm 16:03:26 so people think they are writing me when they are not? 16:03:36 possibly yeah. 16:04:27 thanks for clarification nirik 16:04:48 I had a phantom one for a while too. ;) 16:05:26 so first things first 16:05:29 nirik++ 16:05:29 jednorozec: Karma for kevin changed to 4 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:05:32 mboddu++ 16:05:32 jednorozec: Karma for mohanboddu changed to 3 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:05:40 ha. cookie party. Love it. 16:05:44 jednorozec++ 16:05:44 nirik: Karma for humaton changed to 1 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:05:47 thanks for the clean up yesterday 16:05:48 mboddu++ 16:05:48 nirik: Karma for mohanboddu changed to 4 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:06:22 mboddu++ 16:06:23 pmoura: Karma for mohanboddu changed to 5 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:06:29 nirik++ 16:06:29 pmoura: Karma for kevin changed to 5 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:06:30 pmoura++ 16:06:31 jednorozec: Karma for phsmoura changed to 1 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:07:03 sooo 16:07:04 pmoura++ 16:07:04 nirik: Karma for phsmoura changed to 2 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:07:10 serious stuff 16:07:14 .releng 10376 16:07:15 jednorozec: Issue #10376: Add procedure for updating comps to branch process - releng - Pagure.io - https://pagure.io/releng/issue/10376 16:07:19 nom nom nom 16:07:26 jednorozec++ pmoura++ nirik++ 16:07:26 mboddu: Karma for humaton changed to 2 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:07:29 mboddu: Karma for phsmoura changed to 3 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:07:37 ha! you can do that? 16:08:05 anyhow that ticket 16:08:22 It seems like good candidate for toddler 16:08:51 hum. 16:09:40 I wonder if we couldn't do it sooner... have the thing that retires packages look and see if the to be retired package has any subpackages in comps and then yell? 16:10:18 Also, yell at who/where? 16:10:29 right 16:10:52 At the maintainer who is retiring the package? 16:10:54 I guess a releng ticket? 16:11:18 well, that could get say churchyard when doing the FTBFS retirements or whatever... 16:11:48 Okay, then create a toddler to listen to retirement messages and create a releng ticket? 16:11:58 that was my idea mboddu 16:12:05 yeah, I guess that could work. 16:12:14 but only if the package is in comps or a subpackage from it. 16:12:20 jednorozec: Okay, great 16:12:29 nirik: Right, not for every retirement 16:12:52 But we also need an intial clean up as well 16:13:15 * nirik nods 16:14:25 ok, so listening to the retirement message, running the check-missing script and filing releng ticket if it script fails. 16:14:44 So, we need to do look at the packages and subpackages in comps file, do `dnf whatprovides $pkg` and if nothing returns, clean up the package? 16:15:04 mboddu, there is this https://pagure.io/fedora-comps/blob/main/f/check-missing 16:15:44 also adamw had some scripts he mentioned on the devel list. 16:15:55 Yeah, that would work 16:15:58 that is the script i think 16:16:02 also, we only care abotu active releases. 16:17:20 +1 16:17:26 ok I will summarize it in a comment 16:17:30 ack 16:20:48 so the cleanup they mention is a manual thing it seems 16:22:32 ok 16:22:34 next one 16:22:36 there's also a bunch of old pr's. I was gonna close / ping and close a bunch of them this week 16:22:43 (on fedora-comps that is) 16:22:55 Yeha I have it opened in tab here 16:23:04 .releng 10369 16:23:05 jednorozec: Issue #10369: Q: Why do we install epel-release and fedpkg-minimal into every buildroot in Koji? - releng - Pagure.io - https://pagure.io/releng/issue/10369 16:23:31 * nirik has not had any time to look into this. 16:24:57 I suspect we don't need them, but they are really quite small. 16:25:39 fedpkg-minimal is required though for dist-git cloning and stuff, right? 16:25:46 for srpm builds yes. 16:25:59 but not for the main build after that 16:26:12 they are two different koji groups. 16:26:13 Yeah, we need it in srpm-build group 16:26:55 koji list-groups epel8-build 16:27:04 yep, but not build 16:27:17 Right 16:27:37 epel-release can be removed, as the dist-tag is coming from redhat-release 16:27:38 (probibly) 16:28:03 we should test in stg... I was thinking of doing a prod->stg sync this week 16:28:49 Okay, once the sync is done, we can test removing epel-release from both groups and fedpkg-minimal from *build* group only 16:30:10 my guess to the answer to #10369 is "because smooge didn't know you could apply them to just srpm-build :)" 16:31:39 well, it's that way in epel7 too, so probibly just cargo culted from fedora (where it is needed) 16:32:00 and even epel6 16:32:00 SSmoogen[m]: I did the epel8 tagging and groups, and ^ is what happened 16:32:26 I know about it but didn't quite really check it/remember it 16:33:01 I don't know that the savings is worth even the amount of discussion we have had. ;) 16:33:02 ah cmon guys I am giving you the perfect out here.. 🤪 16:33:38 oh its like most things, all irc/email discussions always outway build savings 16:33:45 Thats so nice of you SSmoogen[m] but, it is my mistake 16:35:41 I will have to run to close the animals. 16:35:52 Can one of you take over? nirik mboddu ? 16:36:02 I need to prep for outage starting at the top of the hour. ;) 16:36:02 Sure, I can take over 16:36:23 thanks! 16:39:35 #topic #10263 A module stream request should add the stream value as a version to Bugzilla 16:39:41 #link https://pagure.io/releng/issue/10263 16:40:37 I never touched bz api other than filing tickets and stuff, but is it possible to create a toddler for this? Esp is it possible in bz api to do something like this? 16:41:17 As in, the toddler will check for new repos/ branches in module name space and create the versions in bz? 16:41:40 I supopse it's possible yeah... could just be a modification of the existing one that creates new components. 16:41:54 Yeah, we could update that one too 16:43:32 Where is that script nirik ? 16:45:41 it's in the toddlers project I think? 16:45:55 https://pagure.io/fedora-infra/toddlers 16:46:01 I couldn't find it in toddlers 16:46:16 huh, ok. I thought it was there, would have to dig around 16:46:47 Okay 16:48:15 #topic #10177 epel-release-latest-8.noarch.rpm 403 forbidden 16:48:24 #link https://pagure.io/releng/issue/10177 16:48:42 I thought pmoura was here 16:48:59 must have dropped out. 16:49:05 Yeah, seems like it 16:49:21 He said he will have a script fix ready for this 16:49:28 ^ today 16:49:36 Anyway, moving on 16:49:41 #topic Open Floor 16:49:50 Anybody has anything to share 16:50:02 I am looking at updating compose-tracker to track ELN composes 16:51:33 buildsystem outage starts in about 10min. ;) 16:53:16 Let me know if you need any help 16:53:53 will do. My plan is move s390x first, then koji update (should just be packages and one small schema update) and then see about updating/rebooting things. 16:54:03 may need help on the last. 16:54:10 Okay 16:54:36 nirik: Side topic, what routers do you use at your place? 16:55:15 * mboddu needs an upgrade and wondering if anyone has used asus aimesh with wifi6 (preferably running merlin wrt) 16:55:27 for wifi? 16:55:31 Yup 16:55:46 I have been using a trusty turris omnia... but wanting to play with wifi6 I recently got a new one... 16:56:32 https://openwrt.org/toh/linksys/e8450 16:56:36 linksys e8450 16:56:51 (which I promptly flashed for openwrt) 16:57:48 Yeah, I had linksys running ddwrt (I prefer a webui for management) but apparently repeater bridge dont wont on both bands 16:58:03 s/wont/work/ 16:58:25 So, I have to either use 2.4 or 5ghz for repeater bridge 16:58:34 But not both :( 16:59:52 Anyway, we are about time 16:59:59 Have fun nirik with the upgrades 17:00:08 Thanks everyone for joining 17:00:10 #endmeeting