16:00:18 #startmeeting RELENG (2023-02-28) 16:00:18 Meeting started Tue Feb 28 16:00:18 2023 UTC. 16:00:18 This meeting is logged and archived in a public location. 16:00:18 The chair is jednorozec. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:18 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:18 The meeting name has been set to 'releng_(2023-02-28)' 16:00:18 #meetingname releng 16:00:18 The meeting name has been set to 'releng' 16:00:18 #chair nirik sharkcz pbrobinson phsmoura dustymabe jednorozec 16:00:18 Current chairs: dustymabe jednorozec nirik pbrobinson phsmoura sharkcz 16:00:18 #topic init process 16:00:26 Hello :) 16:00:38 luna, hello 16:01:09 morning 16:01:55 so I dont have much for today 16:02:29 I have lost membership in fedora-infra group on pagure 16:02:39 so I cannot merge the docs PR :/ 16:02:53 ? weird 16:02:54 I can re-add you. 16:03:17 yeah weird thing is that I can see only 3 groups in my profile https://pagure.io/user/humaton/groups 16:03:35 there is much more here https://fasjson.fedoraproject.org/v1/users/humaton/groups/ 16:03:48 logout/login to pagure does not help :/ 16:03:57 there's not any sync there 16:04:03 oh 16:04:07 fas only creates the account. 16:04:11 pagure.io has it's own groups. ;) 16:04:55 added you there. no idea why you weren't added a long time ago. ;) 16:05:06 thanks 16:05:17 I had a few things today. Docs was one. 16:05:49 yeah here is the pr: https://pagure.io/infra-docs-fpo/pull-request/179 16:06:16 it reflects https://pagure.io/releng/issue/11192 16:06:24 and https://pagure.io/releng/issue/11188 16:06:45 there are 2 more docs issues that are tagged https://pagure.io/releng/issues?tags=docs&status=Open 16:08:17 I think there's lots still to update/fix, but we should merge it and go from there. 16:08:22 Do I have to do something or will the docs page be autogenerated from the source? 16:08:34 the PR is merged 16:09:16 It should build from there I think... 16:09:29 there's more tickets we should carefully check against docs and close... 16:10:22 https://pagure.io/releng/issue/10838 16:10:51 yes that one I a currently looking at 16:11:01 https://pagure.io/releng/issue/10376 16:11:51 https://pagure.io/releng/issue/8950 perhaps 16:12:26 tagging both with docs so we have them all in one list 16:13:17 Probibly others, but I don't see any off hand. 16:13:34 if you see any can you add docs tag to them? 16:13:48 I will be checking https://pagure.io/releng/issues?tags=docs&status=Open 16:13:52 We should go over the branching docs soon and correct anything from the issues we hit this time. ;) 16:13:55 sure. 16:14:01 to process the changes and make them into the new docs 16:15:05 sounds good. 16:15:41 once the new docs is live I will close those 2 or 3 already addressed 16:16:04 +1 16:16:45 oh I just noticed there is stable push request 16:17:14 I just got up, so hadn't see it yet. ;) 16:17:30 for what package? or something else 16:17:35 I wanted to menttion https://pagure.io/releng/pull-request/11180 (and pr's in general) 16:17:54 (if we are done with docs) 16:18:33 oh, the pagure notifications 16:18:48 somehow they all endup in spam in the gmail :/ 16:19:28 :( stupid gmail. You can re-train it I think... 16:20:24 * jednorozec tried and got tired 16:20:26 Also: you can I think add a address book entry for the sender, and google will not mark it as spam anymore. 16:20:33 oh 16:20:36 that might work! 16:21:11 luna: https://pagure.io/releng/issue/11306#comment-843737 16:21:40 nirik, cool thanks 16:21:51 anyhow. Can you look at running that script from that PR and if it works/looks ok, add it to nightly.sh? or would you like me to do so? 16:22:26 and in general, we should go thru all our PRs and merge or drop or comment at least. 16:22:45 nirik, I am looking at the script 16:23:10 this should be executed after the compose I presume? 16:23:15 doesn't have to be right now. Just want to know if you or I are doing it. ;) 16:23:45 yeah. 16:24:03 we need to make this part of the docs aswell 16:24:11 there are f-versioned variables 16:24:30 * nirik nods. yeah 16:24:55 ok so lets go through the PRs we have in releng repos 16:25:14 and I will add this script to the docs and open PR for pungi-fedora 16:25:27 Sounds good. Oldest to newest? 16:25:33 +1 16:26:02 https://pagure.io/releng/pull-request/8820 16:26:14 old pr for mods to the module mass rebuild script. 16:26:25 yeah and it does simplify things 16:26:34 seems ok to me if it still applies? merge? 16:26:57 (and side note, did we ever do the modules mass rebuild? ;) 16:27:04 yes we did 16:27:18 it was extra quick something like 20-30 modules 16:27:23 cool. Its a blur. ;) 16:28:05 ok, that PR has conflicts it seems now. 16:28:38 well, it doesn't rebase 16:29:15 https://pagure.io/releng/pull-request/10811 also has conflicts, but cverna is still around, so let me ask him to fix. 16:29:22 so 16:29:35 I pulled the patch from 8820 am it and pushed it 16:30:18 https://pagure.io/releng/pull-request/10951 also conflicts and there's questions for me I missed. Will answer and ask for rebase 16:31:28 now on to https://pagure.io/releng/pull-request/11129 16:32:03 I asked some questions there with no reply. will ask for reply 16:32:33 https://pagure.io/releng/pull-request/11207 16:32:46 oh 16:32:51 I think thats ready to merge? 16:32:51 I can close that one 16:33:09 ok. great. 16:33:31 https://pagure.io/releng/pull-request/11246 - mass-tag.py: Use rpm vercmp for determining what to tag over 16:33:52 I think thats probibly ok to merge? unless you have reservations on it. 16:34:28 * jednorozec clicks on rebase 16:35:48 https://pagure.io/releng/pull-request/11272 - mail-templates: adjust text about git 16:36:01 I was kinda waiting for this to die down/have all the comments before merging. 16:36:04 we can wait on it I think. 16:36:20 or perhaps it's all done and we should merge? 16:36:40 so last comment is from a week ago 16:37:01 how about I ask... 16:37:02 it seems everything reviewers wanted got in 16:37:23 https://pagure.io/releng/pull-request/11293 16:37:31 [WIP] Add script for checking if retired packages appear active in pdc 16:38:17 yeah i told lenka to open this 16:38:28 I think we should merge the pr and then file a new ticket to deal with those 2 packages it found? 16:38:51 there are issues after branching and/or massrebuild with packages that are retired but branches are created or builds attempted 16:39:06 ack 16:39:17 oh, they were fixed? 16:39:31 so 16:39:40 it really depends when one runs such script 16:39:40 so, merge? 16:39:45 yes merge 16:39:49 its rebased 16:39:55 yeah. 16:40:11 you want to merge? or want me to? 16:40:21 if the script is ran after somebody retired package but the automation dint finish it it can show up 16:40:34 merged 16:40:45 right. 16:41:47 cool. thats it on those. 16:43:10 I had just one other thing: Can we get prepped for RC1 soon? If you like I can submit a pr and you review, or the other way around. Would be nice to be ready for it whenever it comes. 16:43:30 I can do that 16:45:20 excellent. 16:45:53 so i have 2 action items so far, add the ostree base containers script and create RC pr 16:46:21 +1 16:46:39 * nirik tries to think if he had anything else... 16:47:39 next time we should perhaps go thru tickets... starting with oldest first... 16:48:48 yeah 16:49:02 we can start closing changes that are for sure complete 16:49:36 sounds like a plan 16:49:40 Yep. I'm sure there's old things we can close or at least move forward. 16:52:22 I don't think I have anything more today. 16:52:26 so I have one more thing 16:52:33 to change this: https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming 16:52:42 Did you want to do the stable pushes jednorozec? or want me to? 16:52:43 do we need ack from packaging people or someone? 16:53:07 oh I am on bodhi-backend 16:53:09 let me push it 16:53:34 just file a PR against that repo... there's someone who is pretty active in merging/finding things. 16:53:54 https://pagure.io/fedora-docs/package-maintainer-docs/pull-requests 16:54:01 what did you want to change? 16:54:33 so 16:54:54 I would like to change it so people will open tickets to the scm-request repo 16:55:18 and add fedpkg unretire, that will check for some initial checks and post the ticket to the tracker 16:55:35 so all scm related stuff will be in one tracker 16:55:47 and it will get automated from there 16:57:09 oh nice 16:57:17 its best to get all the rest in place before updating the doc of course. 16:57:24 for suure 16:57:52 and we should discuss sometime automating the flatpak and compat requests. 16:58:02 yup 16:58:11 for flatpak I guess we could just use the flatpak sig group... 16:58:25 compat is harder. But it would help if fedpkg provided more info 16:58:40 right now it's just the name of the package and that they want to skip validation. 16:59:01 if it provided a reason and the base package it was compat for, we might be able to do something. 17:00:32 and we are at time 17:00:38 yeah 17:00:39 perhaps you could look at that while looking at retire? 17:00:46 but we are out of time. 17:00:47 yeah. ;) 17:00:50 I can do that 17:00:57 * jednorozec adds note 17:01:02 #nedmeeting 17:01:07 #endmeeting