Why am I stuck in 6.1.0-12 kernel [Solved]

[MikeR]

@j2mcgreg

Sorry, but the list in Individual Sources seemed to consist of only the repos I already have.
So I stopped the process where was: No AHS, No Liquorix.

OTOH, seeing as how the current installed version offers no problems, perhaps I should stay with it until whatever problems you are having are cleared up. (They will eventually be cleared up -- He says hopefully)
My main worry was that I had setup something wrong, and as long as it's someone else's problem - so be it.

As a final question: How important i it that I do eventually upgrade?

Thank you for taking the time, and for you clear suggestions.

Mike

[MXRobo]

[j2mcgreg]

Screenshot_2023-12-14_12-03-41.png

MX Repo, not Individual Sources.

[MXRobo]

My fault, I did not read the second sentence.

[MikeR]

@j2mcgreg
@MXRobo

This is all I saw on the Individual Sources page

x.jpg

[Stevo]

It might be related to you having bookworm-backports enabled, contrary to the MX recommendations.

You can see what may be available for 6.1 kernels by (I use this because it's architecture-independent, so no different commands for i386 or arm installs) So we can see that Bookworm still does not have the 6.1.67 kernels available--maybe they are "twice burned, quadruple shy"?

Code: Select all

$ apt policy linux-source-6.1

linux-source-6.1:
  Installed: (none)
  Candidate: 6.1.66-1
  Version table:
     6.1.66-1 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
        500 http://deb.debian.org/debian bookworm/main i386 Packages
     6.1.55-1 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
        500 http://deb.debian.org/debian bookworm/main i386 Packages
     6.1.52-1 500
        500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
        500 http://security.debian.org/debian-security bookworm-security/main i386 Packages
     6.1.38-4 500
        500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
        500 http://security.debian.org/debian-security bookworm-security/main i386 Packages

[MikeR]

@Stevo

I unchecked bookworm-backports in Synaptic --> Settings --> Repositories --> Other Software
Reloaded, ran sudo apt update .... No visible results

By the way, I didn't know bookworm-backports was disparaged, I don't think I actively added it, IIRC.
Leaving it unchecled meanwhile. Can that hurt?

[MXRobo]

It should NOT be checked, neither should the testing.

Both the Test and Backport tabs in MXPI are TEMPORARILY enabled to install these packages, then disabled after installing to avoid dependency conflicts.
The devs, (maybe Stevo) does his thing and also checks for dependency conflicts before adding them.

I assumed, or guessed, or made some of that up - - but I think it suffices for the concept.

[Stevo]

The apt system itself handles dependency issues, but a packager can also give it extra instructions when setting up the package build.

Our testing repo really never generated problems if left on all the time, but as it expanded to thousands of packages, it became very difficult, if not impossible, to help users that automatically upgraded all of those by leaving it on, and then had some sort of problem that might be due to one.

Dolphin_oracle lowered the test repo's priority so upgrades aren't automatic any longer to keep that from happening, but that means you need special commands to get a newer package installed from it, which MXPI does automatically for you. The Debian backports repo has the same setup, as we pretty much copied it, but MXPI makes it much easier to search and manage both.

[Stevo]

Also, could you run "apt policy linux-source-6.1" and see if your output matches mine in the above example?