No – this is not something that is supported.
Security support for Bullseye handed over to the LTS team
As of 14 August 2024, three years after the initial release, the regular security support for Debian 11, alias “Bullseye”, comes to an end.
Whenever possible, users are encouraged to upgrade their machines to Debian 12, alias “Bookworm”, the current Debian stable release.
It is still maintained and Bookworm is still being worked on. Let’s get v21.1 out first.
1 Like
Just wanted to check in: Debian already moved on to trixie and Kodi also is at 21.3 right now (OSMC 25.11). More importantly Python 3.9 (bullseye) is now already a show stopper (e.g. SentToKodi), so an upgrade to either bookworm or, better still, trixie would be highly appreciated.
Kindly asking, what is the current status one and a half years later?
Thanks Sam!
1 Like
We are moving to Trixie, not Bookworm.
Sam
3 Likes
Sensible choice, obviously. Do you have any kind of an (rough) ETA for us? Just for planning purposes.
Thanks!
Soon. That’s all I can say unfortunately
Sam
2 Likes
Any update on the update? I must admit, I am getting nervous seeing the trixie and bookworm boxes I manage get plenty of updates, including immediate security updates, while my OSMC installations still on bullseye aren’t.
1 Like
Yes, it’s a priority with Kodi v22.
1 Like
Debian 11 is now officially dead, even LTS is EOL:
The Debian Long Term Support (LTS) Team hereby announces that Debian 11 “bullseye” support has reached its end-of-life today, 31 August 2026, five years after its initial release on 14 August 2021.
2 Likes
Indeed, when CVEs are now very regularly announced for core Linux infrastructure, it’s appalling for OSMC to continue shipping an unsupported distro. I guess I have the skills to switch to Kodi running on Raspbian, but I feel sorry for non-techie people who just buy OSMC-based devices, or see it as an easy packaged solution for their Pi, and don’t realize how neglected what’s under the hood is.
1 Like
We already backport CVEs and we will be on Debian 13 very shortly.
So little to worry about. The only recommendation which we always make and would make even for maintained distributions is to not expose OSMC to the public internet.
Sam
3 Likes
Exposing appliances (except firewalls) to the internet is a No-go. But you always must assume that a usual home network is already breached.
At home zero trust and up2date OS is even more important than in a enterprise environment
1 Like
If moving to Kodi 22 is what is holding the Trixie upgrade back, that would be an important qualifier to “very shortly”: Kodi 22 isn’t even out yet, it hasn’t moved on from its one initial beta release, and that ecosystem moves very slowly. People will still be running an unsupported distro for months to come, and while you might backport CVEs, you presumably only do so for packages considered part of a base OSMC install; the whole attraction of OSMC for many users is that one could install the full range of Debian packages.
I don’t think it is. AIUI Kodi 21 can run under Trixie but Kodi 22 can’t run under Bullseye.
Sam linked the two in his post of 22 May.
Can Kodi 21 really successfully run under Trixie? Earlier this year there were discussions on Reddit etc. that while Kodi itself might run, even official Kodi addons in the Kodi 21 ecosystem break on Trixie.
I do hope it can. Changing Debian and Kodi at the same time (or nearly the same) was messy last time, or was that the kernel upgrade 
.
Kodi v21 can run just fine under Trixie.
Add-ons are just fine.
Kodi v22 is in b2: https://kodi.tv/article/kodi-22-piers-beta-2/
And now the problems begin: trying to install ffmpeg (which a lot of OSMC users would want for remuxing) fails because the Bullseye security-updates repo that apt wants to pull from is no longer extant.
1 Like
You do your remuxing on Vero? Won’t that take forever?