Package Details: mythtv-git 34.0.r23.g9b54f1a672-1

Git Clone URL: https://aur.archlinux.org/mythtv-git.git (read-only, click to copy)
Package Base: mythtv-git
Description: A Homebrew PVR project (Stable '-fixes' branch)
Upstream URL: https://www.mythtv.org/
Licenses: GPL
Conflicts: mythtv
Provides: mythtv
Submitter: JohnLBergqvist
Maintainer: JohnLBergqvist
Last Packager: JohnLBergqvist
Votes: 36
Popularity: 0.001288
First Submitted: 2023-04-10 09:11 (UTC)
Last Updated: 2024-06-30 17:31 (UTC)

Dependencies (63)

Sources (6)

Pinned Comments

JohnLBergqvist commented on 2023-04-10 15:56 (UTC) (edited on 2023-04-10 15:57 (UTC) by JohnLBergqvist)

This package replaces the previous 'mythtv' AUR package. It has been renamed to comply with Arch's VCS package guidelines.

I hope to update the various mythplugins AUR packages soon

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 31 Next › Last »

keepitsimpleengr commented on 2021-07-26 02:00 (UTC) (edited on 2021-07-26 02:01 (UTC) by keepitsimpleengr)

Downgraded MariaDB and now backend starts, however, now deleting a recording from a frontend (client) not on the backend (server) computer fails (e.g. deleting a recording from recording it appears to delete but does not show up in status and reappears in recordings)....

archcomp commented on 2021-07-25 21:07 (UTC)

OK, so I downgraded mariadb for the time being to version 10.5.11-1, as someone suggested. Works for me.

deadite66 commented on 2021-07-23 06:02 (UTC) (edited on 2021-07-23 20:16 (UTC) by deadite66)

anyone else have mythbackend fail to start after mariadb upgrade to 10.6.3?

EDIT: just noticed someone posted a bug on the mythtv github https://github.com/MythTV/mythtv/issues/373

bigcajun826 commented on 2021-04-09 18:03 (UTC)

Thanks @delx!

delx commented on 2021-04-09 16:29 (UTC)

@bigcajun826 done. Hope it works for you :)

bigcajun826 commented on 2021-03-24 16:54 (UTC) (edited on 2021-03-24 16:55 (UTC) by bigcajun826)

@delx

I've noticed that sometimes when I reboot my MythTV machine, not all of my tuners are available. A simple restart of mythbackend.service seems to fix it every time. I did a little searching and found that adding "systemd-udev-settle" seems to fix the issue.

Would you consider updating the mythbackend.service unit file like this:

diff --git a/mythbackend.service b/mythbackend.service
index 0ac07b3..e760e77 100644
--- a/mythbackend.service
+++ b/mythbackend.service
@@ -1,7 +1,7 @@
 [Unit]
 Description=MythTV Backend
-Wants=network-online.target mysqld.service
-After=network.target mysqld.service
+Wants=network-online.target mysqld.service systemd-udev-settle.service
+After=network.target mysqld.service systemd-udev-settle.service

bigcajun826 commented on 2021-02-27 15:05 (UTC)

I've been using Arch Linux for almost 9 years now and it never occurred to me that there was a way to have makepkg not put artifacts in the working directory. Thanks @delx, if I would have RTFM here (https://wiki.archlinux.org/index.php/Makepkg#Package_output), I would have found the same answer you gave. And that should work.

delx commented on 2021-02-27 10:29 (UTC)

Hi @bigcajun826. You may want to have a look at the BUILDDIR, PKGDEST and SRCDEST options in either /etc/makepkg.conf or ~/.makepkg.conf.

This will let you control where files for all packages, no need for a .gitignore in each package. Does that solve your problem? :)

bigcajun826 commented on 2021-02-26 15:56 (UTC)

@delx

Would you mind adding a .gitignore file to the source to ignore artifacts of the build? I believe this would be sufficient:

https://github.com/emerkle826/mythtv/blob/gitingnore/.gitignore

delx commented on 2020-11-01 11:46 (UTC) (edited on 2020-11-01 11:46 (UTC) by delx)

@mark.clegg Ah, I didn't notice that the old package had epoch=1. This just means people will need to manually upgrade one time to switch to the new version. I think I'll leave it like that.

@jfabernathy I plan to modify this package to track fixes/32 after MythTV v32 is released. If you want to keep tracking fixes/31 you'd need to fork this package, or maintain your own copy locally.

That version number looks fine to me. It's generated using git-describe. This shows you the number of commits since the v31 tag, followed by 'g' and then the commit hash.