Bug#345918: Possible solution
It appears that this has now been fixed in 2.6.15-3, the localversion file is now installed with the headers. I have tested it with the zaptel module and it now installs to the correct location. Can this bug be closed, or has it been left open for a reason? Richard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345918: Possible solution
Hi, I've looked at this bug and it appears that nothing is wrong with linux-headers. Nothing is wrong in that case means that we did not introduce any bugs compared to the previous versions, I've verified that zaptel driver behaves the same way under 2.6.14. It appears that most of the packages containing the source of third-party modules and using module-assistant prefer to install the modules into the package themselves, relying on the KVERS variable, which contains full version of the kernels (2.6.15-1-686 in this case). Some modules (like zaptel), however, use the modules_install target from the upstream Makefile, and that results in the problems described in the bug report. Since currently we don't have a clear policy on packaging the kernel modules (even though incidents like this get me more and more motivated to start working on one), it is arguable whether it's a bug of linux-headers or the zaptel-source package. I think we should be flexible and support both ways for installation, especially taking into account that the fix is pretty easy: adding a file 'localversion' containing the string -1-686 to the /usr/src/linux-headers-2.6.15-1-686/ directory fixes the problem. I'll bring up the issue on debian-kernel and see whether there will be any objections to such a change. Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345918: Possible solution
On Wed, Jan 04, 2006 at 08:30:11PM -0800, Jurij Smakov wrote: Hi, I've looked at this bug and it appears that nothing is wrong with linux-headers. Nothing is wrong in that case means that we did not introduce any bugs compared to the previous versions, I've verified that zaptel driver behaves the same way under 2.6.14. It appears that most of the packages containing the source of third-party modules and using module-assistant prefer to install the modules into the package themselves, relying on the KVERS variable, which contains full version of the kernels (2.6.15-1-686 in this case). Some modules (like zaptel), however, use the modules_install target from the upstream Makefile, and that results in the problems described in the bug report. Since currently we don't have a clear policy on packaging the kernel modules (even though incidents like this get me more and more motivated to start working on one), it is arguable whether it's a bug of linux-headers or the zaptel-source package. I think we should be flexible and support both ways for installation, especially taking into account that the fix is pretty easy: adding a file 'localversion' containing the string -1-686 to the /usr/src/linux-headers-2.6.15-1-686/ directory fixes the problem. I'll bring up the issue on debian-kernel and see whether there will be any objections to such a change. As said, i believe Bastian Blank was working on implementing just that last night. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
