Bug#289900: Installation seems to clash with kernel-headers-2.6.10-1-686
Package: kernel-image-2.6.10-1-686
Version: 2.6.10-3
Severity: minor
Hi,
I've selected both kernel-headers and kernel-image-2.6.10-1-686 for
installation today, and ended up with a warning I know for long:
Selecting previously deselected package kernel-headers-2.6.10-1.
Unpacking kernel-headers-2.6.10-1 (from
.../kernel-headers-2.6.10-1_2.6.10-3_i386.deb) ...
Selecting previously deselected package kernel-headers-2.6.10-1-686.
Unpacking kernel-headers-2.6.10-1-686 (from
.../kernel-headers-2.6.10-1-686_2.6.10-3_i386.deb) ...
Selecting previously deselected package kernel-image-2.6.10-1-686.
Unpacking kernel-image-2.6.10-1-686 (from
.../kernel-image-2.6.10-1-686_2.6.10-3_i386.deb) ...
You are attempting to install a kernel image (version 2.6.10-1-686)
However, the directory /lib/modules/2.6.10-1-686 still exists. If this
directory belongs to a previous kernel-image-2.6.10-1-686 package, and
if
you have deselected some modules, or installed standalone modules
packages, this could be bad. However, if this directory exists because
you are also installing some stand alone modules right now, and they
got unpacked before I did, then this is pretty benign. Unfortunately,
I can not tell the difference.
If /lib/modules/2.6.10-1-686 belongs to a old install of
kernel-image-2.6.10-1-686, then this is your last chance to abort the
installation of this kernel image (nothing has been changed yet).
If this directory is because of stand alone modules being installed
right now, or if it does belong to an older kernel-image-2.6.10-1-686
package but you know what you are doing, and if you feel that this
image should be installed despite this anomaly, Please answer n to the
question.
Otherwise, I suggest you move /lib/modules/2.6.10-1-686 out of the way,
perhaps to /lib/modules/2.6.10-1-686.old or something, and then try
re-installing this image.
Do you want to stop now? [Y/n]
Ok, Aborting
...
Yeah, you know the message, I know the message, I always got it when I
truly had some modules installed or when I was updating from the same
image, with a different version.
But I'm not! It's my first 2.6.10 install!
The culprit seems to be:
bee% ls -l /lib/modules/2.6.10-1-686/
total 0
lrwxrwxrwx 1 root root 36 2005-01-11 18:51 build ->
/usr/src/kernel-headers-2.6.10-1-686
bee% dpkg -S /lib/modules/2.6.10-1-686/build
kernel-headers-2.6.10-1-686: /lib/modules/2.6.10-1-686/build
Aha!
Could it be you added that new "build" symlink (which is probably handy
to build some modules such as madwifi I'm sure), and that confuses the
"crap detection" script?
workaround: install kernel-image first or say "Yes".
Regards,
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)
--
Loïc Minier <lool@dooz.org>
Reply to: