Package: dpkg
Version: 1.17.6
Severity: important

Hello,

i tried to upgrade from wheezy to jessie with the following steps:

1. I altered sources.list
2. apt-get update
3. apt-get dist-upgrade
4. apt-get remove linux-image-3.2.0-3-amd64
5. apt-get remove linux-headers-3.2.0-3-amd64 linux-headers-3.2.0-3-common
6. apt-get remove linux-headers-3.2.0-4-amd64 linux-headers-3.2.0-4-common

As result i get a system booting a kernel 3.2.0-4 !?

That's what i can see afterwards after a reboot:

uname -a
Linux PC10 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux

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)

ls -l /boot

-rw-r--r--  1 root root 127K Feb  2 02:16 config-3.2.0-4-amd64
drwxr-xr-x  3 root root 4,0K Feb  4 18:32 extlinux
drwxr-xr-x  5 root root  12K Feb  4 18:32 grub
-rw-r--r--  1 root root 8,7M Dez  3  2010 initrd.img-2.6.32-5-amd64.org
-rw-r--r--  1 root root  11M Feb  2 19:03 initrd.img-3.2.0-4-amd64
-rw-r--r--  1 root root 173K Nov 13  2011 memtest86+.bin
-rw-r--r--  1 root root 175K Nov 13  2011 memtest86+_multiboot.bin
-rw-r--r--  1 root root 2,1M Feb  2 02:16 System.map-3.2.0-4-amd64
-rw-r--r--  1 root root 2,8M Feb  2 01:51 vmlinuz-3.2.0-4-amd64

How this is possible?

Regards
Karsten


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to