<@patrikp:matrix.org>
15:00:01
!startmeeting RELENG (2025-04-28)
<@meetbot:fedora.im>
15:00:05
Meeting started at 2025-04-28 15:00:01 UTC
<@meetbot:fedora.im>
15:00:05
The Meeting name is 'RELENG (2025-04-28)'
<@patrikp:matrix.org>
15:00:11
!meetingname releng
<@patrikp:matrix.org>
15:00:11
!info Agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw.
<@patrikp:matrix.org>
15:00:11
!info Meeting is 60 minutes MAX. At the end of 60, it stops.
<@patrikp:matrix.org>
15:00:11
!chair nirik jnsamyak patrikp amedvede
<@meetbot:fedora.im>
15:00:12
The Meeting Name is now releng
<@patrikp:matrix.org>
15:00:36
Hello to all. 👋
<@jnsamyak:matrix.org>
15:03:52
Hey I’m here in and out but will be fully here in 15 at dinner currently
<@patrikp:matrix.org>
15:04:26
Sure, we're waiting for Kevin anyway. Chew properly and don't rush it.
<@jnsamyak:matrix.org>
15:04:28
It was Anton turn, he pinged me to assign the next meeting to him fyi^
<@jnsamyak:matrix.org>
15:04:44
Hehehe leftovers
<@jnsamyak:matrix.org>
15:05:01
I should take you to a Indian place when I’m in the city
<@patrikp:matrix.org>
15:05:25
I'll order something "mildly" spicy.
<@jnsamyak:matrix.org>
15:06:19
What’s the spiciest food you’ve ever eaten?
<@patrikp:matrix.org>
15:07:25
A small piece of a triniad moruga scorpion pepper. Very small piece.
<@nirik:matrix.scrye.com>
15:07:45
morning
<@nirik:matrix.scrye.com>
15:08:30
the hotest food I ever had was a thai dish... can't remember the name now, but wow...
<@patrikp:matrix.org>
15:10:16
Let's go to init?
<@patrikp:matrix.org>
15:10:24
Do we have anything for the init? Any blockers/tasks/issues/requests/features that need releng intervention?
<@patrikp:matrix.org>
15:10:24
!topic Init process.
<@patrikp:matrix.org>
15:11:09
I have one thing about OpenH264. We received no reply from Cisco as of today. How can we contact them?
<@nirik:matrix.scrye.com>
15:12:03
so there was a second email? or no? (I don't think I saw anything but perhaps I wasn't cced?)
<@patrikp:matrix.org>
15:12:49
Title: Fedora Project OpenH264 Distribution Workflow
<@patrikp:matrix.org>
15:12:49
There was a second e-mail on April 7th and I see you in the cc.
<@nirik:matrix.scrye.com>
15:13:08
also, there was a list cc'ed on that? are there any public archives of that list? or it's private?
<@patrikp:matrix.org>
15:13:37
I think private.
<@patrikp:matrix.org>
15:13:48
Or at least I don't know of an archive.
<@nirik:matrix.scrye.com>
15:14:17
ok, was hoping we could see if there's any activity there.
<@jnsamyak:matrix.org>
15:14:21
I have a manager at Cisco that’s known should I reach out to them and ask this to swing internally
<@patrikp:matrix.org>
15:14:22
Can you be reached through that address as well?
<@patrikp:matrix.org>
15:14:22
cc: Kevin Fenzi <kevin@scrye.com>
<@nirik:matrix.scrye.com>
15:14:42
yes
<@jnsamyak:matrix.org>
15:14:45
Not sure if it’s breach of privacy etc
<@nirik:matrix.scrye.com>
15:14:48
jnsamyak: that sounds good!
<@patrikp:matrix.org>
15:15:05
Do you see it in your inbox? April 7th.
<@nirik:matrix.scrye.com>
15:15:08
just ask them to bring some reply/attention to the emails?
<@jnsamyak:matrix.org>
15:15:20
Okay then I’ll reach out tomorrow
<@nirik:matrix.scrye.com>
15:15:21
yeah, I saw the initial one. I thought we were going to resend it a second time
<@patrikp:matrix.org>
15:15:28
Yes, we just need someone to point us in the right direction, that'd be great.
<@patrikp:matrix.org>
15:15:54
It was only sent once to the mailing list.
<@nirik:matrix.scrye.com>
15:16:24
ok, so I'd say lets wait and see if jnsamyak's contact gets anywhere. If not, later this week we should resend that email...
<@patrikp:matrix.org>
15:16:39
Anything else for the init?
<@patrikp:matrix.org>
15:17:57
!topic Scheduled actions coming up in the next week.
<@patrikp:matrix.org>
15:17:57
!info Here we list/discuss anything about items that are due to be done in the next week.
<@patrikp:matrix.org>
15:17:57
<@patrikp:matrix.org>
15:17:57
<@patrikp:matrix.org>
15:19:05
"Update PDC with F40 EOL date"
<@patrikp:matrix.org>
15:19:05
I see in the F42 schedule:
<@patrikp:matrix.org>
15:19:05
But... I thought PDC was dead? Or not completely dead?
<@patrikp:matrix.org>
15:19:37
More of a out of curiosity question.
<@nirik:matrix.scrye.com>
15:19:49
it's 100% dead.
<@nirik:matrix.scrye.com>
15:19:56
we should remove any mentions of it. ;)
<@smooge:fedora.im>
15:20:13
🧟
<@patrikp:matrix.org>
15:20:27
Where are the schedule contents defined?
<@jnsamyak:matrix.org>
15:20:48
Okay I mailed my Cisco guy
<@nirik:matrix.scrye.com>
15:21:51
There's some repo where they are, but I am not sure what it is off hand.
<@jnsamyak:matrix.org>
15:21:52
Tell Aoife - she will remove it
<@patrikp:matrix.org>
15:22:24
I will ping Aoife.
<@patrikp:matrix.org>
15:24:11
OK, I pinged her, she will know more.
<@patrikp:matrix.org>
15:26:03
Aoife said she'll clean it up from F43 onward. 👍️
<@patrikp:matrix.org>
15:26:41
Apart from that I don't really see anything for the next week in terms of upcoming releng things.
<@patrikp:matrix.org>
15:27:32
For reference, here is the repo where issues should be opened in case there are issues with the schedule.
<@patrikp:matrix.org>
15:27:36
<@jnsamyak:matrix.org>
15:32:26
Post release cleanup is almost done ! :3
<@nirik:matrix.scrye.com>
15:33:05
👍
<@patrikp:matrix.org>
15:36:33
Yeah, and I have the things noted down, just need to format it better and I can open a pull request with the SOP update.
<@nirik:matrix.scrye.com>
15:37:28
great to update things as we find them... otherwise it's hard to remember what was wrong. ;)
<@patrikp:matrix.org>
15:38:55
My keyboard betrayed me in the meantime, had to switch to a cheap membrane one until I fix it.
<@patrikp:matrix.org>
15:39:10
It's not a pleasant typing experience.
<@patrikp:matrix.org>
15:39:10
Next section?
<@jnsamyak:matrix.org>
15:39:13
lol
<@patrikp:matrix.org>
15:39:31
I think the cable that connects the two halves is just done.
<@patrikp:matrix.org>
15:39:52
Only right half stopped working. And I was suspicious of the cable before.
<@patrikp:matrix.org>
15:40:02
!topic Tickets that need attention.
<@patrikp:matrix.org>
15:40:02
!info This is the time where you can bring up releng tickets to discuss if there are blockers, etc.
<@patrikp:matrix.org>
15:40:02
<@patrikp:matrix.org>
15:40:41
There's a new private ticket.
<@nirik:matrix.scrye.com>
15:42:09
I'm not sure it needs to be... but ok.
<@nirik:matrix.scrye.com>
15:43:31
I'm not organized this morning to have specific tickets I don't think...
<@patrikp:matrix.org>
15:43:54
You can also get more than 15 minutes of your time back.
<@nirik:matrix.scrye.com>
15:44:04
well, actually... I do have some marked in my mail client
<@nirik:matrix.scrye.com>
15:44:42
!releng 12490
<@zodbot:fedora.im>
15:44:43
● **Last Updated:** 3 days ago
<@zodbot:fedora.im>
15:44:43
<@zodbot:fedora.im>
15:44:43
● **Opened:** 4 months ago by petersen
<@zodbot:fedora.im>
15:44:43
● **Assignee:** Not Assigned
<@zodbot:fedora.im>
15:44:43
**releng #12490** (https://pagure.io/releng/issue/12490):**10 builds still koji tagged with signing-pending**
<@nirik:matrix.scrye.com>
15:45:09
shall we just untag those last ones and close it?
<@jnsamyak:matrix.org>
15:45:25
I had one but I can’t recall which one was it
<@patrikp:matrix.org>
15:45:43
+1
<@nirik:matrix.scrye.com>
15:45:46
well, except...
<@nirik:matrix.scrye.com>
15:46:02
thats a racy query. Packages are tagged in and processed and untagged.
<@nirik:matrix.scrye.com>
15:46:11
at any given time there will be some being signed in there
<@nirik:matrix.scrye.com>
15:46:41
but those seem 'stuck'.
<@nirik:matrix.scrye.com>
15:47:05
Instead of untagging them, we should try re-tagging them... that should make robosignatory process them again.
<@nirik:matrix.scrye.com>
15:47:37
does someone want to do that? :) I mean I could, but you all could too.
<@patrikp:matrix.org>
15:48:12
I can take it. And re-tag them into which tag?
<@nirik:matrix.scrye.com>
15:48:34
the ones they are in now.
<@nirik:matrix.scrye.com>
15:48:59
the reason they are likely stuck is that something happened and robosignatory didn't get the message they needed to be processed.
<@patrikp:matrix.org>
15:49:01
I know I asked about this before, but "re-tagging" is untagging and tagging again?
<@nirik:matrix.scrye.com>
15:49:05
retagging them in would cause it to do so
<@nirik:matrix.scrye.com>
15:49:17
you can untag and tag or you can tag with --force
<@nirik:matrix.scrye.com>
15:49:52
thanks for taking it. ;)
<@nirik:matrix.scrye.com>
15:49:58
!releng 12023
<@zodbot:fedora.im>
15:49:59
● **Opened:** a year ago by kevin
<@zodbot:fedora.im>
15:49:59
● **Assignee:** patrikp
<@zodbot:fedora.im>
15:49:59
● **Last Updated:** 3 days ago
<@zodbot:fedora.im>
15:49:59
<@zodbot:fedora.im>
15:49:59
**releng #12023** (https://pagure.io/releng/issue/12023):**Update pungi filters**
<@patrikp:matrix.org>
15:50:01
Is there a practical difference between the two that one should consider?
<@nirik:matrix.scrye.com>
15:50:12
I don't think there is...
<@nirik:matrix.scrye.com>
15:51:24
so, on this last one, it sounds like we should add glibc32 to the bodhi pungi config in ansible.
<@nirik:matrix.scrye.com>
15:52:09
and on the rawhide one we need to test dropping those old server ones.
<@jnsamyak:matrix.org>
15:52:24
I thought we did it
<@patrikp:matrix.org>
15:52:34
Just so I am wiser, could you please explain to me some of the context around why, what problems it may cause, etc.? I have literally no idea. But if you say to add it in I can do that.
<@jnsamyak:matrix.org>
15:53:02
Good question
<@nirik:matrix.scrye.com>
15:53:23
glibc32 is a weird 32bit glibc on x86_64... it's normally only used to build other glibc stuff, it shouldn't be shipped to users. We filter it in rawhide/branched... but not in updates(yet)
<@nirik:matrix.scrye.com>
15:54:27
: package) to access the 32-bit development files during a 64-bit build.
<@nirik:matrix.scrye.com>
15:54:27
: build environment. Any package which needs both 32-bit and 64-bit
<@nirik:matrix.scrye.com>
15:54:27
: This package is not supported or intended for use outside of the
<@nirik:matrix.scrye.com>
15:54:27
: distribution build enviroment. Regular users can install both 32-bit and
<@nirik:matrix.scrye.com>
15:54:27
: 64-bit runtimes and development files without any problems.
<@nirik:matrix.scrye.com>
15:54:27
``` Description : This package is only used for internal building of multilib aware
<@nirik:matrix.scrye.com>
15:54:27
: packages, like gcc, due to a technical limitation in the distribution
<@nirik:matrix.scrye.com>
15:54:27
:
<@nirik:matrix.scrye.com>
15:54:27
: runtimes at the same time must install glibc32 (marked as a 64-bit
<@nirik:matrix.scrye.com>
15:54:33
` Description : This package is only used for internal building of multilib aware
<@nirik:matrix.scrye.com>
15:54:33
: package) to access the 32-bit development files during a 64-bit build.
<@nirik:matrix.scrye.com>
15:54:33
:
<@nirik:matrix.scrye.com>
15:54:33
: This package is not supported or intended for use outside of the
<@nirik:matrix.scrye.com>
15:54:33
: distribution build enviroment. Regular users can install both 32-bit and
<@nirik:matrix.scrye.com>
15:54:33
: 64-bit runtimes and development files without any problems.
<@nirik:matrix.scrye.com>
15:54:33
: runtimes at the same time must install glibc32 (marked as a 64-bit
<@nirik:matrix.scrye.com>
15:54:33
: build environment. Any package which needs both 32-bit and 64-bit
<@nirik:matrix.scrye.com>
15:54:33
: packages, like gcc, due to a technical limitation in the distribution
<@patrikp:matrix.org>
15:54:40
I don't understand what testing is in this context.
<@patrikp:matrix.org>
15:55:24
Or, sorry, I don't understand what "updates" is.
<@nirik:matrix.scrye.com>
15:55:46
locally changing pungi config, running pungi to produce a server image that we look at / test. Perhaps we could nerd snipe adamw into doing that testing.
<@nirik:matrix.scrye.com>
15:56:27
rawhide and branched are made from pungi-fedora config. updates and updates-testing repos are made by bodhi using the pungi config in ansible repo. They are two disjoint different pungi configs.
<@patrikp:matrix.org>
15:56:43
Ughh.
<@nirik:matrix.scrye.com>
15:56:48
in the rawhide/pungi-fedora repo one we filter glibc32
<@patrikp:matrix.org>
15:56:50
I will need to re-read that a couple of times...
<@nirik:matrix.scrye.com>
15:57:00
in the ansible/bodhi one we currently do not
<@nirik:matrix.scrye.com>
15:57:34
so, it gets shipped to users via the 'updates' repo
<@patrikp:matrix.org>
15:57:48
OK, got it.
<@patrikp:matrix.org>
15:58:35
Can't I just add it to the Ansible config then?
<@patrikp:matrix.org>
15:58:56
I added openh to that exact same file a few weeks ago, or am I wrong?
<@nirik:matrix.scrye.com>
15:59:02
yes. It's just a second line after this openh264 pr: https://pagure.io/fedora-infra/ansible/pull-request/2562#request_diff
<@nirik:matrix.scrye.com>
15:59:10
you are not, it's just one more package/line
<@patrikp:matrix.org>
16:00:06
And then we wait a while but in theory that should solve the ticket?
<@patrikp:matrix.org>
16:00:12
We are over time.
<@patrikp:matrix.org>
16:00:18
!topic Choose next chair.
<@patrikp:matrix.org>
16:00:25
!info Next chair May 5th: Anton
<@patrikp:matrix.org>
16:00:40
I will add that line.
<@nirik:matrix.scrye.com>
16:00:49
well, that will solve that part of the ticket
<@nirik:matrix.scrye.com>
16:01:02
we still need to deal with the server filter stuff. I'll ask QE about it.
<@patrikp:matrix.org>
16:01:27
Right. You are correct.
<@patrikp:matrix.org>
16:01:44
!endmeeting
<@patrikp:matrix.org>
16:01:44
!info Thank you all for coming!