| 31 Jan 2023 |
 @qbit:tapenet.org | probably be easier to patch all the go files though | 20:42:57 |
 @adam:valkor.net | I don't think that's actually my problem. Sigh. | 20:55:56 |
| @adam:valkor.net | python is being used to generate go code | 20:56:23 |
| @adam:valkor.net | Though this worked well: https://github.com/sirkon/go-imports-rename :) | 20:57:20 |
| @qbit:tapenet.org | yay, the sourcehut GOPRIVATE stuff is not gonna happen | 21:36:58 |
| @qbit:tapenet.org | Update 2023-01-31: Russ Cox of the Go team reached out to us to address this problem. After some discussion, an acceptable plan was worked out. The Go team is working on deploying an update to the “go” tool to add a -reuse flag, which should substantially reduce the traffic generated by this system for all users of Go. | 21:37:03 |
| @qbit:tapenet.org | https://sourcehut.org/blog/2023-01-09-gomodulemirror/ | 21:37:09 |
| 1 Feb 2023 |
 Sandro 🐧 | In reply to @adam:valkor.net
ok, here's another question. How can I deal with the improper module name in the go.mod? https://github.com/kovidgoyal/kitty/blob/5a997a5f7a3f28dec1f9675cd434ae6d2c92837a/go.mod#L1 haha, good joke | 13:40:02 |
| Sandro 🐧 | clone the repo and build in place but our tooling could break | 13:40:24 |
| @adam:valkor.net | It actually builds successfully with the improper name. | 13:59:03 |
| @adam:valkor.net | I was just coming here to post this for input and feedback. I kinda hate it, so am open to better ideas: https://github.com/NixOS/nixpkgs/pull/213978 | 13:59:24 |
| 2 Feb 2023 |
 hexa | https://go.dev/blog/go1.20 | 01:08:36 |
| hexa | looking forward to the primary go version bump 🙂 | 01:09:10 |
| @qbit:tapenet.org | ya! | 01:09:34 |
| hexa | (means 1.18 is eol now I think) | 01:09:41 |
| 8 Feb 2023 |
| @qbit:tapenet.org | https://github.com/golang/go/discussions/58409 | 21:50:34 |
| @qbit:tapenet.org | that's pretty gross | 21:50:47 |
| Sandro 🐧 | maybe we wait for 1.20.1 at least https://github.com/golang/go/issues/58370 | 23:53:08 |
| 9 Feb 2023 |
| @qbit:tapenet.org | ya, i think that's what zowoq was shooting for: https://github.com/NixOS/nixpkgs/pull/208706#issuecomment-1409663507 | 00:19:37 |
| 14 Feb 2023 |
|  Dandellion joined the room. | 04:06:13 |
| @qbit:tapenet.org | How do people feel about setting GOTELEMETRY=no by default (or patching out the telemetry stuff) if go proceeds to add it? | 15:12:55 |
 aaron | Strong agree. It can be controlled by a flag if the user wants to enable it, but it should default off. | 16:29:10 |
| 15 Feb 2023 |
|  @wtfiscrq:matrix.org joined the room. | 09:19:30 |
| Sandro 🐧 | In reply to @qbit:tapenet.org
How do people feel about setting GOTELEMETRY=no by default (or patching out the telemetry stuff) if go proceeds to add it? turn it off by default, yes. Probably only slows down the builds because we don't have internet access anway. | 12:48:22 |
| @qbit:tapenet.org | well, i specifically mean turning it off for the go tool in general | 12:57:45 |
| Sandro 🐧 | call the patch make-telemetry-more-gdpr-compliant 🙃 | 14:40:28 |
| @qbit:tapenet.org | lol | 14:40:40 |
| Sandro 🐧 | making it opt out is not allowed, either you need to be asked or it needs to be opt in | 14:40:53 |
| @qbit:tapenet.org | so making the go tool default to GOTELEMETRY=noand documenting that users need to opt in if they want to participate would be ok? :D | 14:41:43 |
| Sandro 🐧 | wouldn't be a problem for me but I don't have the final say | 14:46:39 |
