Installed: genkernel-3.4.1 and gentoo-sources-2.6.18-r1 Using 'genkernel --menuconfig all' I specified "CONFIG_LOCAL_VERSION=-mine" to distinguish my kernel. I expected the new kernel to be called ernel-genkernel-x86-2.6.18-gentoo-r1-mine, but it's called kernel-genkernel-x86-2.6.18-gentoo-r1 This is wrong, is it not?
Not baselayout (and it works just fine here).
Upgrade to 3.4.6 instead, it's already fixed there.
The latest genkernel is 3.4.4 (not 3.4.6) and is not quite right. Here's my latest output: * Gentoo Linux Genkernel; Version 3.4.4 * Running with options: all * Linux Kernel 2.6.18-gentoo-r1-11132.6.18-gentoo-r1-osage for x86... * config: Using config from /usr/share/genkernel/x86/kernel-config-2.6 * Previous config backed up to .config.bak * >> Running oldconfig... * kernel: >> Cleaning... * config: >> Invoking menuconfig... # # configuration written to .config # *** End of Linux kernel configuration. *** Execute 'make' to build the kernel or try 'make help'. * >> Compiling 2.6.18-gentoo-r1-1113 bzImage... The "compiling" line is what I want, but the "Linux Kernel" line seems to have strung 2 versions together. Also, my Makefile has: VERSION = 2 PATCHLEVEL = 6 SUBLEVEL = 18 EXTRAVERSION = -gentoo-r1-1113 NAME=Avast! A bilge rat! and /etc/kernels/kernel-config-x86-2.6.18-gentoo-r1-1113 had CONFIG_LOCALVERSION="" It appears that the "-osage" was pulled in from /etc/kernels/kernel-config-x86-2.6.18-gentoo-r1-2 as that's presently the only file with CONFIG_LOCALVERION="-osage" So, some details aren't quite right...
root@moon_gen_2:~# zcat /proc/config.gz |grep CONFIG_LOCAL_VERSION root@moon_gen_2:~# zcat /proc/config.gz |grep VERSION CONFIG_LOCALVERSION="-Gentoo-moon_12" CONFIG_LOCALVERSION_AUTO=y CONFIG_MODVERSIONS=y CONFIG_MODULE_SRCVERSION_ALL=y root@moon_gen_2:~# So, when initial reports mentions > I specified "CONFIG_LOCAL_VERSION=-mine" to I am not surprised there is a bug ... the bug may be in still in genkernel: there is one more underscore in genkernel option. Any way, I always change this feature manually during menuconfig, and never had any problem. David Relson, please test your bug on new release, and close the bug if it has been fixed as said in comment 2 !
Well, this is reported as FIXED, so marking as such. If there's still a problem, feel free to REOPEN the bug.