dpkg-deb: error: parsing file 'debian/mythtv-build-deps/DEBIAN/control' near line 2 package 'mythtv-build-deps':
'Version' field value '2:29.1+fixes.20190829.7668cc59ab-Version:': invalid character in revision number
dh_builddeb: dpkg-deb --build debian/mythtv-build-deps .. returned exit code 2
dh_builddeb: Aborting due to earlier error
make: *** [debian/rules:30: binary-indep] Error 2
Error in the build process: exit status 2
dpkg: error: cannot access archive 'mythtv-build-deps_29.1+fixes.20190829.7668cc59ab-Version:_amd64.deb': No such file or directory
mk-build-deps: dpkg --unpack failed
error installing dependencies
I was told to edit one of the files for compiling on Debian 9. Same thing here?
On closer examination it seems that the packaging for mythtv fixes/29 has not been updated for Debian 10 (Buster).
So if Debian 9 works for you, that is your best option for quickly getting a working frontend.
Meh. I'm trying to move all my hardware to Debian. My backend was installed on CentOS 6 something like eight years ago. With *great* difficulty I got it upgraded from .27 to 29. I'm going to move it to a little Debian box. I guess I'll downgrade that box from 10 to 9.9. Once I get that done it'll be easier to upgrade to 30.
In case it helps anyone I have produced a patch which allows fixes/29 to build on Debian 10 (Buster) see attached patch which needs to be applied to packaging before doing ./build-debs.sh fixes/29
Note I do not know what the official support position of fixes/29 is on Debian Buster.
There are still some issues:
1. During mythtv (combined frontend/backend) install the mythconverg database is not created, the install tries Configure mythtv-database using MySQL debian-sys-maint account which does not exist for mariadb. This is tried a few times and eventually fails. A fix is to make sure mysqld is running ("sudo systemctl start mysql") then run "sudo dpkg-reconfigure mythtv-database".
2. Due to the removal of package gksu in debian based systems, the user running mythtv needs to be added to the mythtv group, "sudo adduser $USER mythtv" then logout or reboot.
Also the mythtv packaging scripts to control operation of mythtv-backend when running mythtv-setup do not work. It is necessary to use a terminal session and run "systemctl stop mythtv-backend" before running mythtv-setup, when finished use "sudo systemctl start mythtv-backend", sometimes systemd will have "failed" mythtv-backend e.g. restarting too many times, in such cases "sudo systemctl daemon-reload" is required before "sudo systemctl start mythtv-backend".
3. First run of mythtv-setup always fails to login to mythconverg database, it tries to use a default password of "mythtv" but the real password is in /etc/mythtv/config.xml file
Issues 2 and 3 are known (on Ubuntu as well) and changes have just been commited to mythtv packaging master branch, I have no idea if/when they might be applied to fixes/29 or fixes/30
Alas, this lack of backwards compatibility compels me to open my distro horizons. MythTV seems to have always had an Ubuntu focus. With a separate repository for Myth, that seems like a logical choice.
Since I have clean hardware to work with (one frontend and one soon to be backend) I think I'll give Ubuntu a try.
You can user either, personally I use Xubuntu 18.04 Desktop. I have a remote mythtv backend using Desktop with no monitor or keyboard, I just use ssh from another linux machine.