[SOLVED] No in-place update ?

[Tim Curtis]

@Falconcrest

If writing custom code on a moOde player, then it's generally a good idea to use apt update.

OTOH, it's generally not a good idea to run apt upgrade since each released moOde image has been built against a specific version of Raspberry Pi OS and its libraries. Frequently the changes to system libraries, etc., incurred in an upgrade are benign, but once in a while things break because of incompatible changes. Use at your own risk. The worst that can happen is you have to flash a new moOde image and configure it for your circumstances.

Regards,
Kent

I would agree that doing apt upgrade or dist-upgrade could cause breakage. 

Many of the packages that moOde directly depends on are "held" and so they can't be upgraded via apt without explicitly removing the holds. This can further complicate an apt upgrade though because if a package being upgraded is dependent on one of the held packages that particular upgrade won't be done. What you can end up with is a partially upgraded system in an unknown state :-0

If all the moOde package holds are removed then an upgrade can cause other types of problems for example if the upgrade bumps the Linux kernel then the four custom drivers that we compile two of which are for the Allo SIG won't be present. If the upgrade bumps the version of PHP then moOde won't work at all.

Given that our project releases a new version of moOde every quarter and each version includes the latest upgrades you will only be a few months behind the latest upgrades from the Raspberry Pi crew. This assumes you go with a fresh image and restore settings from a backup. We don't do any apt upgrades in the in-place updates.