Author: Christian Marillat Date: To: dmo-discussion Subject: Re: MythTV 31 in experimental
On 04 mars 2020 12:48, Werner Mahr <werner@???> wrote:
> Am Montag, 2. März 2020, 08:38:46 CET schrieb Christian Marillat:
>> On 01 mars 2020 17:45, Werner Mahr <werner@???> wrote:
> Jep, works. I would have preferred to have it named python-mythtv, as this
> allows just a normal apt-upgrade instead of a dist-upgrade, but I guess it's a
> policy thing here.
Yes. Python 3 packages should be named python3-
> The v30 mythtv-backend shipped that file, I saw you changed the EnvironmentFile
> in the mythtv-backend.service and played a bit with that.
> The bad news: Changing the user to as isn't possible with this, so users like
> me, that run the backend as their normal user to easier access mythtv-setup
> have to edit the unit manually.
Normally the configuration is written is the mariadb database.
> The good thing, placing a symlink to the old-file or just moving it there
> works, as the old one isn't removed while upgrading.
Maybe a good documentation for that.
https://wiki.archlinux.org/index.php/Systemd/User > Maybe you can consider to ship a file for that, with all the params predefined
> there. In my cas I have to edit the unit to remove the --syslog... stuff, as
> mythtv has now a --systemd-journal param to directly log there. I read
> somewhere that rsyslog will be replaced by systemd-journald in the future (or
> at least everthing is prepared that it could be replaced).
> And btw. the old defaults calls it EXTRA_ARGS, while the unit uses
OK, back to EXTRA_ARGS variable in service file :
and /etc/default/mythtv-backend to add options with EXTRA_ARGS
> And just as an additional info, changing the dh_sequence_python3 to the older
> dh --with-python3 and freetype-dev to freetyp6-dev makes it work on stable,
Well I think the best is to upload mythtv 31 build for stable packages
This message was posted to the following mailing lists: