Hello, I am preparing to build a larger number of kernels using the git-bisect method. I would like to find a bug introduced somewhere between 2.6.17 and 2.6.19.2.
I would like to package these kernels with make-kpkg so that I can install and remove them easily. I want to have a single package where different versions correspond to different kernels, produced by git-bisect. packagename-1 == v2.6.17 packagename-2 == v2.6.19.2 packagename-3 == somewhere in the middle However I have problems using make-kpkg. It has some automatics inside and enforces rules on debian packagenames/versions, which both are unclear to me. I am experimenting with stuff like: MAKEFLAGS="CC=gcc-3.4 HOSTCC=gcc-3.4" make-kpkg --append-to-version 2.6.17 --revision 2.6-1.gitbisect -us -uc --initrd --rootcmd fakeroot kernel_image But I failed now several times at the end of the process. Could someone help me with the parameter --append-to-version XX --revision 2.6-1.gitbisect YY and the strings in debian/changecontrol ZZ? Or should I address this differently? regards Frank -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
