18:01:40 #startmeeting Go SIG meeting 18:01:40 Meeting started Mon Jun 5 18:01:40 2023 UTC. 18:01:40 This meeting is logged and archived in a public location. 18:01:40 The chair is alexsaezm. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:01:40 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:01:40 The meeting name has been set to 'go_sig_meeting' 18:01:40 Time for our meeting :) 18:02:21 .hello 18:02:21 jcpunk: (hello ) -- Alias for "hellomynameis $1". 18:02:31 .hello copperi 18:02:32 copperi[m]: copperi 'Jan Kuparinen' 18:06:03 I don't see anything tagged for the meeting that is important, so unless someone wants to talk about one of the mean issues tagged here https://pagure.io/GoSIG/go-sig/issues we can jump into the open floor 18:07:39 I've mostly popped in today to check back in on https://pagure.io/GoSIG/go-sig/issue/43 in the context of EPEL9 containerd 18:08:05 Sure, then lets talk about that one 18:08:27 #topic https://pagure.io/GoSIG/go-sig/issue/43 18:08:57 jcpunk: anything you want to bring new to the table? :) 18:09:00 Regretfully I have neither time nor expertise 18:09:19 Mostly I'm just hopeful for a containerd rpm for EPEL9 18:10:26 The dep tree looks _horrid_ so I get why this may be a super pain to work on 18:11:21 not really familiar with containerd so cannot add anything to the topic. Maybe gotmax is around 18:13:09 In case nobody can't add anything to the topic, I guess the best approach would be to update the bug or talk about this in the devel mailing list for more awareness 18:15:51 I guess we can move to the open floor then :) sorry for not having more to add to the issue 18:15:59 #topic Open floor 18:15:59 No worries 18:16:05 The other thing I'm here to check in on is golang deps for https://bugzilla.redhat.com/show_bug.cgi?id=2208339 18:17:09 I think Mark was around few minutes ago, let's ping him :) Mark E. Fuller 18:17:44 .hello fuller 18:17:45 fuller[m]: fuller 'Mark E. Fuller' 18:17:59 Hi - thanks for the ping 18:18:26 np, I was going to ping you later answering your question about the rawhide build :), but jcpunk was faster :) 18:18:39 :) 18:19:48 I forgot to update the node-exporter.bug? 18:20:09 There is a golang dep you requested a bit back that doesn't seem to have gone anywhere 18:20:16 It needs something branched and built in EPEL 18:20:39 I was stuck and I believe on eclipseo 18:23:31 concurrently I'm working on nats-server, which also has some new packages that need review, plus the koji issue I wrote about 18:23:43 the koji issue...: 18:23:44 $ koji latest-build rawhide golang-github-nats-io-nkeys 18:23:44 Build Tag Built by 18:23:44 ---------------------------------------- -------------------- ---------------- 18:23:44 golang-github-nats-io-nkeys-0.2.0-8.fc38 f39 releng 18:23:48 i see that 18:24:30 also, $ koji list-builds --package=golang-github-nats-io-nkeys shows stuff 18:24:40 * ```$ koji latest-build rawhide golang-github-nats-io-nkeys 18:24:40 Build Tag Built by 18:24:40 --- 18:24:40 golang-github-nats-io-nkeys-0.2.0-8.fc38 f39 releng``` 18:25:05 * ```... (full message at ) 18:32:09 from my side: nothing much to add, 4 Go CVEs are expected for tomorrow so I'll update the package as soon as they drop. 18:33:03 Mark E. Fuller: do you see something like I did with those commands? 18:33:36 I see that the build exists, but it's not listed as the latest in rawhide 18:33:43 and that's where I'm confused 18:34:55 if you click up to the task, you'll see it failed tagBuild as the worker ran out of space 18:37:46 just popped into rawhide now - Elliott Sales de Andrade did you do that? 18:38:06 I ran koji tag-build f39-updates-candidate golang-github-nats-io-nkeys-0.4.4-1.fc39 to copy what the tagBuild was doing 18:38:13 it says you did it Mark E. Fuller :) 18:38:20 created by fuller a minute ago for Fedora 39 18:38:29 it might, but I requested the tagging 18:38:37 * it might say that, but 18:40:21 and that's what I couldn't figure out how to do - it's in the web UI? 18:40:35 nm, I see now 18:41:15 QuLogic: thank you - glad to know what to do if this happens again 18:43:45 anything else someone wants to add? :) 18:46:34 In that case... I guess we can call it. 18:46:38 Thanks everyone! 18:46:48 #endmeeting