Since the bump of dtv-scan-tables to version
ceb11833b35f05813b1f0397a60e0f3b99430aab in commit
b1c8794d8a, one file contains non-ASCII
characters, which causes encoding issues tvheadend. Since no other
file in the dtv-scan-tables code base contains files with non-ASCII
characters (despite having files named after cities in various
countries that definitely do have non-ASCII characters), we rename
this file so that it is named with only ASCII characters.
This fixes the build of tvheadend, which was failing when the host
Python interpreter was python3, due to a file name encoding issue.
Fixes:
http://autobuild.buildroot.net/results/1ae8bee297edb089535a2fb6ec724ebf7976888d/
(tvheadend)
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
New scan tables, and updates to existing ones.
Update upstream URL at the same time.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
The commit hash chosen by Yann exists in the repository accessible by
git://, but not the one accessible by http://, which is lagging 3
commits behind the git:// repository, for some reason.
For the time being, revert to the latest commit available in the
http:// repository.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This is a transitioning solution before switching packages that need the
transponders data, to use dtv-scan-tables instead of dvb-apps.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
The dvb-apps package used to carry pre-scanned transponders data. These
transponders data have now been moved out of dvb-apps, and into their
own repository.
So, until we bump the dvb-apps package (to come in a follow-up patch),
dtv-scan-tables is exclusive to dvb-apps.
To be noted: the licensing information for those data is dubious. The
package carries the COPYING and COPYING.LIB files, hinting that the data
is covered by the GPLv2 *and* the LGPLv2.1. This is incoherent, and
dubious:
- since GPLv2 is a superset of LGPLv2.1, the actual license would be
just plan GPLv2;
- the transponders data is just a collection of 'facts': the
frequencies of each transponder; as such, it is usally not considered
to be a 'work' as per traditional copyright, and thus should be in
the public domain [cue the zoneinfo DB not so long ago].
But since this is a difficult question, we'll leave to the user to sort
these things out.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
