Package Details: mythtv-git 35.0.r0.g2cee6aa-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.000059
First Submitted: 2023-04-10 09:11 (UTC)
Last Updated: 2025-03-02 11:54 (UTC)

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 .. 13 14 15 16 17 18 19 20 21 22 23 .. 32 Next › Last »

chuser commented on 2020-09-25 12:04 (UTC)

libhdhomerun is in both 'depends' and 'optdepends'. Is that necessary - or can it just be in optdepends?

bigcajun826 commented on 2020-09-23 18:53 (UTC)

Just a heads-up for anyone using an NVidia card and the NVidia drivers in Arch. I recently upgraded to the 455.23.04 drivers and started having an issue where I'd have to CTRL+ALT+F2 out to a tty to get my system to "wake up" when I paused video for a while. My MythTV box seemed to just have it's output go to sleep. This even happened if I would turn my TV off and back on again while not playing any content in Myth (with just the menu up).

Not sure what the deal is, but I downgraded back to the 450.66 drivers and the issue has gone away. Again, just an FYI.

Louis commented on 2020-09-21 20:39 (UTC)

It would really help if this package depended on specific versions of eg. x265 and x264. This would force mythtv to rebuild when new versions of these libraries are released and I would discover mythtv was bricked by surprise.

ck2katAUR commented on 2020-06-24 15:43 (UTC)

@bigcajun826. Thank you for your quick reply. As my last attempt did not actually rebuild anything, I have followed a suggestion by @matth, in response to my similar post regarding the perl-net-upnp (AUR) package. I have re-built mythtv with a; -f flag appended to makepkg and that appears to have completed OK - with no more old perl module warnings.

bigcajun826 commented on 2020-06-24 13:52 (UTC)

@ck2katAUR I don't think this package (or any of the AUR packages mythtv depends on) need to do anything other than re-build, as you have done.

ck2katAUR commented on 2020-06-24 13:41 (UTC)

Newbie question. Background: Today, a 'pacman -Syu' invokation updated perl from; 5.30.3-1 to; 5.32.0-1. As expected, I got the warning in the pacman log from the; 'detect-old-perl-modules.hook'. Invoking; pacman -Qo 'usr/lib/perl5/5.30/' , listed this package. I have read; https://www.archlinux.org/news/perl-library-path-change/ . I am not (yet) experienced enough to understand/carry-out the suggestion regarding adding the; perl -V:vendorarch clause to PKGBUILD. So, without that mod, I attempted a package re-build with a; 'git pull' followed by a; 'makepkg -cisL' which returned a; 'nothing to do' response. Question: Is there more to do, or is this package OK to carry-on working with, as it is? I look forward to your help. Thanks.

bigcajun826 commented on 2020-06-11 13:51 (UTC)

@ImNtReal The patch I gave @Taijian has been pushed and should fix the QPainterPath compile issue. If you pull down the latest and recompile, everything should be working again.

bigcajun826 commented on 2020-06-10 21:32 (UTC)

@Taijian, I sent you a patch fix. Let me know if you have trouble with it.

bigcajun826 commented on 2020-06-10 21:06 (UTC)

@Taijian, I just did a full update and tried to rebuild and confirm the issue. It seems that mythpainter.cpp needs to add #include <QPainterPath> and that will fix the issue. I can put together a small patch file and PKGBUILD change for you if you like.

Taijian commented on 2020-06-10 20:54 (UTC)

@ImNtReal: Have you tried rebuilding after the Qt update and if so, does this error persist even after the rebuild?