Package Details: mythtv 1:30.0-6

Git Clone URL: (read-only)
Package Base: mythtv
Description: A Homebrew PVR project
Upstream URL:
Keywords: mythtv
Licenses: GPL
Conflicts: mythplugins-mythvideo, myththemes
Replaces: mythplugins-mythvideo, myththemes
Submitter: Barthalion
Maintainer: Taijian
Last Packager: Taijian
Votes: 27
Popularity: 0.002587
First Submitted: 2018-01-07 17:35
Last Updated: 2019-05-25 12:53

Dependencies (47)

Sources (8)

Pinned Comments

Taijian commented on 2019-03-09 11:53

Important Note on AUR packages in general:

For AUR packages, you - as the user installing the package - assume the role that a package maintainer has for regular repo packages.

That means that the responsibility to recompile the package whenever a package B that your package depends on changes. For repo packages, maintainers do this for you and re-release the package with an updated build number (e.g. -1 to -2). AUR mainainers will not do this, because there is no change to the PKGBUILD. You need to recompile locally, whenever this happens.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

glenb77 commented on 2019-11-02 18:53

@boomshalek 30 fixes is the mythtv-git aur package

boomshalek commented on 2019-11-02 18:34

I could resolve my previous issues with killing the backend when running livetv which were of a different problem. @Taijian: Is it possible to update the package to 30-fixes? So far I am modifying your PKGBUILD in order to use instead of 30.0-nofixes with cheerypicked patches.

bigcajun826 commented on 2019-10-05 15:20

boomshalek, I'm not having the issue you are having, but maybe this is relevant:

If so, you could try downgrading MariaDB to 10.3, though that might be a bit of a pain, depending on what else you have running on your Myth backend. Sorry I can't help much more.

boomshalek commented on 2019-09-08 19:26

I recompiled. As soon as I start LiveTV the backend somehow manages to kill the mariadb-server. WTH?! I tried to revert to older verstions but the problem persists. Can someone confirm this problem or is it just my system?

martyg commented on 2019-08-26 20:13

Been seeing a lot of this in my logs recently:

mythpreviewgen[]: OMX: OMX_Init error OMX_ErrorInsufficientResources mythpreviewgen[]: OMX:0 Invalid OpenMAX context

OpenMax is ARM/RPi specific technology, so I just added a --disable-openmax in the configure stanza. Warnings are now gone.

I don't think these warnings were operation-affecting in any way, but they were n the way from me tracking down other unrelated stuff.

keepitsimpleengr commented on 2019-05-25 19:44

@Taijian all four complied successfully ~ thanks for all the good work Congrats on the new home.

Taijian commented on 2019-05-25 13:13

OK, should build - and then also run - again... Sorry for the delay, we just bought a house...

keepitsimpleengr commented on 2019-05-24 14:27

exiv2-0.27 is the current version in repository and is required by gimp-2.10.10 mythtv 1:30.0-5 requires exiv2-0.26 to run

...from my cache: -rw-r--r-- 1 root root 1647024 May 18 00:03 exiv2-0.27.1-1-x86_64.pkg.tar.xz -rw-r--r-- 1 root root 1647588 Sep 17 2017 exiv2-0.26-2-x86_64.pkg.tar.xz

mosh5382 commented on 2019-05-23 03:16

I can confirm that bigcajun826 patch worked. I was able to build the package and mythtv is working correctly.

Taijian commented on 2019-05-22 22:13

Thanks everyone for bringing the issue and the (probable) fix up - I'll update this as soon as I'm able, but RL has kinda kept me busy these last few days... Sorry!