Hey! Sorry, I've had this in the back of my head to reply to, and I'm not sure if you still have your system in that condition and logs available etc, or if you have already cleaned it up or reinstalled from scratch. It might have been helpful to go through one of the user support channels first before filing the bug report though, as it still seems to me this was most probably due to user error.
I've been pondering about asking you to do just that now, and closing this bug report in the interim, because as it stands this bug report is a bit confused and really not actionable in any significant way, and I'm not sure if I'll have the time to track down the issue here. On Thu, 2014-02-06 at 10:53:54 +0100, Karsten Malcher wrote: > >>dpkg -l > >>rc linux-image-2.6.32-5-amd64 2.6.32-38 amd64 Linux 2.6.32 for > >>64-bit PCs > >>rc linux-image-3.1.0-1-amd64 3.1.6-1 amd64 Linux 3.1 for 64-bit > >>PCs > >>ii linux-image-3.12.6 3.12.6 amd64 Linux kernel binary > >>image for version 3.12.6 > >>rc linux-image-3.2.0-3-amd64 3.2.23-1 amd64 Linux 3.2 for 64-bit > >>PCs > >>ii linux-headers-3.12-1-amd64 3.12.6-2 amd64 Header files for Linux > >>3.12-1-amd64 > >>ii linux-headers-3.12-1-common 3.12.6-2 amd64 Common header files > >>for Linux 3.12-1 > >>ii linux-headers-amd64 3.12+55 amd64 Header files for Linux > >>amd64 configuration (meta-package) > > >I suppose there's no linux-image-3.2.0-4-amd64 in your system? > > It's complete chaotic! > I did have linux-image-3.2.0-4-amd64 installed before the upgrade. Hmm I don't see that from your dpkg_before.txt file. The closes one is linux-image-3.2.0-3-amd64. I also do not see any removal or installation of any linux-image package from your upgrade log. > Here you can see what i have on my running wheezy: > rc linux-image-2.6.32-5-amd64 2.6.32-38 > amd64 Linux 2.6.32 for 64-bit PCs > rc linux-image-3.1.0-1-amd64 3.1.6-1 > amd64 Linux 3.1 for 64-bit PCs > rc linux-image-3.2.0-3-amd64 3.2.23-1 > amd64 Linux 3.2 for 64-bit PCs > ii linux-image-3.2.0-4-amd64 3.2.54-2 > amd64 Linux 3.2 for 64-bit PCs Is that from the same system from the logs and the botched upgrade? It does not really match what's on the logs. > As you can see in the logs i have made before and after the system > upgrade, the kernel 3.12.6 was installed. > ii linux-image-3.12.6 3.12.6 amd64 Linux kernel binary > image for version 3.12.6 > > Then i want to remove the old kernel images and headers. > The result was a system with the old wheezy kernel! > > But the package management says the new kernel is installed: > ii linux-image-3.12.6 3.12.6 > amd64 Linux kernel binary image for Having the relevant dpkg.log and apt's history.log and term.log from the affected session might be helpful. Otherwise I'm not sure I can do more. > >Hmm I guess linux-image-3.12.6 is a locally built kernel? Are you sure > >that one was built with the corresponding kernel tree with such > >version? > > In dpkg.txt you see the answer for "apt-cache search linux-image". That only answers what's available to be installed from the repository not what's on the system or why, It does not answer either if that was locally built, or if it came from some third party repository, or what. And if locally built, how was it built, kernel-package, make deb-pkg etc. > There are several other things that i cannot understand: > > 1. I got no notification of your answer to the bug system. Dunno, maybe mail problem on your side, otherwise you'll have to ask the BTS admins. > 2. You don't find the kernel-images online for jessie. > Only > http://packages.debian.org/search?keywords=linux-image&searchon=names&suite=all§ion=all > works, > but it does not show the linux-image-3.12-1-amd64 !? > Just click on the link for jessie and you get an empty result. That's probably because that version is not available in jessie anymore. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
