Package Details: mythtv 1:30.0-6

Git Clone URL: https://aur.archlinux.org/mythtv.git (read-only, click to copy)
Package Base: mythtv
Description: A Homebrew PVR project
Upstream URL: https://www.mythtv.org/
Keywords: mythtv
Licenses: GPL
Conflicts: mythplugins-mythvideo, myththemes
Replaces: mythplugins-mythvideo, myththemes
Submitter: Barthalion
Maintainer: Taijian
Last Packager: Taijian
Votes: 27
Popularity: 0.000939
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 »

keepitsimpleengr commented on 2020-01-18 13:48

@mark.clegg The workarounds are applied after each mythtv package recompile. On the four mythtv clients (1 archlinux-intel, 3 manjaro-intel&2·amd) the workaround reapplied and still does not work :( Bug report @ https://code.mythtv.org/trac/ticket/13544 tags this bug as minor with no one assigned Forum @ https://forum.mythtv.org/viewtopic.php?f=36&t=3505 also talks about the workaround Looks like only users affected are those who keep their systems fully updated

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

@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

@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

@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

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

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

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

Taijian commented on 2019-12-30 22:46

@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

@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

@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 ?