sys-kernel/ck-sources-3.2.2 installs correctly into /usr/src/linux-3.2.2-ck, but installs modules into /lib/modules/3.2.1-ck. uname -r identifies running kernel as 3.2.1-ck as well. Reproducible: Always Steps to Reproduce: 1.emerge sys-kernel/ck-sources-3.2.2 2.confirm /usr/src/linux symlink points to /usr/src/linux-3.2.2-ck 3.configure the kernel options; then build the kernel 'make && make modules_install' Actual Results: /usr/src directory is correct /lib/modules/3.2.1-ck is inconsistently named uname -r yields wrong kernel version no loss of functionality, but could be confusing with multiple kernels installed Expected Results: modules to be installed into /lib/modules/3.2.2-ck uname -r to show kernel version 3.2.2-ck
Same here. Last line of output of #make modules_install … DEPMOD 3.2.1-ck
I'm sorry about this mess, the problem was that genpatches sets the version and what I've named 3.2.2 was in fact 3.2.1, so I removed the incorrectly versioned 3.2.2, added proper 3.2.1 along with correct genpatches. You need to remove current 3.2.2 ck-sources and "downgrade" to 3.2.1 to fix this. Thank you for the report.
Krzysztof, if you told me that >=3.2.3 will be happening say, next month, I'd be inclined to leave my system as is for now and wait, since I can't seem to find any loss of functionality the way it is. Unless you tell me that weird breakage will occur leaving it this way?
(In reply to comment #3) > Krzysztof, if you told me that >=3.2.3 will be happening say, next month, I'd > be inclined to leave my system as is for now and wait, since I can't seem to > find any loss of functionality the way it is. > > Unless you tell me that weird breakage will occur leaving it this way? No, there is no breakage - it's just version mismatch: directory in /usr/src tells you that's 3.2.2, but the kernel inside identifies itself as 3.2.1.
not all fixed yet. despite the fact that the downgrade was successful, portage doesn't know about it. when i run "qlist ck-sources", i get a bunch of listings for files in /usr/src/linux-3.2.2-ck/. the problem is that there's no such directory in /usr/src; there's only the 3.2.1 dir along with the linux -> symlink to it. so, when running "emerge -P", portage uninstalls 3.2.1 every time, because it thinks 3.2.2 is still installed. i've cleaned out my worldfile to ensure that only 3.2.1 is listed, and made sure there are no other lingering 3.2.2 files. so this rename/revert commit didn't fix all the problems introduced by the bad version.
Yes Josh, you're correct. p.masking the 3.2.2 would probably solve this as portage would warn about masked package being installed. This should be fixed now as I've just added 3.2.5.
