<@alexsaezm:fedora.im>
19:00:11
!startmeeting Go SIG meeting
<@meetbot:fedora.im>
19:00:13
Meeting started at 2025-03-24 19:00:11 UTC
<@meetbot:fedora.im>
19:00:14
The Meeting name is 'Go SIG meeting'
<@alexsaezm:fedora.im>
19:00:19
!topic Roll Call
<@alexsaezm:fedora.im>
19:00:24
Hi everyone! (like always, we can wait a few minutes for everyone)
<@buckaroogeek:fedora.im>
19:01:30
!ho
<@buckaroogeek:fedora.im>
19:01:33
!hi
<@zodbot:fedora.im>
19:01:35
Brad Smith (buckaroogeek)
<@buckaroogeek:fedora.im>
19:01:46
Made it this time
<@alexsaezm:fedora.im>
19:02:14
yay
<@alexsaezm:fedora.im>
19:02:50
I think we are going to be alone for this one 🙂
<@buckaroogeek:fedora.im>
19:03:06
Highly likely
<@buckaroogeek:fedora.im>
19:03:49
Altho last time, gotmax23 regretted missing the meeting.
<@alexsaezm:fedora.im>
19:05:56
I was checking the issues tagged with meeting https://pagure.io/GoSIG/go-sig/issues?status=Open&tags=meeting&close_status= and I only see one with activity, hope @gotmax23 is not only lurking 😄
<@alexsaezm:fedora.im>
19:06:11
!topic Adopt go-vendor-tools and switch to vendoring by default
<@alexsaezm:fedora.im>
19:06:19
<@alexsaezm:fedora.im>
19:07:37
is there any next action regarding this issue?
<@buckaroogeek:fedora.im>
19:09:22
My perspective is that there needs to be someone managing this (coordination, messaging, etc). And that gotmax23 is likely too busy to do that
<@buckaroogeek:fedora.im>
19:09:43
Otherwise next action will always be pending :)
<@alexsaezm:fedora.im>
19:11:34
I can help with that, I'll reach out gotmax23 later and try to bother him a little to see what are the next steps. I think will be better than discussing it here at least this time as he is busy.
<@buckaroogeek:fedora.im>
19:12:40
Sounds good to me. I can help with documentation when the time is ready
<@alexsaezm:fedora.im>
19:12:53
!action @alexsaezm will follow up with gotmax23 for the next steps
<@alexsaezm:fedora.im>
19:13:10
I guess we can move to the open floor
<@alexsaezm:fedora.im>
19:13:24
!topic Open floor
<@alexsaezm:fedora.im>
19:14:23
I've been fixing FBTFS packages here and there these past days. There is still a lot to fix and most of them are because orphans. So no much stuff to talk about from my side. Nothing fancy
<@buckaroogeek:fedora.im>
19:15:07
I have a number of CVEs in the docker and kubernetes stacks to chase down and resolve
<@buckaroogeek:fedora.im>
19:16:17
go-vendor-tools is a big help in updating module but always a risk of breaking something
<@buckaroogeek:fedora.im>
19:16:26
go-vendor-tools is a big help in updating modules but always a risk of breaking something
<@alexsaezm:fedora.im>
19:17:07
are you using it already? 🙂
<@buckaroogeek:fedora.im>
19:17:57
yes
<@buckaroogeek:fedora.im>
19:18:16
across the board for docker and kubernetes related packages
<@alexsaezm:fedora.im>
19:18:49
great 😄
<@buckaroogeek:fedora.im>
19:20:02
Just start fresh with go2rpm
<@alexsaezm:fedora.im>
19:20:03
is there anything I can help with the CVEs?
<@alexsaezm:fedora.im>
19:20:36
I tried! and it solved a lot of issues but there was some additional problems and I gave up... I need to go back to those packages
<@buckaroogeek:fedora.im>
19:21:09
Cannot think of anything specific. They are all go related in one way or another but mostly with modules and not golang specifcally
<@alexsaezm:fedora.im>
19:22:11
got it, well, in any case, just ping me if I can help you (I mean, I have too many bugs to fix but... 😄 )
<@alexsaezm:fedora.im>
19:22:16
is there anything else we should discuss or we can call it a day? 🙂
<@buckaroogeek:fedora.im>
19:22:25
Will do! thanks
<@buckaroogeek:fedora.im>
19:22:34
Call it a day i think
<@buckaroogeek:fedora.im>
19:22:47
Unless lurkers have a comment?
<@alexsaezm:fedora.im>
19:22:59
let's give them 1 minute... 😄
<@yselkowitz:fedora.im>
19:24:24
fyi ELN and RHEL will benefit from the go-vendor-tools conversion for those packages which aren't already vendoring
<@alexsaezm:fedora.im>
19:25:07
I wonder how are we going to deal with that. I mean, I guess the very first thing would be to incorporate the go-vendor-tools right?
<@yselkowitz:fedora.im>
19:25:27
I would think so, the macros are needed at build time iirc?
<@yselkowitz:fedora.im>
19:26:02
golang-github-cpuguy83-md2man is my prime suspect atm
<@alexsaezm:fedora.im>
19:26:05
AFAIK, yes
<@yselkowitz:fedora.im>
19:26:46
and golang-github-openprinting-ipp-usb
<@alexsaezm:fedora.im>
19:27:44
Once we have the Fedora proposal, I'll fwd it to the rest of my team. Just to be ahead of time incorporating the packages.
<@alexsaezm:fedora.im>
19:27:58
what a classic 😄
<@buckaroogeek:fedora.im>
19:28:09
See also https://gitlab.com/fedora/sigs/go/go-vendor-tools/-/issues/3
<@yselkowitz:fedora.im>
19:28:13
please do keep me posted on this
<@yselkowitz:fedora.im>
19:28:41
good point Brad Smith
<@alexsaezm:fedora.im>
19:28:51
oh good one Brad Smith I need to check the dependencies
<@alexsaezm:fedora.im>
19:29:19
last time something like that happened with go-rpm-macros was mostly because we didn't have enough time to review them before the GA
<@buckaroogeek:fedora.im>
19:29:19
At least a good place to track and resolve issues on RHEL/ELN
<@alexsaezm:fedora.im>
19:29:31
<@buckaroogeek:fedora.im>
19:29:45
If i recall, license scanners were one limitation
<@alexsaezm:fedora.im>
19:30:32
I'll bother gotmax23 with that too then
<@buckaroogeek:fedora.im>
19:30:37
Yea! buildkit just fixed on CVE :)
<@buckaroogeek:fedora.im>
19:30:48
Yea! buildkit just fixed one CVE :)
<@alexsaezm:fedora.im>
19:31:48
well if we don't have anything else (and we even got one lurker :D) we can call it I think
<@buckaroogeek:fedora.im>
19:31:59
Sounds good
<@alexsaezm:fedora.im>
19:32:38
thanks everyone!!
<@buckaroogeek:fedora.im>
19:32:51
Thank you for leading
<@alexsaezm:fedora.im>
19:33:16
yeah... "*leading*" 😄
<@alexsaezm:fedora.im>
19:33:20
see you next time
<@alexsaezm:fedora.im>
19:33:23
!endmeeting