Package Details: mythtv-git 35.0.r44.g7e93f0d-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.000000
First Submitted: 2023-04-10 09:11 (UTC)
Last Updated: 2025-11-22 14:42 (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

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

mark.clegg commented on 2025-11-22 10:39 (UTC)

@JohnLBergqvist, makes sense. Thanks.

JohnLBergqvist commented on 2025-11-22 09:58 (UTC) (edited on 2025-11-22 10:01 (UTC) by JohnLBergqvist)

@mark.clegg I'll bear that in mind, but I'd like this package to reflect what the "default" is, which is still qt5 I believe. However for the upcoming v36 release which should be early 2026, I will consider switching then, along with migrating to their new build process with cmake

mark.clegg commented on 2025-11-22 09:45 (UTC)

As it's probably likely that we'll see more of the qt5 packages dropped from extra and moved to AUR over the coming months. Is it worth considering incorporating @hedgepigdaniel's changes and switching the mythtv-git build over to qt6 anyway?

JohnLBergqvist commented on 2025-11-22 03:24 (UTC) (edited on 2025-11-22 03:25 (UTC) by JohnLBergqvist)

@hedgepigdaniel Actually, looking at this thread: https://lists.mythtv.org/pipermail/mythtv-users/2025-February/415098.html, qt5-webengine is only needed for mythbrowser which is a separate package on AUR (if qt5-webengine is not present or you are building with qt6, mythbrowser isn't built - but it wouldn't be built anyway here). As a result I'll simply just remove python-py5-qtwebengine and that will resolve the issue. I'll recommend that qt5-webengine is made a dependency of mythplugins-mythbrowser instead (I don't maintain that package and have no desire to start maintaining it)

hedgepigdaniel commented on 2025-11-22 03:21 (UTC)

@JohnLBergqvist

I'm not sure if it's related (I suspect not), but when building without disabling AMF I got the following error:

D   libavcodec/libmythavcodec.so.61
/usr/bin/ld: libavcodec/amfenc_av1.o: in function `GetDefaultChannelLayout':
/usr/include/AMF/core/AudioBuffer.h:89: multiple definition of `GetDefaultChannelLayout'; libavcodec/amfenc.o:/usr/include/AMF/core/AudioBuffer.h:89: first defined here
/usr/bin/ld: libavcodec/amfenc_h264.o: in function `GetDefaultChannelLayout':
/usr/include/AMF/core/AudioBuffer.h:89: multiple definition of `GetDefaultChannelLayout'; libavcodec/amfenc.o:/usr/include/AMF/core/AudioBuffer.h:89: first defined here
/usr/bin/ld: libavcodec/amfenc_hevc.o: in function `GetDefaultChannelLayout':
/usr/include/AMF/core/AudioBuffer.h:89: multiple definition of `GetDefaultChannelLayout'; libavcodec/amfenc.o:/usr/include/AMF/core/AudioBuffer.h:89: first defined here

The referenced files are owned by amf-headers-git - not sure what is at fault.

JohnLBergqvist commented on 2025-11-22 03:06 (UTC)

@hedgepigdaniel Is there a reason why you're explicitly disabling AMF as well? Is it incompatible with qt6?

hedgepigdaniel commented on 2025-11-22 02:06 (UTC)

The transitive dependency qt5-webengine has been removed from extra and is now in the AUR. Compiling it requires ridiculous resource usage, since it involves building Chromium.

I've made a fork here to configure mythtv to build against qt6 rather than qt5, which solves the problem: https://aur.archlinux.org/packages/mythtv-qt6-git

@JohnLBergqvist if you could incorporate the changes here that would be great: https://aur.archlinux.org/cgit/aur.git/commit/?h=mythtv-qt6-git&id=6d7e456d1ea053d3ada6cce5a8e18749e89ef981

JohnLBergqvist commented on 2025-05-05 12:29 (UTC)

@korimitsu It built fine after I cleared the existing src directory from my previous build and rebuilt the package from scratch.

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