Ah! Well done, I didn’t, I wouldn’t know where to start, I thought it was confusing enough when part of the emonpi repo.
The net result of that position is that each user may have a slightly different sdcard build depending on the status or the debian repos at the time of install irrespective of any further updating of the emonsd.
Either not running an update/upgrade at all (not recommended) or running an update/upgrade at each emonsd update would put everyone on a common image and update path. Updating once at time of inception and never again is IMO the worse scenario as it potentially means no 2 images are the same making experience, reliability and debugging a tad random.
I thought following the big discussion regards using apt-get upgrade or dist-upgrade and the fact only recent (non-mosquitto repo?) images are updated via emoncms, the OS was safe to update.
It’s a bit odd that we are pursuing Python v3, dropping Jessie and possibly php 7.0 etc for security reasons as these will no longer get security patches, when we do not pull in any patches to the OS or installed packages (eg Python) for the life of the emonSD image which could be years and years!!!