00:09:45 sommerfeld: I've met another similar error, but for "network/bridge/build/i86/.built" 00:09:59 when did "gmake -n build" 00:30:06 head is oi/hipster , commit 00f7f4327ca7361dc28a29253f87530b26994778 02:56:06 vetal: that makefile hasn't been touched since 2018. likely requires fixes like the uwimap Makefile 13:28:31 wacki: I mean when release tag is set, in general it requires that whole things under that tag are rebuilt. And result artefacts placed to repository. 14:12:37 sommerfeld: Did you mean if I prepare a fix, you will apply it? 14:28:15 vetal_: I don't have the authority to apply it. 14:30:43 if you submit a well-formed pull request that fixes build breakage one of the maintainers would likely merge it. 14:41:19 @vetal_: We don't do that because of resource constraints. Whole OI is maintained by just a few people on a single server. Most people have only limited interests in a few packages they maintain. 14:43:17 Or simply put: I cannot do that because I am almost alone. 14:44:39 Of course you (and everybody else) can fix or enhance things and create a PR for it. If it looks good, builds and publishes for me, I will most likely merge it. 15:49:43 sommerfeld: Excellent! 15:50:58 wacki: Got it. That explains why I met errors during build. Probably I will have some time to help in that. Thanks! 19:40:09 Changing the default compiler to gcc-14 alone broke a lot of builds because many warnings of the past are errors now. 19:41:07 Then you can have all sorts of fun with new versions of a package that break others in subtle (and no so subtle) ways. 19:41:50 Because almost nobody but me checks PR's many problems will only be detected by users. 19:43:12 I have tried to wait for comments on PR's in the past but that mostly was pointless as very seldom someone looked at them. 20:39:57 gcc-15 (released earlier today) may break some more by changing the default to C23 - easy workaround is compiling with -std=c17 instead 20:40:21 https://gcc.gnu.org/gcc-15/porting_to.html