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

mark.clegg commented on 2020-01-17 19:06 (UTC)

@keepitsimpleengr: The workaround still works for me. I notice that x264 3:0.159.r2991.1771b55-1 came in around the same time. I'm pretty sure that would break myth, requiring a package re-compile/install. If that's the case, and you applied the workaround to one of the pre-installed themes (in /usr/share/mythtv...) then you'll have to re-apply the workaround, as the themes will have been re-installed.

keepitsimpleengr commented on 2020-01-16 23:10 (UTC)

@hamelg Your workaround has stopped working :(

today's [2020-01-16T05:59:54-0800] [ALPM] upgraded qt5-declarative (5.14.0-2 -> 5.14.0-3)

mark.clegg commented on 2020-01-01 16:30 (UTC)

@hamelg: Good find, I think that also means it's not just arch users that are affected, so more likely an upstream issue?

hamelg commented on 2020-01-01 14:53 (UTC)

There is a discussion and a mitigate workaround about white rectangle issue here : https://forum.mythtv.org/viewtopic.php?f=36&t=3505

hamelg commented on 2019-12-30 22:54 (UTC)

yes,the latest kf5 libraries are compiled with 5.14. There is no forward compatibility across minor released, only backward.

I found this information here : https://wiki.qt.io/Qt-Version-Compatibility#Binary_Compatibility_Guidelines

So, it means when upgrading minor release qt libraries you don't need rebuilding application.

Thanks

mark.clegg commented on 2019-12-30 22:50 (UTC)

@taijian: I suspect you are correct. I believe @hamlet has already done this. (Thanks hamelg)

Taijian commented on 2019-12-30 22:46 (UTC)

@mark.clegg: Unfortunately it will be a couple of days before I will get a chance to really muck around with bug testing because of travel... Could you (or somebody else with an affected setup) please file an upstream bug report (complete with version numbers and logs) and reference it here? Because to me this looks very much like an upstream issue and not something that is inherent in the PKGBUILD.

mark.clegg commented on 2019-12-30 22:42 (UTC)

@hamelg: Unfortunately that doesn't surprise me. Arch doesn't really like rolling back individual package versions, as everything is built in unison, so dependencies will be broken by doing this, unless you roll the whole system back to a point in time when qt was at 5.13. My myth boxes are dedicated so the only thing depending on qt would be myth itself, which as previously observed, needed a rebuild after the rollback,

hamelg commented on 2019-12-30 22:15 (UTC) (edited on 2019-12-30 22:16 (UTC) by hamelg)

@mark.clegg

Reverted to qt5 5.13 has broken my kde.

My session doesn't start with errors like that :

kf5.kded: Could not load kded module "keyboard":"Cannot load library /usr/lib/qt/plugins/kf5/kded/keyboard.so: (/usr/lib/libQt5Core.so.5: version `Qt_5.14' not found (required by /usr/lib/libKF5Plasma.so.5))" (library path was:"/usr/lib/qt/plugins/kf5/kded/keyboard.so")

It seems the latest kf5 libraries needs qt 5.14 at run-time. do you confirm ?

hamelg commented on 2019-12-29 14:21 (UTC) (edited on 2019-12-29 15:52 (UTC) by hamelg)

If you click with the right mouse button on the white rectangle you get a popup menu with an entry "reload". It's very strange ...

EDIT : I recorded an issue here : https://code.mythtv.org/trac/ticket/13544

« First ‹ Previous 1 .. 14 15 16 17 18 19 20 21 22 23 24 .. 31 Next › Last »