It seems you started off with the recommended procedure for upgrading which is great. I recommend trying to stick to that instead of prematurely doing a dist-upgrade. This procedure is worked out by testing on thousands of systems and is what we think is your best chance of a smooth upgrade.
In this case when you are doing apt-get upgrade
we are EXPECTING lots of packages to be held back. That is by design. We want to do just a minimal upgrade in order to get the new kernel and udev installed, then reboot, then do the rest of the upgrade with dist-upgrade
.
You should be concentrating on this error:
linux-image-2.6-amd64: Depends: linux-image-2.6.32-5-amd64 but it is not going to be installed
There is some reason why apt doesn't want to install linux-image-2.6.32-5-amd64
. Find out by trying to install it directly with apt-get install linux-image-2.6.32-5-amd64
, That will either install it, or will tell you specifically what is wrong with this package. When this results in a problem with another package, do the same with this package, by trying to install it directly, until you reach a root cause. Once the kernel is successfully installed, proceed with the upgrade instructions from there.
One artifact that doing this will have which may be undesired is marking the linux-image-2.6.32-5-amd64
package as automatically installed. After the upgrade is complete, and you are happy with the results, you might run apt-mark auto linux-image-2.6.32-5-amd64
to mark this package as automatically installed.
The reason that /etc/debian_version
reads 6.0.5 is that you already update the base_files
package. This is not a surpise.
The problems with mixing aptitude and apt-get were resolved with apt-get version 7.0 a few years ago, you should feel free to mix their use at will. In fact, Debian recommended aptitude for upgrading from one major release to another in the past and now recommends apt-get, so clearly Debian is recommending using both. We will recommend whichever one seems to work better for a given upgrade. On the lenny->squeeze upgrade, aptitude tends to think "too hard" about finding an optimal upgrade path, and the more simple dependency resolution in apt-get works for more people.
Best Answer
I had a similar problem, except that the list command didn't see it either, but the include command thought it was still there when I tried to add it. This fixed it for me: