Is there any way to add something to kernel-pkg.conf to achieve this? I know I'll forget to use the --revision option someday.
On Sep 18, Bob Nielsen ([EMAIL PROTECTED]) wrote: > Apparently kernel-image-2.2.17-1 uses an epoch, so apt (or dselect) > wants to replace your image with that one. This happened at least once > before and the way to avoid the problem is to use an epoch yourself > when creating the package: > > make-kpkg --revision=3:custom.1.0 kernel_image > > /usr/share/doc/kernel-package/README.gz has some discussion of this. > > Bob > > On Mon, Sep 18, 2000 at 09:45:01PM -0400, Joel Dinel wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > I just compiled kernel 2.2.17 today with the kernel-package tools. I > > installed the resulting kernel-image-2.2.17_custom1.0_i386.deb with > > dpkg -i. > > > > Everything is OK. Now, as soon as I apt-get > > update && apt-get dist-upgrade, apt wants to install a newer version > > of kernel-2.2.17 (kernel-image-2.2.17-1). I don't want that. I just > > spent a lot of time customizing and tailoring my kernel to my > > needs, and I don't feel like replacing it by a stock kernal and have a lot > > of things break down upon reboot. > > > > How do I prevent apt from upgrading my kernel > > package ? I looked into dpkg's MAN pages, and there is something about > > putting a package on HOLD to prevent update. This is what I would want to > > do. > > > > I must've recompiled 2.2.16 at least 10 times using the same method > > (kernel-package), and apt never tried to update my kernel on me before. > > > > Any tips ? This is dribing me nuts. I can't do a succesful apt-get > > dist-upgrade anymore, since apt wants to install 2.2.17-1 everytime. > > > > Thanks ! > > > > > > Joel Dinel > > [EMAIL PROTECTED] -- Neil L. Roeth [EMAIL PROTECTED]
