[SID - Unstable] Problem ungrading kerne

[rossi]

Hello Everyone.

I am have a real problem with updating the current kernel.

Code: Select all

root@debian:~# uname -a
Linux debian 6.6.9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.6.9-1 (2024-01-01) x86_64 GNU/Linux
root@debian:~# 

and when I try to upgrade

Code: Select all

root@debian:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 linux-headers-6.6.9-amd64 : Depends: linux-image-6.6.9-amd64 (= 6.6.9-1+b1) but 6.6.9-1 is installed or
                                      linux-image-6.6.9-amd64-unsigned (= 6.6.9-1+b1) but it is not installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

Code: Select all

root@debian:~# apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  linux-headers-6.6.8-amd64 linux-headers-6.6.8-common linux-image-6.6.8-amd64 linux-kbuild-6.6.8 python3-backcall python3-pickleshare
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  linux-image-6.6.9-amd64-unsigned
Suggested packages:
  linux-doc-6.6 debian-kernel-handbook
The following packages will be REMOVED:
  linux-image-6.6.9-amd64
The following NEW packages will be installed:
  linux-image-6.6.9-amd64-unsigned
0 upgraded, 1 newly installed, 1 to remove and 61 not upgraded.
3 not fully installed or removed.
Need to get 0 B/96.6 MB of archives.
After this operation, 19.5 kB disk space will be freed.
Do you want to continue? [Y/n] 

This update throws other dangerous errors like it will install/remove the same kernel, and the system will NOT be bootable.

I run into this error on two different machines. How did I get here? I think that I am very careful doing updates. I don't understand what happened!

Can you help please

Thanks so much.

Regards,

Angelo

[rossi]

Hello,

This what I get, if I try to continue:

Code: Select all

Do you want to continue? [Y/n] 
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
dpkg: linux-image-6.6.9-amd64: dependency problems, but removing anyway as you requested:
 linux-headers-6.6.9-amd64 depends on linux-image-6.6.9-amd64 (= 6.6.9-1+b1) | linux-image-6.6.9-amd64-unsigned (= 6.6.9-1+b1); however:
  Package linux-image-6.6.9-amd64 is to be removed.
  Package linux-image-6.6.9-amd64-unsigned is not installed.

(Reading database ... 514835 files and directories currently installed.)
Removing linux-image-6.6.9-amd64 (6.6.9-1) ...
E: Aborting removal of the running kernel
dpkg: error processing package linux-image-6.6.9-amd64 (--remove):
 installed linux-image-6.6.9-amd64 package pre-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
 linux-image-6.6.9-amd64
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian:~# 

Again, I am not sure what happened. I have made so many sloppy errors with upgrades in the past, and I have tried to be careful. I now NEVER perform an upgrade if there is even a hint or whiff of a potential problem. I have been burned too many times.

Thanks for your patience with this.

Regards,

Angelo

[rossi]

Hello,

I solved this with the following command (as root):

Code: Select all

aptitude update && aptitude dist-upgrade && aptitude upgrade

aptitude walked me through several steps, for example when it asks me remove the same kernel I am running, apptitude DOES remove the kernel and then reinstalls it properly (I think that was the problem?) and then does an update against that "new" kernel. I am happy.

Regards,
Angelo

[wizard10000]

Said it a few times around here but I strongly recommend aptitude for routine upgrades if you're running Testing or Unstable; its also not a bad idea if one is running Stable and has non-Debian repositories enabled.

Glad you got it sorted