I held (apt-mark hold) mediacenter-addon-osmc, mediacenter-skin-osmc, rbp-userland-osmc, rbp2-libcec-osmc and rbp2-mediacenter-osmc and everything still looks ok, but of course YMMV.
This won’t work after OSMC will move to bullseye, but for now it will postpone the problems.
Rbp-userland-osmc may not be needed but I didn’t care enough about it to try upgrading that too.
I was going to ask a similar question. I have a number of RPI 3B that I would like to keep on v18.
Are there any changes I should make to the sources.list to avoid accidental upgrades of Kodi while keeping any underlying debian security updates?
deb http://ftp.debian.org/debian buster main contrib non-free
deb http://ftp.debian.org/debian/ buster-updates main contrib non-free
deb http://security.debian.org/ buster/updates main contrib non-free
deb http://apt.osmc.tv buster main
I’d have thought that you would comment out all lines, except for:
There are apparently some security updates that are included in regular package updates, but they tend to be things like kernel updates.
As mentioned, this will be unsupported, so at your own risk.
@ghepeu TBH, playing pick and mix with the OSMC packages is probably not a sensible approach. If it were me, I’d be inclined to comment out the OSMC repo, so that you know all (OSMC) packages will stay at the same release level.
OSMC packages can’t really be mixed and matched like that, so you should indeed remove the OSMC repository altogether if you want to stay aligned with Debian updates.