[pkg-nvidia-devel] r958 - in /packages/nvidia-graphics-modules/trunk/debian: changelog control.source rules

[Andreas Beckmann]

Russ Allbery wrote:
> anbe-guest at users.alioth.debian.org writes:
>>  binary-module-%: build binary-arch-meta
>>  	set -e; cd modules/nvidia-kernel$(legacy); \
>> -		KSRC=/usr/src/linux-headers-$* \
>> +		KSRC=/lib/modules/$*/build \
>>  			KVERS=$* \
>> -			KERNEL_DEPENDS=y \
>> +			KDREV=$(nks_debian_revision)+$(call get_package_version,linux-headers-$*) \
>>  			KPKG_DEST_DIR=../.. \
>>  			debian/rules binary_modules ; \

> Why this change?  I think it will always work with existing kernels, but
> so should the other version.  Or does this fix the problem with not
> finding the right kernel version number?

KSRC: make n-g-m behave more like m-a by passing the same value (no
functional change, the path directly in /usr/src works the same way)

KERNEL_DEPENDS: was obsolete, removed

KDREV: this is the place to do the magic with the version number, this
value is set by m-a, too, to the version (incl. debian revision) of the
kernel header package used.

Before:
  nvidia-kernel-2.6.32-5-amd64_195.36.24+0+2.6.32-5-amd64-0_amd64.deb
(useless duplication of 2.6.32-5-amd64)

After:
  nvidia-kernel-2.6.32-5-amd64_195.36.24+0+1.0anbe0+2.6.32-13_amd64.deb

The version can be decoded as follows:
  195.36.24+0+1.0anbe0+2.6.32-13
  ^           ^        ^
  |           |        linux-headers-2.6.32-5-amd64 (2.6.32-13)
  |           nvidia-kernel-source (195.36.24-1.0anbe0 -- because -2 was
  nvidia-graphics-modules (195.36.24+0)                   not yet there)

I'm not sure how this would work for binary NMUs, but eventually we
would get
  195.36.24+0+b42+2+2.6.32-14
                    ^ kernel was updated yesterday
                  ^ n-k-s amd64 was uploaded yesterday
             ^ the NMU suffix of the 42nd BinNMU

Just verified that it works this way.


Andreas