Hi,
Please explain why e.g. KOTD head used from a normal leap 42.1 at the moment gave me some 4.6.0-3.1 or something a few days ago and today it likes me to upgrade it to 4.6.0-4.1 or something.
Why are there recompiles? Isnt the actual 4.6 kernel by the kernel.org folks finished? Arent any fixes coming to this kernel then called higher and later kernel versions e.g. 4.6.1 or something?
Or is there more to this than a mere recompile? Are there backports or fixes from .3-1 to .4-1? Where can I find about any of this and how this all fits together and the reasoning behind these procedures and happenings?
TY
On Sat, May 28, 2016 at 04:10:59PM +0200, cagsm wrote:
Hi,
Please explain why e.g. KOTD head used from a normal leap 42.1 at the moment gave me some 4.6.0-3.1 or something a few days ago and today it likes me to upgrade it to 4.6.0-4.1 or something.
Why are there recompiles? Isnt the actual 4.6 kernel by the kernel.org folks finished? Arent any fixes coming to this kernel then called higher and later kernel versions e.g. 4.6.1 or something?
Or is there more to this than a mere recompile? Are there backports or fixes from .3-1 to .4-1? Where can I find about any of this and how this all fits together and the reasoning behind these procedures and happenings?
We apply patches on top of this kernel.
Or configuration changes like this recent one commit b829bc700eb18f7cd1ef48d42964555e9e9f2357 Author: Dirk Mueller dmueller@suse.com Date: Wed May 25 22:08:51 2016 +0200
Set CONFIG_NET_XGENE=y as a workaround for (bsc#973756)
which will cause a new release number.
Ciao, marcus
On Sat, May 28, 2016 at 5:05 PM, Marcus Meissner meissner@suse.de wrote:
We apply patches on top of this kernel. Or configuration changes like this recent one commit b829bc700eb18f7cd1ef48d42964555e9e9f2357 Author: Dirk Mueller dmueller@suse.com Date: Wed May 25 22:08:51 2016 +0200 Set CONFIG_NET_XGENE=y as a workaround for (bsc#973756) which will cause a new release number. Ciao, marcus
Thank you for explaining.
-
cagsm -
Marcus Meissner