Package: kernel-image-netbootable Severity: normal it seems the kernel dependencies for several "tested" architectures depend on virtual kernel packages that could be satisfied by nearly any kernel available for the architecture.
from the rules file:
DEB_NETBOOT_DEPENDS_mipsel = genext2fs, kernel-image-2.4 | kernel-image-2.6 |
kernel-image-netboot
DEB_NETBOOT_DEPENDS_hppa = kernel-image-2.6 | kernel-image-2.6smp |
kernel-image | kernel-image-netboot
DEB_NETBOOT_DEPENDS_ia64 = kernel-image-2.6 | kernel-image |
kernel-image-netboot
DEB_NETBOOT_DEPENDS_sparc = kernel-image-2.6 | kernel-image |
kernel-image-netboot
kernel-image-2.6, kernel-image-2.4 and kernel-image are all virtual
packages that do not provide a specific kernel, and i suspect that all
the possible kernels that provide these virtual packages have not been
tested- so it seems a poor idea to consider these kernels "known to work
with initrd-netboot-tools"
in the past, you (jonas) have objected to my requests to include such
broad-reaching virtual packages in the dependencies.
if allowing such broad-reaching virtual kernel packages to satisfy
dependencies on some architectures, i do not understand why "untested"
and "tested" architectures do not also specify:
Depends: ${Depends:netbootable} | kernel-image-2.4 | kernel-image-2.6 |
kernel-image
beyond that, it means that this package will fail to install on those
architectures unless a kernel is installed, rather than pulling in a
kernel, such that:
apt-get install kernel-image-netbootable
will result in a long list of possible kernels, rather than installing a
kernel capable (combined with initrd-netboot) of network boot.
live well,
vagrant
-- System Information:
Debian Release: 3.1
Architecture: i386 (i586)
Kernel: Linux 2.6.8-2-386
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
signature.asc
Description: Digital signature
