Every time I (re)install Tvheadend (on Debian-like systems) I end up with a really old dvb-t/uk-Salisbury scan file, which contains frequencies no longer in use from this transmitter. So tvheadend finds no muxes.
Having done a git clone of tvheadend, I see that the Makefile does a git clone of tvheadend/dtv-scan-tables.git to get the scan files.
But the canonical source is, I believe, a different project (https://git.linuxtv.org/dtv-scan-tables.git) which contains files which are regularly updated and much newer. The dvb-t/uk-Salisbury scan file contains the right frequencies for the transmitter muxes.
Is there a good reason for using a different set of scan files ? If so, should we be syncing the files in order to stay up to date ?
I believe the dtv-scan-tables used to be part of dvb-apps, but they've now been separated out. Should we avoid having 2 copies of the scan files on tvheadend systems (my machines have files in both /usr/share/dvb and /usr/share/tvheadend) by git cloning the canonical project ?
Or should we be even simpler and add a package dependency on dtv-scan-tables ?
The time difference is huge, tvheadend's uk-Salisbury dates from 2014-03-25, dtv-scan-tables's from 2023-02-10
