19:01:25 #startmeeting Go SIG meeting 19:01:26 Meeting started Mon Nov 22 19:01:25 2021 UTC. 19:01:26 This meeting is logged and archived in a public location. 19:01:26 The chair is jcajka. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 19:01:26 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:01:26 The meeting name has been set to 'go_sig_meeting' 19:01:33 #topic Roll Call 19:01:38 #chair alexsaezm 19:01:38 Current chairs: alexsaezm jcajka 19:02:51 Hello and welcome to the Go SIG meeting 19:03:23 There seems to be no tagged issue this time 19:03:56 I would wait a bit if other SIG member will come and then move to the open floor. 19:04:28 sounds good 19:07:16 it seems that no one new has arrived 19:07:26 #topic Open Floor 19:08:24 Not much to talk about, I updated 1.16 on f34 and f35 (both on testing now) 19:08:36 I have a question regarding next fedora version 19:08:43 should we skip 1.17? 19:08:51 any opinions? 19:09:00 I have nothing from my side, just wanted to ask about the updates seems that they are worked on. 19:09:32 In which sense? I think that keeping it in rawhide, updating it would be nice. 19:09:45 And have f36 on 1.18 19:10:09 if schedule more or less aligns. 19:10:12 Where is your meeting ? 19:10:18 It looks like the Matrix -> IRC bridge is off, the meeting is happening as scheduled on IRC. 19:10:19 * Eighth_Doctor waves 19:10:20 oh I see 19:10:29 jcajka, my idea is to keep updating rawhide with 1.17, when 1.18 goes live, move rawhide to that and that's it 19:10:41 #chair Eighth_Doctor 19:10:41 Current chairs: Eighth_Doctor alexsaezm jcajka 19:10:53 * jcajka adds a chair 19:11:03 haha 19:12:31 alexsaezm: sounds good to me, it will most probably be a pre-release of Go 1.18 for mass-rebuild https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html 19:13:01 I'm fine with that 19:13:13 Just a note for the folks here, it looks like Matrix has finally caught back up with IRC. 19:13:47 this means we need to deal with Go modules in our macros, though 19:13:49 because right now, we don't handle it, afaik 19:13:49 Yes I noticed 19:13:53 and Go 1.18 removes the ability to turn them off 19:14:06 mroche, oh so the [m] means Matrix? 19:14:23 Eighth_Doctor, does it? 19:14:40 alexsaezm: Yes, sorry. The bridge was out of sync for a while. 19:15:40 alexsaezm: actually it apparently happened in 1.17? 19:16:03 Eighth_Doctor, no, it didn't, let me find the email... 19:16:10 https://go.dev/blog/go116-module-changes 19:16:31 GOPATH is deprecated, but there is no fixed date for removal I think 19:17:20 https://groups.google.com/g/golang-dev/c/hGwvCceDr14/m/vb0pxZ8PBgAJ 19:17:28 I sent that email while ago 19:17:57 and I have no idea if they are going to do that for 1.18 but I didn't check tbh 19:18:15 oh crap it's on the 1.18 milestone 19:18:26 so ... yes Eighth_Doctor I need to deal with that 19:18:55 *sigh* 19:19:51 * alexsaezm wasn't following the issue :( 19:21:47 I don't see anything about removing GOPATH, can you link the issue? 19:21:57 https://github.com/golang/go/issues/43684 19:22:04 smfs, ^ that link 19:22:30 thats only for `go get`, right? 19:22:56 yes, AFAIK is the only component affected 19:23:15 I mean 19:23:18 does that affect the macros? 19:23:19 let me correct myself 19:23:29 smfs what macros? 19:23:42 it might be good to make revision of the macros even partially drop them, although there might be "too much" work in that and need for some proposal for FESCO, to make it more known and vetted 19:24:14 smfs: go get shouldn't affect macros in it self, but GOPATH do as they are built around of it 19:24:19 from the mail I sent, one of the responses: For GOPATH mode for finding, loading, and building packages (i.e., what the go command does with GO111MODULE=off): we don't actually have a concrete plan to remove it yet. There won't be any major change in Go 1.17. It's possible we'll print a deprecation notice in 1.18, but we haven't settled on anything. 19:25:00 https://github.com/golang/go/wiki/GOPATH#deprecating-and-removing-gopath-development-mode 19:25:17 TL;DR: Sometime, possibly, in the future 19:25:30 mroche, yeah, that used to be Go 1.17 and now they have it as 1.NN 19:25:42 yep 19:26:00 but, sooner or later we'll need to fix it 19:27:16 Are these the macros that'll need adjusting? 19:27:16 https://github.com/gofed/go-macros 19:27:24 It's what I pulled from the go-srpm-macros spec 19:28:41 these ones https://pagure.io/go-rpm-macros https://src.fedoraproject.org/rpms/go-rpm-macros 19:29:23 Gotcha, wasn't sure if it was the -rpm or -srpm package 19:30:33 ot 19:30:38 thery are left overs, they should be eventually retired, but none told me to do it(it is safe to do so). I will have to look in to that I guess. 19:30:38 it's a little messy :) 19:31:27 hm... they seems to be, that is good 19:31:41 or not? 19:31:57 I will have to dig in to that 19:32:46 jcajka, when you do that, ping me if you don't care someone looking over your shoulder, because I always find this thing messy 19:33:18 alexsaezm: are there any particular next task that you will be looking in to on the macros/module revision? 19:33:31 next tasks 19:33:55 tbh I have everything a little blurry in my mind because I've been working on other non fedora stuff for the past few months, so I guess I need to start more or less from scratch 19:34:35 I would love to find the correct package where I need to implement the fix for the deprecation and to figure out if we can remove the others and trim down the whole macros thing 19:35:50 tbh, macros are still a little magical to me 19:35:53 I'm not sure if we will be able to draft a bit smfs, mroche or other, but it might make sense to create some tracking issue on post updates there so more people can hop on it, and argue about it :D 19:37:18 I can probably help with scratch rebuilds, etc.(how it breaks the Fedora) and with limited knowledge to untangle it a bit 19:38:31 are we talking about the failing 1.17 builds on ppc? 19:39:35 more on the macros 19:41:14 sounds good to me, we need to find something that we like as group 19:43:54 ok. I will ping you tomorrow. 19:43:59 thanks a lot jcajka 19:44:35 np 19:44:58 Are there some other concerns or more topics? 19:45:19 not from my side 19:47:49 Last call. 19:50:03 #endmeeting