Manoj Srivastava <[EMAIL PROTECTED]> writes: > On Sun, 18 Feb 2007 18:04:50 +0100, Frank Hartmann <[EMAIL PROTECTED]> > said: > >> 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? > > Can you post the error message?
Hello Manoj, Not verbatim, its gone now. It said something about a mismatch of the part marked below in debian/changelog linux-source-2.6.172.6.17 (2.6-1.gitbisect) unstable; urgency=low ( ^^^^^^^^^^^^^^) versus 2.6.17, which was not part of cmd line parameters, but seemed to be derived from the kernel itself (version.h). This experience, was not done with the posted cmdline, but was the result of one of my many trials in the 3 hours before posting. I tried at least the following variants 434 MAKEFLAGS="CC=gcc-3.4 HOSTCC=gcc-3.4" make-kpkg --revision 2.6-v2.6.17 -us -uc --initrd --rootcmd fakeroot kernel-image 436 MAKEFLAGS="CC=gcc-3.4 HOSTCC=gcc-3.4" make-kpkg --revision 2.6-v2.6.17 -us -uc --initrd --rootcmd fakeroot kernel-image 439 MAKEFLAGS="CC=gcc-3.4 HOSTCC=gcc-3.4" make-kpkg --revision 2.6-2.6.17-fjh -us -uc --initrd --rootcmd fakeroot kernel-image 440 MAKEFLAGS="CC=gcc-3.4 HOSTCC=gcc-3.4" make-kpkg --revision 2.6-1.v2.6.17 -us -uc --initrd --rootcmd fakeroot kernel-image I do not have debian/changecontrol in a SCM system, so I lost track what was in it. Sorry. The cmdline from my previous email 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', works in fact. I discouvered this 20 minutes after sending out my email. The only drawback is, that it created linux-image-2.6.172.6.17_2.6-1.gitbisect_i386.deb which is a strange looking name. dpkg -l gives: ii linux-image-2.6.172.6.17 2.6-1.gitbisect Linux kernel binary image for version 2.6.172.6.17 I noticed too, that the beginning of a line in debian/changecontrol was modified by make-kpkg linux-source-2.6.172.6.17 (2.6-1.gitbisect) unstable; urgency=low ^^^^^^^^^^^^^^^^^^^^^^^^^ and was something different in my editor. Is this as expected? I think I can work with the current approach. But I still feel slightly confused. regards Frank -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]