18:00:13 #startmeeting Go SIG meeting 18:00:13 Meeting started Mon Jul 31 18:00:13 2023 UTC. 18:00:13 This meeting is logged and archived in a public location. 18:00:13 The chair is alexsaezm. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:00:13 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:13 The meeting name has been set to 'go_sig_meeting' 18:00:35 #topic Roll Call 18:00:41 Welcome everyone! 18:00:53 it's seems the bridge works this time (or at least I can see bot messages in matrix) 18:01:16 As usual, we can wait a little for everyone :) 18:03:45 .hello2 18:03:46 eclipseo: eclipseo 'Robert-André Mauchin' 18:04:14 Hi people 😀 18:04:16 .hello 18:04:16 MavJS: (hello ) -- Alias for "hellomynameis $1". 18:04:22 .hello2 18:04:23 MavJS: mavjs 'Maverick Kaung' 18:04:27 hello! :) 18:05:11 o/ 18:06:36 We have two issues tagged, for the meeting, the same ones as the last meeting. docker and ix86. Does anyone has a preference? (I don't have anything for those two) 18:07:49 not much to ay about each 18:08:44 In that case, unless anyone else has something to add (we can wait) we can jump into the open floor 18:08:49 me neither :> 18:09:20 ok for me 18:09:50 #topic Open floor 18:10:37 Go 1.21rc3 is on rawhide and seems that it made several package fail. Apart from that I have a "nice" list of FTBFS, so nothing fancy to add 18:11:01 (Tomorrow there will be a security go release apparently) 18:11:04 could we put a lits of all Go FTBFS 18:11:25 i, working on updating acme rignt now mut there's 50 new deps 18:11:42 s/lits/list/ 18:11:48 .hello mikelo2 18:11:49 mikelo_m[m]: mikelo2 'Mikel Olasagasti Uranga' 18:12:06 s/,/'m/, s/rignt/right/, s/mut/but/ 18:13:11 eclipseo: I’ve that query, give 2mins 18:13:57 The F39 failures -> https://kojipkgs.fedoraproject.org/mass-rebuild/f39-failures.html 18:14:42 thx 18:14:54 https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&email1=go-sig%40lists.fedoraproject.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals&list_id=12392650&query_format=advanced&short_desc=FTBFS&short_desc_type=allwordssubstr 18:15:11 that is way better ^ 18:15:50 one of the packages failing with 1.21 is golang-github-pkg-errors, unmaintained upstream, that is used by quite a few packages 18:17:22 golang-github-onsi-ginkgo-2 was affected also and upstream already fixed after reporting 18:17:44 and a test with azure sdk that merged my PR upstream 18:18:49 but... many of the ftbfs are previous to go-1.21 18:19:43 For this week I'm planning on going through the ones I own and fix them no matter if they are long FTBFS or not, because I have 109 bugs open :D 18:20:14 newbie... 149 in my case :rofl: 18:20:18 hahah 18:20:26 wanna some more? 18:20:58 I've been cleaning my plate the last few days, I'm close to 30 closed BZ iirc 18:21:25 O: 18:21:54 don't have that much time to close that much! I'll look into it this wee-end more 18:22:36 i'm looking at golang-github-pkg-errors forks but there is not much more activity 18:24:48 mikelo_m: do you have a build.log of golang-github-pkg-errors ? just to see if I can patch it 18:25:00 at least for this time 18:25:12 https://koschei.fedoraproject.org/package/golang-github-pkg-errors 18:25:28 * alexsaezm always forgets about koschei when he needs it 18:26:06 --- FAIL: TestStackTrace (0.00s)... (full message at ) 18:26:57 this list is not acurate but worth checking https://koschei.fedoraproject.org/affected-by/golang-bin?epoch1=0&version1=1.20.5&release1=1.fc39&epoch2=0&version2=1.21~rc3&release2=2.fc39&collection=f39 18:27:01 I can try to patch it, but it's not a solution of course 18:27:28 the problem with that list is that many of the packages were in ftbfs mode already 18:28:20 podman is there?! 18:30:24 if they appear with the green check it means that they are not failing anymore but they did right? 18:30:29 https://koschei.fedoraproject.org/package/podman yes 18:30:51 I don't understand why some of them are duplicated 18:31:00 tinygo and delve appear multiple times 18:31:19 multiple times, where? 18:32:13 https://koschei.fedoraproject.org/affected-by/golang-bin?epoch1=0&version1=1.20.5&release1=1.fc39&epoch2=0&version2=1.21~rc3&release2=2.fc39&collection=f39 18:32:14 there 18:32:20 I see delve more than once 18:32:42 podman too 18:33:54 I guess that it's because koschei keeps building packages and it may record how many times has been built against golang-1.21rc3 18:35:16 hmm, yeah podman build failing on gvisor-tap-vsock it seems 18:36:17 gvisor package is +18 months old, there may be some issue there 18:36:59 and i love that it's gohacks that seems to be causing it "Package gohacks contains utilities for subverting the Go compiler." (in my naive reading of the build log output from go) 18:41:42 so I guess the plan now is to keep fixing this things :) 18:41:55 does anyone has something to add, or we can call it? 18:42:09 I have 1 thing, regarding my email on the golang list 18:42:30 podman seems to be fixed in 4.6.0 18:42:40 my PR for gobuster was merged by Fab however a build was not submitted: https://src.fedoraproject.org/rpms/gobuster/pull-request/5 (could someone from go-sig submit a build?) 18:42:53 the other one is still waiting for a merge: https://src.fedoraproject.org/rpms/ffuf/pull-request/1 18:43:05 sure 18:43:08 let me do it 18:43:48 if that was for me: thank you :) 18:43:53 wait... it should be built 18:43:57 let me check... 18:44:05 it won't build 18:44:12 + %global goipath github.com/OJ/gobuster/v3 18:44:12 + Version: 3.5.0 18:44:21 https://koji.fedoraproject.org/koji/buildinfo?buildID=2239402 18:44:30 you chnaged the import patch 18:44:37 s/patch/path/ 18:45:04 ah its a binary ok 18:45:17 yeah, and it seems it was build during the mass rebuild 18:45:23 so rawhide has it already 18:45:39 ah, okay, since i didn't see a "build" in the PR like the rest, I thought it was 18:45:43 do you want it on older path? 18:46:11 personally no preference 18:46:20 it's just a go binary tool 18:46:29 s/path/branch/ 18:46:47 ah, there was one person wishing for it 18:47:42 MavJS: I suggets you to write an email to fab if you want to be the co-maintainer of those two packages 18:47:47 s/suggets/sugget/ 18:48:11 mikelo_m[m]: i did that today 18:48:31 awesome 18:48:53 so i guess i still have to wait on ffuf merge from fab then ? :S 18:49:43 well I can build the ther branches with PP 18:50:02 eclipseo: i didn't answer your question properly, if you could please build for F38 minimum for gobuster 18:50:38 i think current+rawhide branches are good enough, imho 18:50:51 MavJS: PR is correct, but can you wait for a few more days for fab to answer your email? if not ping me and I'll do the PR + build 18:51:01 mikelo_m[m]: roger. will do. appreciate it. 18:52:57 anything else before we call it? 18:53:14 also, does anyone have a script/tool that can walk the dependencies to see what needs to be packaged? 18:53:21 if someone uses restic, I'll appreciate feedback on 0.15.2 update https://bodhi.fedoraproject.org/updates/FEDORA-2023-6cd7536ba3 18:53:53 mikelo_m[m]: i use restic.. will take a look. 18:54:01 MavJS: not me, but I also feel the need of something that parses go.mod and compares against Fedora versions. 18:54:40 so a tool that reads go.mod, checks the nvr there and check the packages in fedora? 18:54:45 hmmm that sounds interesting 18:54:53 i started working on that using https://pkg.go.dev/golang.org/x/mod/modfile#File 18:55:17 some packages have +20 deps and checking versions manually can be tedious 18:55:20 not perfect.. and looking at the go2rpm parsing for name stuff 18:55:31 like removing go- from package name etc 18:55:32 I usually check go.mod diffs between packages version and new version 18:56:00 but for new packages or large updates can be handy 18:56:02 yeah, that's easy to do if you have around 10x first-level deps :> 18:56:18 looking at some "security" tools i gave up :p 18:56:31 you usually only need the first level deps to build the package 18:56:37 i see 18:56:43 i'm still learning this stuff :) 18:56:47 the problem is that we require everything in the chain because... Fedora I guess 18:56:56 heh :) 18:57:14 when you build a package in Fedora it may require 700 packages, but if you just go with git clone && go build, it will take only those in the go.mod 18:57:26 our problem is that we chain BuildRequires 18:57:47 so if you have a chain of 7, you need to pull the deps of all the packages in the chain 18:57:50 do you folks also use copr to get the packages build into a project so you can build multiple packages ? 18:58:02 yeah 18:58:09 I like to use copr for new packages and to test package updates 18:58:19 okay, i'll give that a go 18:58:33 using copr cli can be useful to test new packages and it's deps easily 18:58:42 i might send some questions here or on the mailing list 18:58:47 thank you for all your answers :) 18:58:48 iirc alexsaezm wrote a script based on some comments I gave him 18:59:07 https://github.com/alexsaezm/dotfiles/blob/main/scripts/.local/scripts/fedora-build-on-copr 18:59:10 <3 18:59:19 alexsaezm++ 18:59:25 might not work as expected, I usually change a lot my scripts 18:59:32 but feel free to copy it and use it 18:59:44 appreciate the pointers :) 19:00:10 the trick is to use PRs 19:00:15 ouch, not PRs, but branches 19:01:07 so fedpkg fork then git push to your fork, in a branch if possible, and then use that branch to be built by copr and then all the packages that require the package to be built against the update in copr 19:01:18 super useful to ensure and update doesn't break things 19:03:57 yeah, if I recall correctly the script I pasted doesn't do that exactly, just try to build the currect branch on copr (f38 for example). If later I want to use my personal branch, I usually use the fepkg copr-build 19:04:15 alexsaezm: what do you think about asking a Fedora Badge for the go-sig team? 19:04:26 that works for packages already in fedora, but for most what i see for new packages i was playing around with.. dependencies and its dependencies are not in fedora :> 19:04:46 TIL fedpkg copr-build 19:05:01 I usually use fedpkg scratch-build 19:05:22 MavJS: for that I use a github repo and copr 19:05:44 mikelo_m[m]: ok, do you have an example repo? 19:05:46 I do too, but fedpkg copr-build user/project is really fast to use with already made dependencies, that's why I didn't include that functionality in the script 19:06:23 mikelo_m[m]: the folks that design the badges do an amazing work, it would be lovely to have a gopher with a fedora or something like that 19:06:28 https://github.com/mikelolasagasti/rclone-specs plus https://copr.fedorainfracloud.org/coprs/mikelo2/rclone/ 19:06:38 sweet :) 19:07:09 for packages that are in Fedora but you just want to update them, you can create a fork + branch and use copr's dist-git option 19:07:38 for new packages, I've a hack-script that creates the output required for fedora-review 19:07:53 i see 19:08:13 do you have a thing to rebuild all packages affected by a chane? 19:08:30 yes 19:09:24 https://mikel.olasagasti.info/tmp/fedora/chain.txt 19:10:25 I use those commands for that, I don't have a script, but it's easy to script 19:11:11 neat :) 19:11:35 https://github.com/alexsaezm/dotfiles/blob/main/scripts/.local/scripts/fedora-builddependencies 19:11:40 I think it had a bug last time I used it 19:14:55 #action Alex to check what is required for a go-sig Fedora Badge 19:16:17 did i miss some messages between "I think it had a bug last time I used it" and action for alex ? 19:16:31 no 19:16:53 ah okay :) 19:16:56 I was referring to the github link I pasted, it's the same idea mikelo_m pasted, but in a script 19:17:39 yeah, that i got, but there was like 3 minutes of no messages, so i thought maybe the bridge died a bit :) 19:18:33 any other topic? 19:18:47 not from me. thank you all for answering my questions patiently :) 19:18:47 not from my side 19:20:24 sorry ts ate got to go 19:21:06 nothing for me 19:21:35 then we can call it 19:21:39 thanks everyone!!! 19:21:49 #endmeeting