#meeting-3:fedoraproject.org log

<@amedvede:fedora.im>

15:59:35

!startmeeting RELENG (2025-01-20)

<@meetbot:fedora.im>

15:59:42

Meeting started at 2025-01-20 15:59:35 UTC

<@meetbot:fedora.im>

15:59:43

The Meeting name is 'RELENG (2025-01-20)'

<@amedvede:fedora.im>

15:59:43

Hello everyone

<@patrikp:matrix.org>

16:00:00

Good evening. 👋

<@amedvede:fedora.im>

16:00:09

!meetingname releng

<@meetbot:fedora.im>

16:00:10

The Meeting Name is now releng

<@bittin:matrix.org>

16:00:14

afternoon

<@amedvede:fedora.im>

16:00:20

!chair nirik jnsamyak patrikp amedvede

<@amedvede:fedora.im>

16:01:02

how you doing guys, It's my first releng meeting so if there will be some mistakes sorry for that

<@amedvede:fedora.im>

16:01:23

!info Meeting is 60 minutes MAX. At the end of 60, it stops.

<@amedvede:fedora.im>

16:01:29

!info Agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw.

<@amedvede:fedora.im>

16:01:36

!topic Init process.

<@nirik:matrix.scrye.com>

16:01:41

morning

<@amedvede:fedora.im>

16:01:52

Do we have anything for the init? Any blockers/tasks/issues/requests/features that need releng intervention?

<@patrikp:matrix.org>

16:02:12

I have a thing about the OpenH264 composes. Would now be a good time or at the end?

<@amedvede:fedora.im>

16:02:38

I guess we can discuss it now

<@patrikp:matrix.org>

16:02:48

Alright.

<@jnsamyak:matrix.org>

16:02:51

Hey hey

<@amedvede:fedora.im>

16:03:03

whatsup

<@patrikp:matrix.org>

16:03:21

So now my plan is to use Pungi to accomplish this.

<@patrikp:matrix.org>

16:03:21

Koji can build the RPMs and sign them, but it doesn't have the functionality to compose repositories or distrubutions directly.

<@patrikp:matrix.org>

16:03:21

I have come to the conclusion that we cannot rely solely on Koji, we will also need Pungi.

<@patrikp:matrix.org>

16:03:21

<@patrikp:matrix.org>

16:03:21

Roughly:

<@patrikp:matrix.org>

16:03:21

1) Create `openh264` config file

<@patrikp:matrix.org>

16:03:21

(Q1: What is the most minimalist possible .conf file? What can I use as a template? I might need some help with this.)

<@patrikp:matrix.org>

16:03:21

<@patrikp:matrix.org>

16:03:21

2) Tag the build in Koji (I think the openh264 tag already exists)

<@patrikp:matrix.org>

16:03:21

<@patrikp:matrix.org>

16:03:21

3) Run a command such as this (Q2: on which host would be best?):

<@patrikp:matrix.org>

16:03:21

`pungi-koji --config=openh264.conf --target-dir=/mnt/koji/private`

<@patrikp:matrix.org>

16:03:21

(Q3: Does that look right?)

<@patrikp:matrix.org>

16:03:21

<@patrikp:matrix.org>

16:03:21

4) Check what is generated and go from there.

<@patrikp:matrix.org>

16:03:21

<@patrikp:matrix.org>

16:03:21

Does this look reasonable? Anything to keep in mind?

<@patrikp:matrix.org>

16:03:21

I took a look at the older odcs composes and there is more that we need, i.e. repodata.

<@patrikp:matrix.org>

16:05:32

There is a draft from Samyak in our doc as related to the config file.

<@nirik:matrix.scrye.com>

16:05:51

so, I can't recall... why did we not want to use dist-repos?

<@patrikp:matrix.org>

16:06:08

Licensing issues.

<@patrikp:matrix.org>

16:06:38

The RPMs cannot be exposed to the wider internet, we send those to Cisco and they publish them. If I understand the question correctly.

<@nirik:matrix.scrye.com>

16:07:02

sure, but we could block the dist repo from being exposed perhaps...

<@nirik:matrix.scrye.com>

16:07:23

just use it to make the repo and sync it to the place we normally put them...

<@nirik:matrix.scrye.com>

16:07:39

but I would have to look and see if thats possible... there might be some reason I am not remembering.

<@patrikp:matrix.org>

16:07:48

That would be very helpful.

<@nirik:matrix.scrye.com>

16:08:43

ugh, I hate apache rewrite rules. )

<@jnsamyak:matrix.org>

16:08:51

Maybe because to keep an extra layer of safety so we don’t expose or sync it to the wrong place?

<@nirik:matrix.scrye.com>

16:09:15

well, the builds are there using this method to protect them

<@patrikp:matrix.org>

16:09:30

For reference this is the SOP we used for odcs:

<@patrikp:matrix.org>

16:09:30

https://docs.fedoraproject.org/en-US/infra/releng_misc_guide/sop_generating_openh264_composes/

<@jnsamyak:matrix.org>

16:10:00

But can we not achieve this by just making use of a private repo only accessible by the root users or something? For the initial testing use cases at least?

<@nirik:matrix.scrye.com>

16:11:22

well, dist-repos always go to the same dir named after the tag... but yeah, possibly we could make them unreadable normally...

<@nirik:matrix.scrye.com>

16:11:53

this is the setup we use for the fN-infra tags...

<@jnsamyak:matrix.org>

16:11:57

It does, but in my opinion trying doing things in a side tag (f42-openh264-test) for example and see and then once we have these sorted we can switch to the main tag for all these

<@nirik:matrix.scrye.com>

16:12:09

https://kojipkgs.fedoraproject.org/repos-dist/

<@jnsamyak:matrix.org>

16:12:18

I’ll take a look

<@nirik:matrix.scrye.com>

16:12:36

I can look and see if our current protection for those rpms works for dist repos...

<@patrikp:matrix.org>

16:13:25

And what would the workflow look like then? If we had a dist-git repo?

<@nirik:matrix.scrye.com>

16:14:19

then packages would be built, land in a fN-openh264 tag and tag2distrepo would make a dist repo, then we would just need to sync it to the right place to publish it after cisco said it was there.

<@nirik:matrix.scrye.com>

16:15:23

hum, except no, tag2distrepo wouldn't do multilib... so we would probibly have to run our own dist-repo command

<@patrikp:matrix.org>

16:15:40

And how would it relate to the way the repo is generated? These are two separate issues or is there a connection?

<@patrikp:matrix.org>

16:16:16

I.e. generate it with a Pungi config file and then?

<@nirik:matrix.scrye.com>

16:16:31

no need for pungi... ;)

<@nirik:matrix.scrye.com>

16:16:37

yeah, so it works: https://kojipkgs.fedoraproject.org/repos-dist/testing/

<@nirik:matrix.scrye.com>

16:17:01

so it would be a koji call like:

<@nirik:matrix.scrye.com>

16:17:50

koji dist-repo f42-openh264 THEKEY --multilib=CONFIG --noinherit

<@nirik:matrix.scrye.com>

16:18:15

and then koji would make the repo under repos-dist/f42-openh264

<@nirik:matrix.scrye.com>

16:18:49

I guess one downside is that dist-repos get removed as they age, we would have to sync it off to make sure we had a copy.

<@patrikp:matrix.org>

16:20:18

And we would have everything needed from the compose, not just the RPMs? On batcave in my home there's the odcs composes. From those we synced all of this (not the RPMs that were sent to Cisco): fN-openh264/compose/Temporary

<@nirik:matrix.scrye.com>

16:20:52

Yeah, should have everything... I can fire one off and you can take a look at it? or you can fire it off.

<@nirik:matrix.scrye.com>

16:20:57

I think it should be safe to do.

<@jnsamyak:matrix.org>

16:20:57

Would there be a way to automate this process?

<@nirik:matrix.scrye.com>

16:21:21

well, we have tag2distrepo... but I don't think it can do multilib... which we needed for this. ;(

<@patrikp:matrix.org>

16:21:26

koji dist-repo f42-openh264 THEKEY --multilib=CONFIG --noinherit

<@patrikp:matrix.org>

16:21:26

This command?

<@patrikp:matrix.org>

16:21:40

What would be THEKEY and CONFIG?

<@patrikp:matrix.org>

16:21:57

If you could fire it off that would be great, let's see what happens.

<@nirik:matrix.scrye.com>

16:22:32

THEKEY should be the f42 gpg key name in koji... lets see.

<@patrikp:matrix.org>

16:23:00

Next topic I suppose? Don't want to take up all of the time.

<@amedvede:fedora.im>

16:23:09

okay

<@nirik:matrix.scrye.com>

16:23:20

105ef944 :)

<@amedvede:fedora.im>

16:23:27

we can return to this discussion at the end

<@nirik:matrix.scrye.com>

16:23:28

sure, I can. Sorry I didn't think about this before... ;(

<@patrikp:matrix.org>

16:23:38

No worries, thanks a lot!

<@amedvede:fedora.im>

16:23:47

!topic Scheduled actions coming up in the next week.

<@amedvede:fedora.im>

16:24:36

!info Here we list/discuss anything about items that are due to be done in the next week.

<@amedvede:fedora.im>

16:24:42

!link https://fedorapeople.org/groups/schedule/f-41/f-41-releng-tasks.html

<@amedvede:fedora.im>

16:24:47

!link https://fedorapeople.org/groups/schedule/f-42/f-42-releng-tasks.html

<@amedvede:fedora.im>

16:24:59

what we have planned for next week?

<@jnsamyak:matrix.org>

16:25:27

Okay for mass rebuild

<@jnsamyak:matrix.org>

16:25:38

It was fired last week

<@jnsamyak:matrix.org>

16:25:47

And got completed this Monday morning

<@amedvede:fedora.im>

16:26:17

what i see in doc, we have planned "fedora-repos update with the new keys is available in updates-testing" for tomorrow

<@jnsamyak:matrix.org>

16:26:19

We found out that there was some packages that were left because of Indra/pagure outage

<@jnsamyak:matrix.org>

16:26:41

So we did a mass rebuild for those specific changes as well today

<@amedvede:fedora.im>

16:27:41

so mass rebuild related tasks are done?

<@jnsamyak:matrix.org>

16:27:55

Still if we match the number of failed composes vs the needs rebuild one there are 218 packages still vaguely differentiating I’ll figure that out what happens

<@jnsamyak:matrix.org>

16:28:09

Still if we match the number of failed composes vs the needs rebuild one there are 218 packages still vaguely differentiating I’ll figure that out what happening

<@jnsamyak:matrix.org>

16:28:32

Once that done, I’ll merge the rebuild tag and send a mail on the list

<@nirik:matrix.scrye.com>

16:29:42

yeah, wonder what those are. :)

<@jnsamyak:matrix.org>

16:29:47

Not sure is we do something separately here, but i did create keys for f44 and pushed and build those to fedora repos

<@nirik:matrix.scrye.com>

16:29:58

and do remember to merge direct to the f42 tag...

<@jnsamyak:matrix.org>

16:30:14

Aye aye captain

<@nirik:matrix.scrye.com>

16:30:22

jnsamyak: I think that one is to make sure there's updates pushed to all releases with it?

<@jnsamyak:matrix.org>

16:30:45

That’s all for the release update I’ll be back on my desk in the morning tomorrow and can check more

<@jnsamyak:matrix.org>

16:31:11

I’ll check it more in depth tomorrow

<@amedvede:fedora.im>

16:31:28

I think its about it

<@amedvede:fedora.im>

16:32:43

okay, next topic then?

<@amedvede:fedora.im>

16:34:43

!topic Tickets that need attention.

<@amedvede:fedora.im>

16:34:52

!info This is the time where you can bring up releng tickets to discuss if there are blockers, etc.

<@amedvede:fedora.im>

16:36:31

for last 7 days few tickets was opened, most of them are closed now. so I guess we will mostly discuss old tickets

<@amedvede:fedora.im>

16:37:21

!me )

<@amedvede:fedora.im>

16:37:56

!releng 12531

<@zodbot:fedora.im>

16:37:57

● **Assignee:** Not Assigned

<@zodbot:fedora.im>

16:37:57

**releng #12531** (https://pagure.io/releng/issue/12531):**Packages that have not been rebuilt in a while or ever**

<@zodbot:fedora.im>

16:37:57

<@zodbot:fedora.im>

16:37:57

● **Opened:** 5 days ago by kevin

<@zodbot:fedora.im>

16:37:57

● **Last Updated:** 4 days ago

<@amedvede:fedora.im>

16:38:19

one of recent ones

<@jnsamyak:matrix.org>

16:44:48

Nothing from my end for the tickets this time, I’m boarding see you all on the next one!

<@nirik:matrix.scrye.com>

16:45:23

I asked the go room about those...

<@nirik:matrix.scrye.com>

16:45:39

but yeah, many seem to be the case that the package was added and no one ever did a build.

<@amedvede:fedora.im>

16:47:24

so should we build them or what investigation it expects?

<@nirik:matrix.scrye.com>

16:48:22

well, the people who got them reviewed/main admins on those packages should decide if they are needed or not.

<@nirik:matrix.scrye.com>

16:48:41

I suppose we could set some sort of deadline to just retire them...

<@amedvede:fedora.im>

16:49:07

okay so solution will be to connect with those people and ask?

<@nirik:matrix.scrye.com>

16:49:47

yeah, I was hoping the go sig could poke at some of them at least.

<@nirik:matrix.scrye.com>

16:49:53

perhaps we revisit in a few weeks?

<@amedvede:fedora.im>

16:50:16

yop

<@amedvede:fedora.im>

16:51:45

and can you clarify how this topic of meeting works, should i bring up tickets that seems interesting to me?

<@patrikp:matrix.org>

16:52:13

Yeah, if you have a ticket to bring up this is the correct time.

<@patrikp:matrix.org>

16:52:37

I don't have anything else.

<@amedvede:fedora.im>

16:52:42

!releng 12522

<@zodbot:fedora.im>

16:52:43

<@zodbot:fedora.im>

16:52:43

● **Last Updated:** a week ago

<@zodbot:fedora.im>

16:52:43

● **Assignee:** amedvede

<@zodbot:fedora.im>

16:52:43

● **Opened:** a week ago by cottsay

<@zodbot:fedora.im>

16:52:43

**releng #12522** (https://pagure.io/releng/issue/12522):**Missing rawhide branch for recently created package 'pybind11-json'**

<@amedvede:fedora.im>

16:52:51

i took a look on it

<@amedvede:fedora.im>

16:53:09

in fedora-scm-request repo json looks as usual

<@amedvede:fedora.im>

16:53:18

but rawhide wasn't created

<@patrikp:matrix.org>

16:53:30

Can't they just use `fedpkg request-branch`? What would happen then?

<@amedvede:fedora.im>

16:54:00

so I plan recreate it tomorrow, but the other part is investigate why it wasn't create in first place

<@nirik:matrix.scrye.com>

16:54:47

normally main is just an alias to rawhide...

<@nirik:matrix.scrye.com>

16:54:56

so yeah, very odd, not sure what could have happened.

<@amedvede:fedora.im>

16:55:47

i will use `fedpkg request-branch` tomorrow and will take a look what will be in toddlers log

<@nirik:matrix.scrye.com>

16:56:02

I am not sure that will work... but you can try it. ;)

<@patrikp:matrix.org>

16:56:31

If they use `fedpkg request-branch` and then set it in project configs?

<@patrikp:matrix.org>

16:56:31

So alias rawhide to main.

<@patrikp:matrix.org>

16:56:31

There is an alias section in the settings.

<@patrikp:matrix.org>

16:56:50

Settings -> Git Branches

<@patrikp:matrix.org>

16:57:49

Well we are nearly at the top of the hour. I can take next week as a host. Thanks for hosting!

<@amedvede:fedora.im>

16:58:21

Perfect!, I will modify meet doc regarding it

<@amedvede:fedora.im>

16:58:31

!topic Choose next chair.

<@amedvede:fedora.im>

16:58:43

!info Next chair Jan 27th: patrikp

<@nirik:matrix.scrye.com>

16:59:31

yeah, should be able to add aliases /etc in settings

<@amedvede:fedora.im>

16:59:38

!info Next chair Jan 27th: Patrik

<@amedvede:fedora.im>

16:59:52

!topic Discussion / Any other business.

<@amedvede:fedora.im>

17:00:35

I think we overtime now, so if you don't have anything for discution we can finish this meeting

<@amedvede:fedora.im>

17:00:45

!info Thank you all for coming!

<@amedvede:fedora.im>

17:01:01

!endmeeting