"Hukadan" <m...@hukadan.org> writes: > On Fri Mar 7, 2025 at 12:27 AM CET, Stuart Henderson wrote: >> On 2025/03/06 19:48, Philip Kaludercic wrote: >> > Stuart Henderson <s...@spacehopper.org> writes: >> > >> > > On 2024/07/31 16:32, Stuart Henderson wrote: >> > >> Ok with you, Hukadan? >> > >> >> > >> https://marc.info/?l=openbsd-ports&m=172226686214725&w=2 >> > > >> > > tb@ pointed out that this breaks with go-1.23rc2: >> > > >> > > # github.com/superseriousbusiness/gotosocial/cmd/gotosocial >> > > link: codeberg.org/gruf/go-fastcopy: invalid reference to >> > > io.errInvalidWrite >> > > >> > > This can be worked around with the following snippet: >> > > >> > > # disable https://go.dev/doc/go1.23#linker to unbreak with go-1.23rc2. >> > > # remove either if codeberg.org/gruf/go-fastcopy is fixed, or "existing >> > > # usages of //go:linkname found in a large open-source code corpus >> > > # remain supported" is extended. >> > > MODGO_LDFLAGS += -checklinkname=0 >> > > >> > > That part can't be committed before go-1.23, and I doubt it would be >> > > needed for long, gotosocial is actively developed. >> > >> > Sorry to ping this thread again, but I don't remember what the result >> > was and there has since been an apparently important security release >> > https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.17.4 >> > that might be nice to have in ports before the next release of OpenBSD? >> >> If I understand correctly GTS doesn't run properly on OS without coherent >> file + mmap access (i.e. unified buffer cache) any more, so we should >> probably delete the port.. > > Hi, > > @Philip, following this thread, I provided a diff a while ago (at that time to > update to 0.17.1). > > I do not use this port anymore. I don't feel confident in being able > to maintain > it, especially without being able to test it properly.
I have an active server that I would like to keep on using. If I have to figure out how to fix whatever issues gotosocial has on OpenBSD, I am happy to share these findings here (IIRC the mmap issue was related gotosocial bundling ffmpeg and some other tools in wasm form, which we don't have to do). Sadly I am not familiar with the inner workings of the ports system, so I would appreciate any pointers here. > @Stuart, I agree, I have no objection on my side. > > Regards, > > Hukadan
