#meeting-1:fedoraproject.org log

<@alexsaezm:fedora.im>

18:00:23

!startmeeting Go SIG meeting

<@meetbot:fedora.im>

18:00:24

Meeting started at 2025-07-28 18:00:23 UTC

<@meetbot:fedora.im>

18:00:24

The Meeting name is 'Go SIG meeting'

<@alexsaezm:fedora.im>

18:00:28

!topic Roll Call

<@mikelolasagasti:matrix.org>

18:00:30

!hi

<@zodbot:fedora.im>

18:00:32

Mikel Olasagasti Uranga (mikelo2)

<@alexsaezm:fedora.im>

18:00:41

Hi! as always we'll wait a feew minutes

<@buckaroogeek:fedora.im>

18:01:29

!hi

<@zodbot:fedora.im>

18:01:30

Brad Smith (buckaroogeek)

<@alexsaezm:fedora.im>

18:06:00

ok, looks like we are just mikel and brad 🙂

<@buckaroogeek:fedora.im>

18:06:13

And alexsaezm

<@alexsaezm:fedora.im>

18:06:21

I always forget about that guy

<@mikelolasagasti:matrix.org>

18:06:37

🤣

<@alexsaezm:fedora.im>

18:07:07

Last week I was on PTO and away from the laptop, but it was a little bit chaotic. there is a bunch of things that happened, is there anything relevant we should cover first?

<@alexsaezm:fedora.im>

18:07:19

Last week I was on PTO and away from the laptop, but it was a bit chaotic. There are a bunch of things that happened. Is there anything relevant we should cover first?

<@alexsaezm:fedora.im>

18:07:36

Or we should start with the elephant in the room: the Go 1.25 mass rebuild 😄

<@buckaroogeek:fedora.im>

18:08:03

gotmax23: did an excellent response and follow through

<@mikelolasagasti:matrix.org>

18:08:24

yep, he deserves a big cookie

<@alexsaezm:fedora.im>

18:08:40

we need to ask for a big cookie reward

<@alexsaezm:fedora.im>

18:09:08

!topic Go 1.25 Mass Rebuild Status - DWARF5 Issue Resolution

<@mikelolasagasti:matrix.org>

18:09:46

the good thing is that most of the packages affected in the f43 mass rebuild built just fine once the hotfix landed

<@alexsaezm:fedora.im>

18:10:35

If I'm not missing anything, everything is fine, but the solution should be a temporary fix.

<@alexsaezm:fedora.im>

18:10:54

thanks for rebuilding the packages mikel

<@mikelolasagasti:matrix.org>

18:11:00

source-only packages just were OK (unless not affected by orphans or other stuff)

<@mikelolasagasti:matrix.org>

18:11:18

status can be checked in https://kojipkgs.fedoraproject.org/mass-rebuild/f43-need-rebuild.html and https://kojipkgs.fedoraproject.org/mass-rebuild/f43-failures.html

<@mikelolasagasti:matrix.org>

18:11:27

!link https://kojipkgs.fedoraproject.org/mass-rebuild/f43-failures.html

<@mikelolasagasti:matrix.org>

18:11:35

!link https://kojipkgs.fedoraproject.org/mass-rebuild/f43-need-rebuild.html

<@mikelolasagasti:matrix.org>

18:13:00

I think we should work and encourage others to move to Go Vendor Tools to be able to retire most of those packages

<@mikelolasagasti:matrix.org>

18:13:22

and I think until we retire current orphans we won't be able to detect new leave packages

<@mikelolasagasti:matrix.org>

18:14:06

alexsaezm: you should start orphaning you leave packages https://gitlab.com/fedora/sigs/go/package-data/-/blob/main/leaves-by-maintainer?ref_type=heads#L379

<@alexsaezm:fedora.im>

18:14:45

Got it, I'll start with that list this week.

<@mikelolasagasti:matrix.org>

18:15:30

you can use https://raw.githubusercontent.com/decathorpe/miscripts/refs/heads/master/orphan.py to automate the process

<@mikelolasagasti:matrix.org>

18:15:55

it doesn't handle the errors, but you can either skip the failing packages or fix the script ;)

<@buckaroogeek:fedora.im>

18:16:25

mikel: will the listed packages that failed need a manual rebuild or will they just work with the dwarf5 fix in place?

<@mikelolasagasti:matrix.org>

18:16:55

most of the packages are failing because other problems (failing tests, missing dependencies)

<@buckaroogeek:fedora.im>

18:17:00

I did a local build of containernetworking-plugins for rawhide and it works fine

<@mikelolasagasti:matrix.org>

18:18:29

then I understand you need to do manual rebuild

<@buckaroogeek:fedora.im>

18:19:14

Ok. thanks. Bump the release and submit normally i suspect

<@gotmax:matrix.org>

18:21:05

If the last rebuild failed, you don't need to bump the release again

<@gotmax:matrix.org>

18:21:16

You can just submit the build

<@mikelolasagasti:matrix.org>

18:21:56

correct, the rebuilds are done with a commit that will bump the release

<@mikelolasagasti:matrix.org>

18:22:11

correct, the mass rebuilds are done with a commit that will bump the release

<@gotmax:matrix.org>

18:23:40

I plan to rebuild everything after Go 1.25.0 was released to make sure everything that was built with the beta got built with the GA release and also to catch anything that didn't get rebuilt at all because of the debuginfo failures

<@gotmax:matrix.org>

18:24:12

I filed an issue in the Go SIG tracker

<@alexsaezm:fedora.im>

18:24:38

I want to try a tool that a coworker has made. Do you mind if I try it first ?

<@gotmax:matrix.org>

18:25:06

Is that for Copr rebuilds or actual rebuilds in Koji?

<@alexsaezm:fedora.im>

18:26:01

In COPR. I didn't read the documentation but I don't think it supports Koji yet

<@gotmax:matrix.org>

18:26:24

https://gitlab.com/fedora/packager-tools/mass-prebuild ?

<@alexsaezm:fedora.im>

18:26:35

yeah that one

<@gotmax:matrix.org>

18:27:41

That is only for test rebuilds in Copr but I don't think it handles real mass rebuilds where the releases need to be bumped in dist-git and Koji builds have to be submitted

<@gotmax:matrix.org>

18:28:03

But I have heard good things about it for the Copr rebuild usecase

<@alexsaezm:fedora.im>

18:28:36

I can bother fberat with questions 🙂

<@alexsaezm:fedora.im>

18:29:09

but if it's only for COPR it won't solve the whole problem

<@mikelolasagasti:matrix.org>

18:29:35

+1 for me if the testing of this tool doesn't block the mass-rebuild with 1.25 for too long

<@gotmax:matrix.org>

18:30:07

!info https://pagure.io/GoSIG/go-sig/issue/62

<@gotmax:matrix.org>

18:31:02

MPB is built entirely around Copr so I don't think it'll work here

<@gotmax:matrix.org>

18:31:40

But we should definitely try it out prior to Go 1.26 to be aware of any changes there before we push it to rawhide

<@gotmax:matrix.org>

18:32:30

AIUI that's mass *pre*-build's purpose. It's for use *before* a mass rebuild in Rawhide

<@alexsaezm:fedora.im>

18:32:34

yeah, I want to try it to be sure that I can run it from time to time before finding out ourselves in something like merging to rawhide and waiting for the mass rebuild

<@alexsaezm:fedora.im>

18:32:58

my intention if mass prebuild works for us, is to run against go tip

<@alexsaezm:fedora.im>

18:33:26

Waiting for rc to be on Rawhide is getting more and more errorprone.

<@alexsaezm:fedora.im>

18:33:38

with very little time to handle issues

<@alexsaezm:fedora.im>

18:34:23

but working on go tip is quite easy, and we can even report new issues to upstream

<@mikelolasagasti:matrix.org>

18:35:43

gotmax23: when do you plan to retire the golang-* orphans?

<@gotmax:matrix.org>

18:36:13

I did want to talk about that actually

<@gotmax:matrix.org>

18:36:53

I have updated the orphan packages report (https://a.gtmx.me/orphans/orphans.txt) now that FESCo has approved our exception

<@gotmax:matrix.org>

18:37:30

Take a look especially that the new SPECIAL NOTE paragraph at the beginning

<@gotmax:matrix.org>

18:37:35

Does that look okay to y'all?

<@gotmax:matrix.org>

18:38:43

packages will resume after a six-week grace period."

<@gotmax:matrix.org>

18:38:43

I need to clarify the last sentence, as it should be "Once the new guidelines are fully implemented, mass retirements of **orphaned** Golang

<@mikelolasagasti:matrix.org>

18:40:06

based on that list in 4-5 weeks many packages will be retired

<@gotmax:matrix.org>

18:40:18

packages will resume after a six-week grace period."

<@gotmax:matrix.org>

18:40:18

I need to clarify the last sentence, as it should be "Once the new guidelines are fully implemented, automatic retirements of

<@gotmax:matrix.org>

18:40:18

orphaned Golang

<@mikelolasagasti:matrix.org>

18:40:23

~end of september

<@gotmax:matrix.org>

18:41:45

Assuming they're not in the exemptions list, yes

<@mikelolasagasti:matrix.org>

18:43:18

<@mikelolasagasti:matrix.org>

18:43:34

most of the package will be part of F43 then, as branching happens on Aug-12

<@alexsaezm:fedora.im>

18:48:21

Do you think we should remove them before that happens?

<@mikelolasagasti:matrix.org>

18:48:50

no, just noting that

<@mikelolasagasti:matrix.org>

18:49:39

the only problem I see is that if a package has simple dependency chain of 4 levels, it would take ~24 weeks to be retired

<@gotmax:matrix.org>

18:50:53

If anyone wants to add recursive logic to the go_leaves script, they're welcome to :D

<@gotmax:matrix.org>

18:51:20

But once we have the new guidelines, we can at some point start mass retirements of leaves like we did a few releases ago

<@gotmax:matrix.org>

18:51:34

Which will speed up the process

<@mikelolasagasti:matrix.org>

18:51:42

agree

<@mikelolasagasti:matrix.org>

18:53:05

any other topics?

<@alexsaezm:fedora.im>

18:53:36

no, I think we covered everything relevant

<@alexsaezm:fedora.im>

18:53:53

done btw

<@gotmax:matrix.org>

18:54:25

I've been making slow but steady progress on the new guidelines

<@gotmax:matrix.org>

18:54:48

Nothing much to report yet, but feel free to look at the guidelines fork repository on Gitlab

<@mikelolasagasti:matrix.org>

18:55:22

I've been porting packages to gvt, updating specs and adding some packages to EPEL. I think today it's the first time in 2 months I sit in my desk, so I consider it a good amount of work from my side 😅

<@mikelolasagasti:matrix.org>

18:55:56

I'll check the guidelines when I've a few minutes

<@zodbot:fedora.im>

18:55:56

gotmax23 has already given cookies to mikelo2 during the F42 timeframe

<@mikelolasagasti:matrix.org>

18:56:25

gotmax23: are you OK about adding packages to EPEL with the current status of gvt? It's working fine, but I'm not sure if you like the idea of having many packages using it

<@gotmax:matrix.org>

18:56:26

I've been meaning to make an announcement on the EPEL SIG mailing list or Matrix room about GVT being added

<@gotmax:matrix.org>

18:56:47

But I'm glad that you've started adopting it and that it's working :)

<@mikelolasagasti:matrix.org>

18:56:59

I love how simple it is

<@gotmax:matrix.org>

18:57:05

That's a good question :)

<@mikelolasagasti:matrix.org>

18:57:08

*to use it

<@gotmax:matrix.org>

18:58:23

At this point it's still technically in beta/preview but I guess starting to use it in a limited number of packages is okay, and I don't see any major changes at this point

<@mikelolasagasti:matrix.org>

18:58:58

and the other question I've is if still using `%gocheck` is a good idea for packages like `rclone` where there are a bunch of `-d path` to skip some tests until we figure out a clean way to do it with `%gotest`

<@mikelolasagasti:matrix.org>

19:00:09

if all beta/preview software was this good the world would be a better place 😅

<@gotmax:matrix.org>

19:00:34

I had some minor issues with the original CLI interface that I had at one point planned to refactor in https://gitlab.com/fedora/sigs/go/go-vendor-tools/-/issues/63 but I decided against it so after that I was more comfortable branching it for EPEL

<@gotmax:matrix.org>

19:01:12

I have to go so can we table the gocheck discussion for next meeting?

<@alexsaezm:fedora.im>

19:01:29

absolutely

<@gotmax:matrix.org>

19:01:31

I have some thoughts about that also :D

<@gotmax:matrix.org>

19:01:41

Don't think we should start that up now

<@mikelolasagasti:matrix.org>

19:01:45

happy to read them

<@mikelolasagasti:matrix.org>

19:01:51

no worries

<@mikelolasagasti:matrix.org>

19:02:16

I'll use whatever works now and change later

<@mikelolasagasti:matrix.org>

19:02:19

I'll use whatever works now and change later if required

<@gotmax:matrix.org>

19:02:51

SGTM

<@mikelolasagasti:matrix.org>

19:03:09

I should leave also, but before leaving just a ping on prometheus renaming review https://bugzilla.redhat.com/show_bug.cgi?id=2383787 I would like to adhere my packages as soon as possible to the correct namign

<@mikelolasagasti:matrix.org>

19:04:06

leaving, have a nice rest of the week :)

<@alexsaezm:fedora.im>

19:04:21

thanks everyone for attending 🙂

<@alexsaezm:fedora.im>

19:05:19

!action Discuss gocheck status in the next meeting

<@alexsaezm:fedora.im>

19:05:30

!endmeeting