On Sun, Jul 02, 2006 at 10:46:51PM +0200, Francesco Pietra wrote: > While my amd64 debian etch is in order, 32 bit debian etch has suffered much > and is now in a state of semi-mess. alright, I'll tackle this, but I don't use amd64 and so there may be other issues. > > Kernel booted is > linux-image-2.6-15-1-k7: > but > #aptitude > shows also a collection of kernels, partly broken: > BA linux-image-2.6-486 *** > BA linux-image-2.6-686 *** > BA linux-image-2.6-686-smp *** > iA linux-image-2.6-k7 *** > BA linux-image-2.6-k7-smp *** > i linux-image-2.6-15-1-k7 > the packages marked *** above are what are called "meta-packages". they are packages which do not actually contain anything, but depend on the current latest linux-image of the type specified. The 4th item, linux-image-2.6-k7 is a meta-package specifying a dependency on the latest 2.6 kernel compiled for k7 architecture, which happens to be, on your machine linux-image-2.6.15-1-k7. That is why that particular meta-package is not marked as broken. The others, marked as broken, are broken because their dependencies, in this case kernels compiled for 486, 686, 686-smp and k7-smp, are not installed, though the meta-package is. I would guess that at some point you uninstalled the kernels that these meta-packages rely on without also uninstalling the meta-packages themselves. This is not really a problem except for the big problems it causes for the apt system when trying to update your system. > unusued refuse to uninstall: > debian:/home/francesco# apt-get --purge remove linux-image-2.6-k7 > Reading package lists... Done > Building dependency tree... Done > You might want to run `apt-get -f install' to correct these: > The following packages have unmet dependencies: > linux-image-2.6-486: Depends: linux-image-2.6.15-1-486 (= 2.6.15-8) but it > is not going to be installed > linux-image-2.6-686: Depends: linux-image-2.6.15-1-686 (= 2.6.15-8) but it > is not going to be installed > linux-image-2.6-686-smp: Depends: linux-image-2.6.15-1-686-smp (= 2.6.15-8) > but it is not going to be installed > linux-image-2.6-k7-smp: Depends: linux-image-2.6.15-1-k7-smp (= 2.6.15-8) > but it is not going to be installed > nvidia-kernel-legacy-2.6-k7: Depends: linux-image-2.6-k7 but it is not going > to be installed > E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a > solution). > debian:/home/francesco# this is all caused by the situation described above. > > Also > > #apt-get -f install (in an attempt to install so that it can be removed > later): > debian:/home/francesco# apt-get -f install > Reading package lists... Done > Building dependency tree... Done > Correcting dependencies... Done > The following extra packages will be installed: > linux-image-2.6.15-1-486 linux-image-2.6.15-1-686 > linux-image-2.6.15-1-686-smp > linux-image-2.6.15-1-k7-smp > Suggested packages: > linux-doc-2.6.15 linux-source-2.6.15 lilo fdutils > The following NEW packages will be installed: > linux-image-2.6.15-1-486 linux-image-2.6.15-1-686 > linux-image-2.6.15-1-686-smp > linux-image-2.6.15-1-k7-smp > 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. > 12 not fully installed or removed. > Need to get 0B/63.0MB of archives. > After unpacking 182MB of additional disk space will be used. > Do you want to continue [Y/n]? > > Yes resulting in warning for each installation: > You are attempting to install a kernel image (version 2.6.15-1-486) However, > the ??? > ??? directory /lib/modules/2.6.15-1-486 still exists. If this directory > belongs to a ??? > ??? previous linux-image-2.6.15-1-486 package, and if you have deselected some > ??? > ??? modules, or installed standalone modules packages, this could be bad. [[ snipped hard to read stuff about broken kernel packages ]] > ??? > ??? If this directory is because of stand alone modules being installed right > now, or ??? > ??? if it does belong to an older linux-image-2.6.15-1-486 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.15-1-486 out of the way, > perhaps to ??? > ??? /lib/modules/2.6.15-1-486.old or something, and then try re-installing this > image. ??? > ??? > ??? > ??? Stop install since the kernel-image is already installed? > > So that I stopped installing. So, then answer the questions it asked. do you have stand-alone modules being installed? did you have an older version of these kernels ? Since you have a currently working kernel (2.6.15-1-k7) I would go ahead with this install and don't panic. Alternatively, you could follow the suggesting of temporarily moving those modules aside into <kernelversion>.old directories somewhere and proceed with the install. THen you can purge the kernels you aren't using (though its nice to keep a couple around in case you have problems). Probably though, you should settle on one architecture. You don't need 486 and 686 and k7 kernels. Probably just the k7 would be sufficient. And if you have dual core or multi-processor setup then the smp is for you. Regardless, you will have to resolve this problem or you will not be able to correctly update your system. If it were MY machine, I'd just do it, but then I love breaking things so I can fix them. I don't think you'll break anything, and if you do, it should be readily fixable after you get of this mess. > > Something (probably libwine) was dependent of the 686 kernel and now wine > exits with error 127 (a known event that I remedied in the past by removing > libwine and reinstalling it: now any attempt at removing libwine results in > the problems above of broken packages. these problems shown above are almost certainly NOT related to libwine. > > What means "A" that appears for some packages on aptitude? I think it means "a"utomatically installed in that something you did somewhere with aptitude caused it to install automatically. > > Should a remedy be conceivable from this messing desription, thank you > yes. hope this helps A
Attachment:
signature.asc
Description: Digital signature