go_sig_meeting
LOGS
17:59:12 <jcajka> #startmeeting Go SIG meeting
17:59:12 <zodbot> Meeting started Mon Feb  1 17:59:12 2021 UTC.
17:59:12 <zodbot> This meeting is logged and archived in a public location.
17:59:12 <zodbot> The chair is jcajka. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:59:12 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:59:12 <zodbot> The meeting name has been set to 'go_sig_meeting'
17:59:37 <eclipseo[m]> .hello eclipseo
17:59:38 <zodbot> eclipseo[m]: eclipseo 'Robert-André Mauchin' <zebob.m@gmail.com>
17:59:40 <jcajka> Hello everyone
17:59:46 <jcajka> #chair eclipseo[m]
17:59:46 <zodbot> Current chairs: eclipseo[m] jcajka
17:59:55 <alexsaezm> Hi there
18:00:03 <alexsaezm> .hello alexsaezm
18:00:04 <zodbot> alexsaezm: alexsaezm 'None' <asm@redhat.com>
18:00:14 <jcajka> #chair alexsaezm
18:00:14 <zodbot> Current chairs: alexsaezm eclipseo[m] jcajka
18:00:17 <eclipseo[m]> hello everyone
18:01:14 <jcajka> #topic Roll call
18:01:27 <jcajka> let's wait a tiny bit
18:01:40 <jcajka> .hello jcajka
18:01:41 <zodbot> jcajka: jcajka 'None' <jcajka@redhat.com>
18:01:55 <jcajka> still none :)
18:05:27 <jcajka> there is one tagged issue
18:05:53 <jcajka> #topic https://pagure.io/GoSIG/go-sig/issue/35  GOPATH deprecated on Go 1.17
18:06:31 <jcajka> How that is looking?
18:06:32 <eclipseo[m]> Yeah this gonna be a problem if we don't move fast
18:06:56 <eclipseo[m]> Sadly nim is not here to discuss the status of the modules in Fedosa
18:07:26 <eclipseo[m]> Last time I hot him he said he will try to move forward at the end of January
18:07:38 <eclipseo[m]> I haven't got news since
18:08:06 <eclipseo[m]> I wished to include them in F34 to be able to use them in RHEL 9
18:08:16 <alexsaezm> I would love to help there, I need to schedule some time to work on it tbh :(
18:08:33 <jcajka> I think that I haven't seen him around much. IMHO it would be good in there is something available around branch time to keep it moving quickly, even if that is not perfect.
18:08:55 <jcajka> eclipseo[m]: is there copr repo around with wip stuff?
18:10:05 <jcajka> typo grr... in there is-> if there is
18:10:10 <eclipseo[m]> Yes, it needs changes in redhat-rpm-config, that was the most important to do before F34 release
18:10:41 <eclipseo[m]> I haven't tested it yet myself because I am not familiar with the new syntax
18:13:23 <jcajka> are there any docs or change draft available?
18:13:49 <jcajka> I assume it will need also partial guidelines rewrite.
18:14:10 <eclipseo[m]> Nothing, so far what I've learnt was from the SPEC in nim's COPR
18:14:15 <eclipseo[m]> yes
18:14:42 <jcajka> ack
18:15:26 <jcajka> I guess we need to wait for nim. Do you think that there is anything that we can do in the mean time?
18:16:04 <eclipseo[m]> not really, we need his input for redhat-rpm-config and any documentation
18:16:45 <jcajka> ok I will add this in to the ticket. Can we move to open floor?
18:16:55 <eclipseo[m]> I expect building packages to be more complicated as we may need to provide our on go.mod and we will have to dirable some tests manually too now
18:17:09 <eclipseo[m]> *own
18:17:47 <eclipseo[m]> ok for open floor
18:18:46 <jcajka> ack
18:19:17 <jcajka> to the open floor
18:19:18 <jcajka> #topic Open Floor
18:19:39 <jcajka> from my side we have go1.16rc1 now in rawhide
18:20:12 <eclipseo[m]> yes thanks I was able to build the ftbfs
18:20:41 <eclipseo[m]> So just a status report for my work this past months, I updated all the packages (although there is still new one coming)
18:20:48 <jcajka> I have hit one new issue in the build, but it seems fortunately as just bug in the test https://github.com/golang/go/issues/44028
18:20:57 <jcajka> thanks Neal for help
18:21:09 <jcajka> in the build on s390x
18:21:12 <eclipseo[m]> and then I fixed all the new FTBFS from the mass rebuild
18:21:58 <eclipseo[m]> ack
18:22:38 <eclipseo[m]> One FTBFS remains golang-github-projectdiscovery-mapcidr but upstream has to do the work
18:24:03 <eclipseo[m]> that's all for me
18:24:46 <jcajka> I have seen most of the issues to be related to the GO modules, respectively specs not being by the Fedora guidelines
18:26:03 <eclipseo[m]> which ones?
18:26:12 <jcajka> like packages?
18:26:34 <jcajka> I don't have full list handy
18:26:45 <eclipseo[m]> ok
18:27:37 <eclipseo[m]> Anyhow the conclusion is that we need nim for the next part of Golang packaging
18:28:03 <eclipseo[m]> Do we have a timeline for 1.17?
18:28:39 <jcajka> arduino-builder, deepin-gir-generator, kata-agent, kata-runtime, tmux-top, reg, startdde, oci-kvm-hook, cri-tools, manifest-tool this should be partial list eclipseo[m]
18:29:53 <eclipseo[m]> ah yes the binaries packages, I haven't touched them, I don't know who the maintainers are
18:29:54 <jcajka> eclipseo[m]: for compiler/upstream? I would assume same as always release around September, i.e. in roughly 6m
18:31:32 <eclipseo[m]> I expect I would need two months to redo all the packages using Go modules, maybe more
18:32:25 <jcajka> eclipseo[m]: we should plan for that, especially if nim couldn't get back to the packaging
18:34:24 <jcajka> I guess we will see in few weeks, that is really all from my side for today
18:34:35 <eclipseo[m]> I need nim input to explain how the new packaging works
18:34:41 <eclipseo[m]> ok
18:34:47 <eclipseo[m]> that's all for me too
18:35:21 <jcajka> any more topics?
18:35:38 <eclipseo[m]> not from me
18:35:48 <alexsaezm> nothing from my side
18:36:43 <jcajka> #endmeeting