Open GuillaumeSeren opened 4 years ago
iadegesso
commented
4 years ago My ebuild (genkernel-next-70-r1.ebuild) uses the newer busybox version (1.32) to fix the issue, not an older version... and the patch called in the ebuild is just to change the references in the package cache to this newer version...
And all works fine not only for me...
So...
Iade Gesso, PhD
iadegesso
commented
4 years ago My ebuild (genkernel-next-70-r1.ebuild) uses the newer busybox version (1.32) to fix the issue, not an older version... and the patch called in the ebuild is just to change the references in the package cache to this newer version...
And all works fine not only for me...
So...
Iade Gesso, PhD
You can find it here: https://github.com/iadegesso/howl-gentoo-overlay
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/719968I 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:
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:
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.