On Sun, 2011-06-05 at 21:23 -0500, Jonathan Nieder wrote: [...] > + <p> > + To start, recreate the problem with a vanilla kernel: > + <example> > +# apt-get install git build-essential > +$ git clone > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git > +$ cd linux-2.6 > +$ make localmodconfig; # minimal configuration > + </example> > + The above commands acquire and configure a vanilla kernel. > + Build and test a binary package as explained in > + <ref id="common-building">: > + <example> > +$ make KDEB_PKGVERSION=bisecting.1.0 deb-pkg [...]
This is not a valid Debian package version, and dpkg-deb will reject it. But dpkg-deb will print the generated package names at the end of the 'make deb-pkg' output, e.g.: dpkg-deb: building package `linux-headers-3.0.0-rc1+' in `../linux-headers-3.0.0-rc1+_3.0.0-rc1+-1_amd64.deb'. dpkg-deb: building package `linux-libc-dev' in `../linux-libc-dev_3.0.0-rc1+-1_amd64.deb'. dpkg-deb: building package `linux-image-3.0.0-rc1+' in `../linux-image-3.0.0-rc1+_3.0.0-rc1+-1_amd64.deb'. So you can say 'install the package(s) that this generates'. And note that the version is incremented each time. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
