go_sig_meeting
LOGS
19:01:31 <jcajka> #startmeeting Go SIG meeting
19:01:31 <zodbot> Meeting started Mon Dec  6 19:01:31 2021 UTC.
19:01:31 <zodbot> This meeting is logged and archived in a public location.
19:01:31 <zodbot> The chair is jcajka. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
19:01:31 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:01:31 <zodbot> The meeting name has been set to 'go_sig_meeting'
19:01:44 <jcajka> Hello and welcome to the Go SIG meeting.
19:01:51 <alexsaezm> hi there!
19:01:52 <jcajka> #topic Roll Call
19:02:00 <jcajka> #chair alexsaezm
19:02:00 <zodbot> Current chairs: alexsaezm jcajka
19:05:33 <jcajka> It seems that there are not many folks around.
19:05:48 <jcajka> There are no tagged issues in the issue tracker at https://pagure.io/GoSIG/go-sig
19:06:11 <jcajka> So, right to the Open Floor.
19:06:17 <jcajka> #topic Open Floor
19:06:37 <alexsaezm> Nothing much to say from my side, tomorrow I'm planning in updating go 1.16 and 1.17
19:07:52 <jcajka> alexsaezm: great. I have been looking in to the issue you have mentioned on the ppc64le and it seems that it is not really serious, I'm still investigating it for the root cause, but the binaries seems correct, so far.
19:08:13 <alexsaezm> awesome, any idea what might be going on?
19:08:20 <alexsaezm> do you need help?
19:08:20 <jcajka> I think you can do safely build with tests disabled/ignore on ppc64le to not block the update.
19:08:28 <alexsaezm> sounds good
19:09:40 <Eighth_Doctor> sweet
19:10:02 <jcajka> something is triggering the comparison failure in rawhide, although the binaries are identical between f35 and rawhide, I will have to dive deeper in to the test code, haven't done that yet, just poked around.
19:10:43 <alexsaezm> thank you!
19:11:50 <jcajka> np
19:11:58 <jcajka> thank you for looking in to the updates
19:12:32 <jcajka> I think one more topic is update to the EPEL7/8's go
19:12:41 <jcajka> as it is now at 1.15
19:12:55 <alexsaezm> never did that, but I can totally try it
19:12:58 <jcajka> I can do that when the rawhide will be up to date on go1.17
19:13:14 <jcajka> ok, we will sync on that then.
19:14:13 <alexsaezm> do you want to update both branches with 1.17?
19:15:37 <jcajka> I have kept the epel on the odd release of Go for it whole life cycle, merging back the respective branch from Fedora. There are some epel specific thing in the respective epel branches.
19:15:46 <jcajka> I would have done that.
19:16:08 <alexsaezm> got it
19:17:04 <alexsaezm> one question, these kind of things, wouldn't it be good to document them in the wiki? not sure if the wiki is the best place but I can totally start documenting stuff so others (or even ourselves) remember this in a future :)
19:18:52 <jcajka> Sure how that feel fit for you, for me it makes some hard commitment, EPEL for me was only on best effort level, how spare time allowed me.
19:21:11 <alexsaezm> documenting is not fun but I think it will pay itself in the long run. Not sure about the policies of the wiki but I'll try to do it while updating and poking things around
19:21:24 <alexsaezm> not sure if we even have some documentation already
19:22:54 <jcajka> alexsaezm: not really, I think it can live in the Go SIG repo.
19:23:11 <jcajka> If you do not find any better place.
19:23:43 <alexsaezm> got it
19:24:40 <jcajka> thank you again :)
19:25:50 <alexsaezm> my pleasure
19:28:28 <jcajka> I think we can move to any more topics.
19:28:35 <jcajka> I have none.
19:29:08 <alexsaezm> me neither
19:30:24 <jcajka> Anyone else?
19:30:35 <jcajka> If not I will end the meeting in a minute.
19:31:39 <jcajka> #endmeeting