15:00:20 <jednorozec> #startmeeting RELENG (2023-04-25)
15:00:20 <zodbot> Meeting started Tue Apr 25 15:00:20 2023 UTC.
15:00:20 <zodbot> This meeting is logged and archived in a public location.
15:00:20 <zodbot> The chair is jednorozec. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:00:20 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:20 <zodbot> The meeting name has been set to 'releng_(2023-04-25)'
15:00:20 <jednorozec> #meetingname releng
15:00:20 <zodbot> The meeting name has been set to 'releng'
15:00:20 <jednorozec> #chair nirik sharkcz pbrobinson phsmoura dustymabe jednorozec
15:00:20 <zodbot> Current chairs: dustymabe jednorozec nirik pbrobinson phsmoura sharkcz
15:00:20 <jednorozec> #topic init process
15:01:27 <jnsamyak> hi folks 0/
15:01:28 <nirik> morning
15:01:33 <phsmoura> morning
15:01:40 <luna_> afternoon
15:02:08 <jednorozec> hello everyone
15:03:12 <jednorozec> I have just few things for today
15:03:28 <jednorozec> sooo
15:03:35 <jednorozec> .releng 11399
15:03:36 <zodbot> jednorozec: Issue #11399: Add container/fedora-toolbox as a Fedora Linux 39 release-blocking deliverable - releng - Pagure.io - https://pagure.io/releng/issue/11399
15:03:53 <jednorozec> what do we need to do to make the artifact release blocking?
15:04:42 <jednorozec> oh there are some comments I have missed
15:04:46 * jednorozec reads
15:05:28 <nirik> well, if we don't build it as part of a compose... there's nothing we can do really.
15:06:21 <nirik> we could definitely help at branching, but... that has nothing to do with it being release blocking I don't think.
15:06:29 <jednorozec> yeah
15:06:38 <jednorozec> I am reading the comment from rishi
15:06:57 <nirik> It could be that we can make pungi make it... ie, it just gets made as part of compose.
15:06:58 <jednorozec> so they just need to run containerbuild after the branching
15:07:05 <nirik> but that will need some investigation
15:07:19 <nirik> well, and at rc's...
15:07:57 <jednorozec> yeah I am not in favor running thing manually
15:08:24 <jednorozec> we are working on getting thing automated so adding new manual tasks seems weird...
15:08:32 <jednorozec> *things
15:09:11 <nirik> yeah.
15:09:23 <nirik> so, perhaps we should look at what it would take to do them as part of pungi runs...
15:09:44 * jednorozec writes comment and assign it to me
15:10:30 <nirik> it might be weird if we do that and then maintainers also manually make it... but probibly won't be too much of a problem
15:12:33 <jednorozec> ok moving on
15:12:39 <jednorozec> .releng 11388
15:12:40 <zodbot> jednorozec: Issue #11388: Files not removed when retiring due to blocking of git repo before the final push - releng - Pagure.io - https://pagure.io/releng/issue/11388
15:12:47 <jednorozec> close upstream?
15:13:55 <nirik> we needed to fix the broken repo/package first I think?
15:14:20 <nirik> ust delete the rest and dead.package it?
15:14:55 <jednorozec> well, they didnt actually retired it
15:14:57 <nirik> ah it seems to be
15:15:09 <jednorozec> yeah you can --skip-checks
15:15:14 <jednorozec> and it will do the right thing
15:16:11 <nirik> ok, can you do that, or you want me to?
15:16:16 <nirik> then we should close it after that. ;)
15:16:22 <jednorozec> done
15:16:26 <jednorozec> and closed
15:17:03 <jednorozec> .releng 11156
15:17:04 <zodbot> jednorozec: Issue #11156: rubygem-kgio in weird zombie state - releng - Pagure.io - https://pagure.io/releng/issue/11156
15:17:07 <jednorozec> so this is weird
15:17:21 <jednorozec> there is a few packages in this weird state
15:17:37 <jednorozec> where they get branched but are supposed to be retired
15:18:16 <jednorozec> and the branch staid there without any attention because original maintainer thinks its retired
15:18:26 <nirik> yeah, we need to detect them and fix them
15:18:50 <nirik> yeah, it has a dead.package... but... not the rest
15:20:43 <jednorozec> I dont understand why do they get branched in first place
15:20:57 <jednorozec> the script ignores retired packages
15:22:17 <nirik> well, it's not blocked... or orphaned... how does it tell it's retired?
15:23:30 <jednorozec> the thing is it was retired, it had orphan as maintainer
15:23:52 <jednorozec> but suddenly there is package owner changed for rubygem-boxgrinder-build in module-package-list by bodhi
15:23:52 <jednorozec> owner.name: orphan -> releng
15:23:56 <nirik> huh, doesn't seem to now... https://src.fedoraproject.org/rpms/xorg-x11-drv-fbturbo/
15:24:02 <jednorozec> or similar owner change that I cannot explain
15:24:56 <jnsamyak> nirik: I think this is the one: https://src.fedoraproject.org/rpms/rubygem-kgio/blob/rawhide/f/dead.package
15:25:33 <nirik> wait, are we talking about 2 different tickets here?
15:25:47 <jednorozec> right
15:25:48 <nirik> h yeah, I am looking at the wrong one. ;)
15:25:48 <jednorozec> :)
15:25:49 <jednorozec> we are
15:25:49 <luna_> it changed
15:26:28 <nirik> so, bodhi is doing that somehow
15:26:49 <nirik> Wed Apr 19 10:30:34 2023 package owner changed for rubygem-boxgrinder-build in module-package-list by bodhi
15:26:49 <nirik> owner.name: orphan -> releng
15:26:49 <nirik> Thu Apr 20 10:32:06 2023 package owner changed for rubygem-boxgrinder-build in module-package-list by bodhi
15:26:49 <nirik> owner.name: releng -> orphan
15:27:29 <jednorozec> yeah and on some packages it just added releng
15:28:35 <nirik> was that branching day?
15:28:41 <nirik> no. hum
15:29:46 <jednorozec> nope
15:30:15 <jednorozec> I checked the original reported package and some of the changes are at randnom dates
15:30:28 <nirik> so... it has to be the koji sync listener. somehow
15:30:28 <jednorozec> some are relevant to branching or mass rebuild
15:32:56 <nirik> ah ha
15:33:07 <nirik> it is koji sync listener
15:33:20 <jednorozec> what part of it?
15:33:43 <nirik> https://pagure.io/releng/issue/6663 is referred to in a comment
15:34:06 <nirik> basically it's syncing rawhide/rpms package list with module-package-list for mbs
15:34:22 <nirik> but it must somehow not be seeing some things as retired when they are.
15:34:39 <jednorozec> at least we have a suspect
15:34:44 <nirik> roles/bodhi2/backend/templates/owner-sync-pagure.j2 is the script
15:34:52 <nirik> yeah, I think it's this, but I am not sure why...
15:35:22 <jednorozec> my guess off by one in some cycle
15:35:37 <nirik> could well be. needs more investigation.
15:35:45 <jednorozec> anyhow we can update the ticket
15:35:47 <nirik> and I'm low on coffee right now. ;)
15:36:06 <jednorozec> go get some :)
15:36:17 <jednorozec> or actually I dont have anything else
15:36:22 <jednorozec> so
15:36:29 <luna_> also don't have anything else
15:36:32 <jednorozec> #topic open floor
15:36:41 * luna_ does not have anything else today
15:36:41 <nirik> I'm not sure I had anything this week... lets see... oh, one thing
15:37:42 <nirik> So, I am doing a prod->staging koji sync right now... it's taking a long time, but I wanted it working so I could test some things in staging. Then, likely later this week I will roll out to prod probibly. And soon we need to upgrade builders to f38, but if we just upgrade that should not be too hard.
15:38:38 <nirik> thats all I had.
15:38:47 <luna_> sounds good
15:38:52 <jednorozec> I can do some of the updates in EU mornings
15:39:08 <jednorozec> there seems to be less trafic at CET mornings
15:39:46 <nirik> sure, we can coordinate. It can be next week or something, not urgent
15:41:44 <jednorozec> ok
15:41:59 <jednorozec> thank for coming.
15:42:02 <jednorozec> #endmeeting