Not upgrading: linux-headers-mnt-reform-arm64

1

Hi, I ran a apt update && apt full-upgrade today but now my battery status is no longer visible; the reform2-lpc-dkms kernel module is no longer loaded. dkms reports a version for an older kernel version is installed. So not all is upgraded.

More information:

[remp 17:48 ~]$ sudo apt full-upgrade
Not upgrading:
  linux-headers-mnt-reform-arm64

Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 1
[remp 17:48 ~]$ sudo apt install linux-headers-mnt-reform-arm64
Solving dependencies... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
 linux-headers-6.17.8-mnt-reform-arm64 : Depends: gcc-15-for-host but it is not installable
Error: Unable to correct problems, you have held broken packages.
Error: The following information from --solver 3.0 may provide additional context:
   Unable to satisfy dependencies. Reached two conflicting decisions:
   1. linux-headers-6.17.8-mnt-reform-arm64:arm64 is selected for install because:
      1. linux-headers-mnt-reform-arm64:arm64=6.17.8-1+reform20251126T085426Z is selected as an upgrade
      2. linux-headers-mnt-reform-arm64:arm64=6.17.8-1+reform20251126T085426Z Depends linux-headers-6.17.8-mnt-reform-arm64 (= 6.17.8-1+reform20251126T085426Z)
   2. linux-headers-6.17.8-mnt-reform-arm64:arm64 Depends gcc-15-for-host
      but none of the choices are installable:
      [no choices]
[remp 17:48 ~]$ sudo dkms status
reform2_lpc/1.82, 6.16.7-mnt-reform-arm64, aarch64: installed

Anybody know how to fix or workaround this?

1 Like
2

To reproduce this, I triggered a new system image build on the MNT gitlab CI which will also install both linux-headers-mnt-reform-arm64 as well as gcc-15-for-host and it seems to be able to do so without issues:

Between me writing this and your initial message another dinstall happened so maybe you were just unlucky and unstable was broken for the mirror update that you used? Can you run apt update && apt full-upgrade again and see if it works now? Otherwise we can have a deeper look on the dependency situation on your machine.

3

Found it! I changed my debian.sourced to trixie just before that became stable and enjoyed a stable debian for a couple of months but i guess the party is over now.

Moving up to forky seems to work.

4

If you already upgraded from Trixie to Forky then indeed there is no easy way back. But this kind of information (that you are using the repository from reform.debian.net) would’ve been essential in your initial post. I assumed you were using the MNT repositories…

If there is a bug in the repositories from reform.debian.net then I will prepare a fix. It should not be necessary to upgrade to Forky.

2 Likes
5

I am very sorry about wasting your time Josh. I totally forgot about the trixie trickery which works so well for months. Thank you for investigating as it did help me find the issue by confirming I made a mistaken somewhere.

6

@rwv out of curiosity and because your nicknames share 2/3 letters: do you happen to be user rwa_ on IRC?

7

No, I am not on IRC.