On Sun, 16 Feb 1997, Jesse Goldman wrote: > I've run into a snag making a kernel package for version 2.0.29. I got > new sources, patched them, did a "make-kpkg clean" and then a "make-kpkg Why patch the new sources? I thought you only needed to patch if you had 2.0.28 sources and wanted to upgrade to 2.0.29. Anybody??
> --rev 2.0.29 kernel-image." Everything goes along fine until the very end > which looks like this: > > cp arch/i386/boot/bzImage \ > debian/tmp-image/boot/vmlinuz-2.0.29 > cp vmlinux debian/tmp-image/boot/vmlinux-2.0.29 > cp System.map debian/tmp-image/boot/System.map-2.0.29 > chmod 644 debian/tmp-image/boot/vmlinuz-2.0.29 \ > debian/tmp-image/boot/vmlinux-2.0.29 \ > debian/tmp-image/boot/System.map-2.0.29 > dpkg-gencontrol -pkernel-image-2.0.29 -Pdebian/tmp-image/ > parsechangelog/debian: error: badly formatted trailer line, at changelog > line 6 > dpkg-gencontrol: error: syntax error in parsed version of changelog at > line 0: empty file > make: *** [stamp-image] Error 29 It looks like you new kernel was made after all. I would copy it to the right place /boot/vmlinuz and use it. I think your problem may have a lot to do with the patching. /************************************************************************/ D.J. Mashao, [EMAIL PROTECTED], -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
