2.6.16-rc2 build failure - packaging problem
Hi,
I've tried to build 2.6.16-rc2 yesterday, using the orig.tar.gz from
Fredrik's page (people.debian.org/~fs), latest kernel-package and debian
dir from svn (dists/trunk or dists/exp, which Fredrik has created
recently). I ran into a problem: kernel-package ends up with a kernel
version like:
2.6.16-rc2-686-686
It is being called as
make -f debian/rules.real binary-arch-flavour FLAVOUR='686'
SOURCE_UPSTREAM='2.6.15+2.6.16-rc2' LOCALVERSION_HEADERS=''
KPKG_ABINAME='' UPSTREAM_VERSION='2.6.16-rc2'
SOURCE_VERSION='2.6.15+2.6.16-rc2-0experimental.1' VERSION='2.6.16'
KERNEL_HEADER_DIRS='i386' SUBARCH='none' ABINAME='rc2'
TYPE='kernel-package' LOCALVERSION='-686' ARCH='i386'
REVISIONS='0experimental.1'
[..]
cd 'debian/build/build-i386-none-686'; env -u ABINAME -u ARCH -u SUBARCH
-u FLAVOUR -u VERSION DEBIAN_LOCALVERSION='-rc2-686'
DEBIAN_LOCALVERSION_HEADERS='-rc2' DEBIAN_VERSION='2.6.16' MAKEFLAGS=''
make-kpkg --append-to-version '-686' --arch 'i386' --stem linux --initrd
configure
exec make -f /usr/share/kernel-package/ruleset/minimal.mk debian
APPEND_TO_VERSION=-686 KPKG_ARCH=i386 KPKG_STEM=linux INITRD=YES
Most probably the problem arises due to the fact that there is
APPEND_TO_VERSION, which make-kpkg appends, but then LOCALVERSION is
interpreted too, and added to version. 2.6.15 does not seem to have this
problem, so it appears that LOCALVERSION handling changed somehow since
then? I'm pretty sure that renaming the LOCALVERSION variable or
preventing it from being passed to make-kpkg call will fix the problem.
Since such a change has a great potential for breaking things, I am asking
for advice :-).
Best regards,
Jurij Smakov jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
Reply to: