15:59:25 <jcajka> #startmeeting Go SIG meeting
15:59:25 <zodbot> Meeting started Tue Mar 31 15:59:25 2020 UTC.
15:59:25 <zodbot> This meeting is logged and archived in a public location.
15:59:25 <zodbot> The chair is jcajka. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:59:25 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:59:25 <zodbot> The meeting name has been set to 'go_sig_meeting'
15:59:29 <jcajka> hello
15:59:33 <jcajka> #chair nim
15:59:33 <zodbot> Current chairs: jcajka nim
15:59:44 <jcajka> #chair Eighth_Doctor
15:59:44 <zodbot> Current chairs: Eighth_Doctor jcajka nim
15:59:54 <jcajka> #chair eclipseo
15:59:54 <zodbot> Current chairs: Eighth_Doctor eclipseo jcajka nim
16:00:20 <olem> .hello2
16:00:21 <zodbot> olem: olem 'Olivier Lemasle' <o.lemasle@gmail.com>
16:00:50 <Eighth_Doctor> .hello ngompa
16:00:51 <zodbot> Eighth_Doctor: ngompa 'Neal Gompa' <ngompa13@gmail.com>
16:01:35 <jcajka> hello and welcome there are no open and tagged issues, so let's move directly to the open floor
16:01:42 <jcajka> #topic Open Floor
16:03:05 <olem> Hi, I started maintaining containerd last week. I tried to upgrade it but there's packages that depend of that version of containerd-devel.
16:03:24 <olem> How do you keep every update in synch?
16:04:00 <eclipseo> pain
16:04:00 <olem> A lot of golang packages depend of each others with a commit dependency (not release-based).
16:05:00 <eclipseo> olem usually we try to depend on the latest released version
16:05:21 <QuLogic> .hello qulogic
16:05:22 <zodbot> QuLogic: qulogic 'Elliott Sales de Andrade' <quantum.analyst@gmail.com>
16:05:33 <jcajka> #chair QuLogic
16:05:33 <zodbot> Current chairs: Eighth_Doctor QuLogic eclipseo jcajka nim
16:06:17 <olem> eclipseo That's why I'm trying to do. So when other packages depend of an old version, I have to either update the dependent packages as well, or patch them?
16:06:28 <Eighth_Doctor> yep
16:07:43 <olem> Ok, thanks. May I join the go-sig group, in order to have commit access to these dependent packages?
16:08:32 <jcajka> olem: if nobody objects I will add you there
16:09:57 <eclipseo> olem yes that's gist of it, i have package waiting to be updated including containerd I believe
16:10:21 <olem> ok
16:10:47 <olem> I will also try in the future to de-bundle some go packages, such as moby-engine (which I maintain) and ignition.
16:11:13 <jcajka> eclipseo: olem is waiting in fas to be sponsored in to the sig
16:11:27 <eclipseo> good luck
16:11:36 <olem> :-)
16:13:41 <jcajka> happy hacking ;)
16:13:45 <eclipseo> ok added to SIG and ML
16:13:55 <olem> Thank you
16:14:12 <eclipseo> might need to relog for it to be effective
16:15:04 <jcajka> not much news on myside, I would like to just note that etcd is going to be orphaned as it is FTBFS, https://bugzilla.redhat.com/show_bug.cgi?id=1799329, the issue seem to be that Go now implements more cyphersuites that it is expecting(at least that is my guess after brief look on the log), do we care about it?
16:16:25 <eclipseo> I'm working on updating etcd
16:17:02 <eclipseo> golang-github-creack-pty
16:17:04 <eclipseo> golang-github-docker-swarmkit
16:17:06 <eclipseo> etcd
16:17:08 <eclipseo> containerd
16:17:17 <nim> olem, golang is mini mass rebuilds all the time, the hope is that things get a little better and easier after each pass
16:17:41 <jcajka> eclipseo: ok, cool
16:17:43 <eclipseo> that's the goal, creak-pty is updated, swarkit is not yet
16:18:43 <nim> eclipseo, last I’ve seen, once you get past the moby/swarmkit/K_s death triangle, the rest is a lot easier
16:19:00 <nim> k8s
16:20:13 <eclipseo> k8s is easier than docker, docker is pinned to old version of stuff
16:20:55 <olem> Yes, docker depends of an old version of containerd for example :-(
16:21:10 <nim> yes k8s codebase is pretty nice, it’s just HUUUGE
16:23:01 <nim> what is sad is that most of the golang stack would not care about the appaling docker state, if docker had bothered to define a stable interfacing subset
16:23:10 <eclipseo> anyone got some topic to discuss for the meeting today? I got to get moving
16:23:43 <nim> eclipseo, just remember to ack the gitea support stuff if you want it integrated
16:23:55 <nim> eclipseo, or tell me what you need fixed
16:25:29 <eclipseo> ah yes I haven't got time to look at it with thi review requests I hd to do, I should be able to look at it ASAP
16:26:21 <nim> eclipseo, the review requests were appreciated :)
16:26:46 <nim> reviews actually :)
16:26:54 <eclipseo> nim do you have a link to your Gitea thing I can't find it
16:27:25 <eclipseo> ha got it
16:27:39 <nim> eclipseo, your net is fatser than mine
16:28:18 <nim> https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/80
16:28:57 <nim> anyway no hurry on my side, it will just take longer to be available
16:31:11 <jcajka> any other topics?
16:32:36 <QuLogic> nothing new right now
16:33:51 <eclipseo> nothing beside needing help to review new package
16:33:56 <eclipseo> if anyonehas time
16:34:52 <eclipseo> nim, it doesn't work: https://gitea.com/xorm/core/archive/0.7.3.tar.gz != https://gitea.com/xorm/core/archive/v0.7.3.tar.gz It's missing a v before version
16:35:25 <jcajka> eclipseo: do you have link handy?
16:35:44 <nim> eclipseo: I’m not adding v by default before version for non github forges
16:36:01 <nim> eclipseo, v is not a standard thing (outside of go)
16:36:41 <nim> eclipseo, and the way github tried to make it default is full of quirks
16:37:03 <nim> eclipseo, just use %global tag v%{version}
16:37:03 <eclipseo> https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&classification=Fedora&columnlist=short_desc&component=Package%20Review&email1=zebob.m%40gmail.com&email2=zebob.m%40gmail.com&email3=zebob.m%40gmail.com&emailreporter1=1&emailtype1=substring&emailtype2=substring&emailtype3=substring&known_name=My%20own%20bugs&list_id=10955912&product=Fedora&query_based_on=My%20own%20bugs&query_format
16:37:04 <eclipseo> =advanced
16:37:18 <eclipseo> ok I'll try
16:37:33 <nim> eclipseo, unfortunately, Linus has always sucked at versionning, and that propagated to git design
16:38:05 <jcajka> eclipseo: thanks
16:38:57 <nim> eclipseo, github was the first forge I processed, I naïvely expected its v use to be consistent, it isn’t, i won’t make the same mistake for new forges
16:41:28 <jcajka> I guess we have nothing else to discuss I will end the meeting in 2mins any other topics?
16:42:27 <eclipseo> no it's ok for me
16:43:11 <nim> ok for me too
16:43:39 <olem> Ok for me, thank you for your welcome.
16:43:49 <jcajka> #endmeeting