[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

linux-image-2.6-amd64 strangeness?



Howdy,

A backport novice here. I have a system tracking the new kernels for kvm.

I notice (to my untrained eye) something is odd with the kernel meta package. Is this a timing issue, or is something awry? Also any rt*m welcomed with a pointer please ;-)

Berni /enclosed:


> The meta package:

aptitude show linux-image-2.6-amd64/lenny-backports
Package: linux-image-2.6-amd64
State: installed
Automatically installed: no
Version: 2.6.32+25~bpo50+1
Priority: optional
Section: kernel
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Uncompressed Size: 32.8k
Depends: linux-image-2.6.32-bpo.3-amd64
Provides: linux-latest-modules-2.6.32-bpo.3-amd64
Description: Linux 2.6 for 64-bit PCs
This package depends on the latest Linux kernel 2.6 and modules for use on PCs
 with AMD64 or Intel 64 processors.

 This kernel also runs on a Xen hypervisor.  It supports only unprivileged
 (domU) operation.

> Breakage ????

aptitude show linux-image-2.6.32-bpo.3-amd64/lenny-backports
Unable to find an archive "lenny-backports" for the package "linux-image-2.6.32-bpo.3-amd64"

> Interesting, the next version is there ready and waiting :-) ???

aptitude show linux-image-2.6.32-bpo.4-amd64/lenny-backports
Package: linux-image-2.6.32-bpo.4-amd64
New: yes
State: not installed
Version: 2.6.32-11~bpo50+1
Priority: optional
Section: kernel
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Uncompressed Size: 101M
Depends: module-init-tools, linux-base (>= 2.6.32-11~bpo50+1), initramfs-tools
         (>= 0.55) | linux-initramfs-tool
PreDepends: debconf | debconf-2.0
Recommends: firmware-linux-free (>= 2.6.32)
Suggests: linux-doc-2.6.32, grub | lilo
Conflicts: initramfs-tools (< 0.55)
Provides: linux-image, linux-image-2.6, linux-modules-2.6.32-bpo.4-amd64
Description: Linux 2.6.32 for 64-bit PCs
 The Linux kernel 2.6.32 and modules for use on PCs with AMD64 or Intel 64
 processors.

 This kernel also runs on a Xen hypervisor.  It supports only unprivileged
 (domU) operation.

Reply to: