sys-kernel/genkernel-next fail to build with glibc-2.31 #90
Description
Hello,
Sorry to report this late, but been busy lately.
This issue was reported in gentoo bugtracker on 2020-04-28 23:10,
here the link: https://bugs.gentoo.org/719968
I discovered the issue, later when it was decided to mask the package,
on 2020-07-11 15:40:41, and as I use it on all my machine I asked more informations.
I was told:
- There is a maintainer issue on the gentoo side, so it was proposed to be proxy-maintained.
- The genkernel-next project stopped moving and merging code, since
2018-12-22 10:41:23, so quite some time.
So there a patch in the bugtracker, which force the use of an old busybox version,
but it won't solve the problem for me, and I don't really like it.
Here the details I gathered:
- glibc-2.31 deprecated stime() and replace it with clock_settime() (https://bugs.gentoo.org/708350)
- This function is used in busybox so the patch should probably be there (https://git.busybox.net/busybox/patch/?id=d3539be8f27b8cbfdfee460fe08299158f08bcd9)
So I don't think the patch should be in genkernel-next,
it can be a workaround with the package or fixed a bit cleaner by patching busybox (sensitive package),
in the end the patch for busybox is in 1.32 release (https://git.busybox.net/busybox/commit/?h=1_32_stable&id=d3539be8f27b8cbfdfee460fe08299158f08bcd9).
I think the mask / removal could have been avoided with some maintainer research and communication with upstream.
So I wanted to share this with you (the upstream) and all other genkernel-next users.
Also I want to propose my help on the project to sort / review PR, and hopefully merge code again.