Re: dpkg and custom kernels ( was: report of upgrade bo -> hamm )

[Manoj Srivastava <srivasta@datasync.com>]

Hi,

	I missed the start of this discussion, so this may not be
 really germane to the issue. 

	The reason, I think, that dpkg upgrades the custom kernel with
 a new standard kernel is that the new standard kernel comes with an
 epoch; hence making it preferable in dpkg's eyes over _all_ non
 epoched versions. 

	The solution, for the future, is to put an defensive epoch on
 the custom kernel (kernel-package allows you to do so: 
    --revision 1:custom.Y); however, the solution is admitedly ugly. I
 wish there had been no epochs on standard kernels ;-), however, since
 each new kernel version is a new package, at least the epoch won't be
 carried around for ever.

	manoj
-- 
 Computers are the most fun you can have with anything that isn't
 breathing. Bruce Walker, CACM Forum
Manoj Srivastava  <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .