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

[Joost Kooij <kooij@mpn.cp.philips.com>]

On 22 Oct 1997, Manoj Srivastava wrote:

> 	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.

Could you make the epoch a standard feature of kernel-package? 

If /etc/kernel-pkg.conf gets a switch that sets the default epoch level,
then the maintainer of the distribution kernel-{source,image}s can
configure his kernel-package to use an epoch that is always lower than the
one that is used by default, thus keeping dselect from wanting to
"upgrade". 

Cheers,


Joost


--
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 .