make-kpkg fails with "compatibility" errors
Hi,
On a mixed sid/ubuntu-edgy system I am having errors building the
ubuntu kernels from source. The kernel compile seems to go fine but
there are issues with make-kpkg and dh_* along these lines:
$ sudo make-kpkg --append-to-version=-suspend2 --initrd kernel-image
---[snip]-------------------------
if [ -x debian/post-install ]; then \
TMPTOP=/home/matt/src/ubuntu-2.6/debian/linux-image-2.6.19-rc6-ubuntu1-suspend2
STEM=linux version=2.6.19-rc6-ubuntu1-suspend2 \
IMAGE_TOP=/home/matt/src/ubuntu-2.6/debian/linux-image-2.6.19-rc6-ubuntu1-suspend2
debian/post-install; \
fi
dh_clean: Compatibility levels before 4 are deprecated.
dh_installdirs: Compatibility levels before 4 are deprecated.
grep: ../../../config/archmap: No such file or directory
Use of uninitialized value in string eq at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
dh_installdocs: Compatibility levels before 4 are deprecated.
Use of uninitialized value in string eq at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
dh_installchangelogs: Compatibility levels before 4 are deprecated.
dh_compress: Compatibility levels before 4 are deprecated.
dh_fixperms: Compatibility levels before 4 are deprecated.
dh_shlibdeps: Compatibility levels before 4 are deprecated.
Use of uninitialized value in string eq at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
dh_installdeb: Compatibility levels before 4 are deprecated.
Use of uninitialized value in string eq at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
Use of uninitialized value in string eq at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
dh_gencontrol: Compatibility levels before 4 are deprecated.
Use of uninitialized value in string eq at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
dpkg-gencontrol: error: package
linux-headers-2.6.19-rc6-ubuntu1-suspend2 not in control info
dh_gencontrol: command returned error code 65280
make: *** [install/linux-image-2.6.19-rc6-ubuntu1-suspend2] Error 1
---------------------------
Yesterday I ubilt a debian-based 2.6.18 kernel with no trouble. I
don't know what might cause these issues... anyway, thanks for any
help,
matt
Reply to: