Manoj Srivastava <[EMAIL PROTECTED]> writes:
> You could try: --append-to-version -foo, which will create:
> linux-image-2.6.17-foo.
>
>
>> 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
>
> You probably mean debian/changelog
>
>> linux-source-2.6.172.6.17 (2.6-1.gitbisect) unstable; urgency=low
>> ^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Which is the package name from above.
>
>> I think I can work with the current approach. But I still feel
>> slightly confused.
>
> Hope this clears it up a bit.
Hi Manoy,
I am still confused, not by your explanation, but by the behaviour of
the process.
I was able to build this package:
linux-image-2.6.18ebdea46fecae40c4d7effcd33f40918a37a1df4b_2.6-1.gitbisect_i386.deb
MAKEFLAGS="CC=gcc-3.4 HOSTCC=gcc-3.4" make-kpkg --append-to-version
ebdea46fecae40c4d7effcd33f40918a37a1df4b --revision 2.6-1.gitbisect -us -uc
--initrd --rootcmd fakeroot kernel_image
but I this gives an error:
MAKEFLAGS="CC=gcc-3.4 HOSTCC=gcc-3.4" make-kpkg --append-to-version
8c6270f957f0eaa343e4a609159c4b85038468d6 --revision 2.6-1.gitbisect -us -uc
--initrd --rootcmd fakeroot kernel_image
...
po2debconf debian/templates.master > debian/templates
install -p -m 644 ./debian/templates.master
/home/frank/tmp/linux-2.6/debian/linux-image-2.6.198c6270f957f0eaa343e4a609159c4b85038468d6/DEBIAN/templates
dpkg-gencontrol -DArchitecture=i386 -isp \
-plinux-image-2.6.198c6270f957f0eaa343e4a609159c4b85038468d6
-P/home/frank/tmp/linux-2.6/debian/linux-image-2.6.198c6270f957f0eaa343e4a609159c4b85038468d6/
dpkg-gencontrol: error: package
linux-image-2.6.198c6270f957f0eaa343e4a609159c4b85038468d6 not in control info
make[1]: ***
[debian/linux-image-2.6.198c6270f957f0eaa343e4a609159c4b85038468d6] Error 255
make[1]: Leaving directory `/mnt/hdd2/home/frank/tmp.nobackup/linux-2.6'
make: *** [binary/linux-image-2.6.198c6270f957f0eaa343e4a609159c4b85038468d6]
Error 2
debian/changelog for successful build
linux-source-2.6.18ebdea46fecae40c4d7effcd33f40918a37a1df4b (2.6-1.gitbisect)
unstable; urgency=low
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
autogenerated by make-kpkg
debian/changelog for failing build
linux-source-2.6.20 (2.6-1.gitbisect) unstable; urgency=low
^^^^^^^^^^^^^^^^^^
no modification by make-kpkg
are there some rules for the -append-to-version parameter in relation to
debian/changelog?
regards
Frank
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
