Comment 5 for bug 757338

Mh. Actually I don’t know which package is at fault here, but I tend towards d-i.

linux-generic depends on linux-image-generic, linux-restricted-modules-generic

linux-restricted-modules-generic is obviously not in main
linux-generic apparently is in restricted for hardy but in main for hardy-updates (this would be a Policy violation in Debian)

d-i installs linux-generic whereas installing linux-image-generic would (at _that_
poing in time during installationi) would be enough.

On the other hand, what I’d _really_ want to know is, why did it stop working,
i.e. what changed? We have been using the network installer for years, and it
only got uninstallable some days ago (can’t exactly pinpoint it because we’re
not installing computers every day).

Most puzzling (to me) is why hardy-updates is used during the installation
process, instead of installing hardy (+hardy-security, if it must be) first,
_then_ writing the final in-target etc/apt/sources.list and dist-upgrading.
But then, I don’t know the inner workings of d-i well (and d-i *is* not being
happily welcomed even in the greater debian community)…

Anyway, like I said, I managed to get the pressing need to install it done
with a workaround (enable restricted early), so this is mostly for curiosity
and possibly other people who run into the problem…