Crash while upgrading kernel & stable releases

[Markus Kolb]

Matt Zimmerman wrote on Mon, Jun 20, 2005 at 12:58:52 -0700:
> On Mon, Jun 20, 2005 at 05:42:27PM +0200, Markus Kolb wrote:
> 
> > But there is no dependency on metapackage in linux-kernel-package and
> > the metapackage is not updated the way it should be to support
> > kernel-updates the way you want, I think.
> > Else, nothing would be against another package name on security updates
> > ;)
> 
> I don't know what you mean; there is in fact exactly such a metapackage and
> has been since before the first Ubuntu release.

No the metapackage doesn't do this:

Installed kernel: linux-X-686-release_version
Metapackage_0 requires linux-X-686-release_version
linux-X-686-release_version requires Metapackage_0

There is a new patched kernel.
So new linux-X-686-fix1_version package.
Metapackage is updated to new package version Metapackage_1

Metapackage_1 requires linux-X-686-fix1_version.
Metapackage_1 suggests linux-X-686-release_version
linux-X-686-fix1_version requires Metapackage_1

On update Metapackage_0 is updated with Metapackage_1 which requires
linux-X-686-fix1_version which is installed parallel to old
linux-X-686-release_version.

So you have two linux-kernel packages installed because of the update
until you delete the old linux-X-686-release_version yourself.

This can be continued with each new kernel update.
The package version of the linux kernel packages can be recognized for
some stuff but need not anymore.

In your other mail it seems you don't know why anyone wants to have the
old kernel available after the kernel update.

There are many possibilities where a kernel update isn't finished
succesful. It need not to be bug or a crashed machine. Anyone switches
off the computer during installation of the new package or the power
is lost. 
With the left old kernel you can boot and run the update again.
When old kernel was deleted  and the installation of update has not
finished you can not boot because there is no kernel available.