Both my Vero4k+ appear to be running that version too. I didn’t deliberately try to go to an unsupported version, but they’re both on that version. I did find I had to apply the fix for the updates, because I was getting errors popping up on the screen about an update being available and it failing.
That said, it all seems to be working perfectly fine at the moment. The 4k+'s occasionally lock up, but a reboot fixes that, and that’s not a new bug.
If the 4K+ and 5 are diverging Sam then you perhaps should run separate repos for them to avoid this sort of thing happening.
I do also have 2x Vero V’s too.
One thing I find a bit odd/disappointing is that it appears better OS support is provided to 3rd party devices than to your own devices.
OSMC latest version is available as far back as the Raspberry Pi 2, yet not your own more recent hardware devices, despite everything largely working just fine.
I’m sorry, but that doesn’t make a whole lot of sense to me. I have 2x 4k+ devices that largely work just fine (the last of which I purchased in 2021), but i’m not supposed to run that version on those devices. Yet if i go dig my Pi 3b+ out (which I purchased in 2018, and not from you), I apparently can run the latest version on that.
We stopped updates some time ago via the UI, if you run dist-upgrade (it’s at your own risk).
Going forward, Trixie will only run on Vero V and not 4K/4K+
That’s not quite the case. Vero 4K has been supported from 2017 to 2025.
I can see your point, but we haven’t been doing anything to maintain RBP2/RBP3 for some time. Sadly it’s for the chopping block with Trixie and Pi 5 support. So it has not been getting substantial updates for a long time (before Vero 4K/4K+) now.
Ahh that’s probably it. I run tailscale on my remote Vero’s so to update that I use the CLI.
Moving to 64 bit and Trixie, can totally understand drawing the line there. From a customer point of view, it’d have probably been good to run the 4K/4K+ up to the end of the current release, then draw the line at Trixie. Especially give, if I’ve read correctly, Trixie will need a fresh install, not an upgrade?
I was actually going to deploy a Vero V remotely to replace a 4K+, but reading about the Trixie upgrade path, I may now wait till that’s released if it’s going to require physical intervention to upgrade.
but please explain a bit more why this can be ignored and there are no other packages then the kernel that are marked with “arm64”.
The apt error, as well, tells us that this source will be skipped, or?
Already have it, thanks But I need to deploy it to a remote location, and if I’m reading correctly, to upgrade to 64 bit Trixie will need a fresh install? If that’s the case, rather than deploy it now, I guess I’ll sit on my hands for a bit and wait till Trixie comes, so I can do a fresh install and deploy directly with Trixie.
Thanks Sam for the constant and diligent support, easy fix and workaround. This is undoubtedly what makes Osmc and Vero-V such a outstanding stable and dependable product, that you may not get from others. Whenever there is an issue he goes out of his way to fix it.
It is great that we will have Debian Trixie and à native 64-bit platform, with a new linux kernel (5.15 LTS?). I guess this has entailed a hard work to wrestle with Amlogic’s minimal Android kernel and drivers documentation and turn it into a proper, compatible and optimised Linux kernel and OS. I can imagine they don’t care much for Linux, so it’s all the more commendable for Osmc team.
Thanks and all the best for what’s coming.
Kodi Piers is on its way too!
Thanks for all the hard work especially now with Trixie and getting ready for the big changes involved.
…so it will need a fresh installation. My OSMC’s backup and restore will carry
your settings across, and the process will be documented properly before release.
When you refer to “settings” carrying over using My OSMC backup and restore, does this include the library database and playlists as well? I know the db is within the B&R process provided one is doing a full backup or at least selecting the database for backup, but not sure if the DB is in fact considered “settings”.
I know that may seem like a stupid question, but those words “fresh install” have me thinking (panicking?) about the prospect of having to recreate a library database for a curated 34TB library of Movies/TV/Music is terrifying.
Just wanted to confirm the library database will be “safe” when its time to do a fresh install of Trixie, and confirm that once I’ve overwritten my 2 Vero Vs with Trixie that I can restore an entire full backup from the current running version which will correctly restore the library DB
Thanks again, and apologies if this was a ridiculous question!
H
Edit: I notice you’ve edited the post I’m responding to since I was pulled away from posting this a few days ago (kudos to the board software for saving my work!) Given the edit, now I’m really feeling hesitant. Did that bit about OSMC backup/restore carrying settings change? Is that still the plan? Thanks Sam
I have already converted my Pi 4 to vanilla Debian Trixie. This turned out to be straightforward; it took less than an hour to set up and move my Kodi folder over, and then I have all the same functionality as I had before. I guess that since Debian began supporting Raspberry Pi itself and packaging a recent Kodi version, there has been less need for a specialized OS like OSMC.
And now I can rest assured that my OS is being maintained by a whole competent security team instead of just one man. It remains deeply disturbing that you are keeping your users on an EOLed and unsupported OS. Your recent remark on this forum that “OSMC is maintaining Debian Bullseye security updates ” is outright misleading to your users: you might be keeping a few default OSMC packages patched, but you are not providing security patches for all the myriad other packages available for installation under Bullseye, some of which have already been found to have vulnerabilities patched in Bookworm and Trixie.
Outstanding, thanks Sam, exactly what I’d hoped given the fresh install situation. Short of being able to upgrade in place, being able to fully restore to Trixie from a full backup is perfect! Thanks again for all you do, Godspeed on the upgrade!
But I need to deploy it to a remote location, and if I’m reading correctly, to upgrade to 64 bit Trixie will need a fresh install? If that’s the case, rather than deploy it now, I guess I’ll sit on my hands for a bit and wait till Trixie comes, so I can do a fresh install and deploy directly with Trixie.
