I am trying to build debian packages for the latest stable kernel version
(2.6.16) and I get the following error :

The UTS Release version in include/linux/version.h
"2.6.16-own"
does not match current version:
"2.6.16-own"
Please correct this.
exit 2
make: *** [modules_clean] Error 2


What does this mean ? I am using the same command line as I have used for
all my debian kernel compiles in the past.

make-kpkg --append_to_version "-own" clean; make-kpkg --append_to_version
"-own" kernel_source kernel_headers kernel_manual kernel_image
modules_clean modules_image

Does the new kernel need to be installed and running before any of the
modules are compiled ? Is this new with kernel 2.6.16 ?


GC

Grant wrote:

> On Wed, 22 Mar 2006 23:37:16 -0500, Geico Caveman <spam@spam.invalid>
> wrote:
>
>>The UTS Release version in include/linux/version.h
>> "2.6.16-own"
>>does not match current version:
>> "2.6.16-own"
>>Please correct this.
>>exit 2
>>make: *** [modules_clean] Error 2
>
> What command gives that error?
>
> Grant.

The command line I included in my previous post (one that I have used for
ages) :

make-kpkg --append_to_version "-own" clean; make-kpkg --append_to_version
"-own" kernel_source kernel_headers kernel_manual kernel_image
modules_clean modules_image

A look at the generated packages indicates that the following are
generated :

linux-doc-2.6.16-own_2.6.16-own-10.00.Custom_all.deb
linux-headers-2.6.16-own_2.6.16-own-10.00.Custom_i386.deb
linux-image-2.6.16-own_2.6.16-own-10.00.Custom_i386.deb
linux-manual-2.6.16-own_2.6.16-own-10.00.Custom_all.deb
linux-source-2.6.16-own_2.6.16-own-10.00.Custom_all.deb

So, I am guessing that this occurs after the kernel_image target is
processed, and fails at modules_clean (which is what the error message in
my post indicates).

To confirm this, I issued the following command :

make-kpkg --append_to_version "-own" modules_clean modules_image

Surprisingly, the error above went away. But a large majority of the modules
failed to compile against this new kernel. Now, it is possible that that is
happening because the kernel is new and has made some changes that the
source packages have not yet incorporated, but the ghost error that seems
to occur sometime before modules_clean and after generation of the kernel
image is strange. I am assuming that the target kernel_image concludes
after the generation of the kernel image, but this above set of
circumstances would seem to indicate that this is not the case.

Puzzling.