Package: debian-installer When a pseudo-package is detected util/pkg-list builds a list of providing packages, but currently it does not check if such providing packages are valid.
There are at least two cases where this could/does cause problems: - wrong kernel flavor gets included for kernel module udebs - udeb is not valid for a subarch Example of the first is 'qcontrol-udeb Depends: input-modules'. This results in: pkg-lists: adding qcontrol-udeb pkg-lists: collecting dependencies for qcontrol-udeb pkg-lists: postponed satisfying dep on input-modules-2.6.25-2-ixp4xx-di | input-modules-2.6.25-2-orion5x-di for qcontrol-udeb [...] pkg-lists: adding input-modules-2.6.25-2-ixp4xx-di (chosen at random out of input-modules-2.6.25-2-ixp4xx-di input-modules-2.6.25-2-orion5x-di) pkg-lists: collecting dependencies for input-modules-2.6.25-2-ixp4xx-di pkg-lists: added kernel-image-2.6.25-2-ixp4xx-di for input-modules-2.6.25-2-ixp4xx-di pkg-lists: collecting dependencies for kernel-image-2.6.25-2-ixp4xx-di pkg-lists: added usb-modules-2.6.25-2-ixp4xx-di for input-modules-2.6.25-2-ixp4xx-di pkg-lists: collecting dependencies for usb-modules-2.6.25-2-ixp4xx-di pkg-lists: added kernel-image-2.6.25-2-ixp4xx-di for usb-modules-2.6.25-2-ixp4xx-di It should be possible to filter out such cases in pkgdeps() based on info available from apt-cache.
signature.asc
Description: This is a digitally signed message part.
