Package Details: mythtv 1:30.0-6

Git Clone URL: https://aur.archlinux.org/mythtv.git (read-only)
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.002447
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

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

bigcajun826 commented on 2019-05-22 19:16

I think this patch will work until a new mythtv 30 bundle is ready: https://gist.github.com/emerkle826/831061ae347a7a8dd98cc472d1ff3a24

Shouldn't have to downgrade exiv2 in Arch with this.

UPDATE: Taijian, feel free to pull from my clone here: https://github.com/emerkle826/mythtv/compare/exiv2-fix

keepitsimpleengr commented on 2019-05-22 19:10

Found the problem with archlinux compilations of mythtv Downgraded package exiv2 (0.27.1-1 => 0.26-2)

RuneArch commented on 2019-05-22 08:41

Reverting to exiv2 0.26-2 worked for me, until that Myth commit makes it's way into the AUR package.

boomshalek commented on 2019-05-21 20:21

Compilation has failed me today with an up to date system. Possible culprit could be this commit (maybe it should be reversed): https://github.com/MythTV/mythtv/commit/fc79822ce4c8775361053d1bdd8d9dce2dc44ec1

imagemetadata.cpp: In constructor ‘PictureMetaData::PictureMetaData(const QString&)’: imagemetadata.cpp:315:19: error: ‘Error’ in namespace ‘Exiv2’ does not name a type catch (Exiv2::Error &e) ^~~~~ In file included from /usr/include/qt/QtCore/qcoreapplication.h:43, from /usr/include/qt/QtCore/QCoreApplication:1, from imagemetadata.h:12, from imagemetadata.cpp:1: imagemetadata.cpp:317:74: error: ‘e’ was not declared in this scope LOG(VB_GENERAL, LOG_ERR, LOC + QString("Exiv2 exception %1").arg(e.what())); ^ imagemetadata.cpp:317:9: note: in expansion of macro ‘LOG’ LOG(VB_GENERAL, LOG_ERR, LOC + QString("Exiv2 exception %1").arg(e.what())); ^~~ make[2]: [Makefile:1781: obj/imagemetadata.o] Error 1 make[2]: Leaving directory '/tmp/trizen-chris/mythtv/src/mythtv-30.0/mythtv/libs/libmythmetadata' make[1]: [Makefile:301: sub-libmythmetadata-make_first] Error 2 make[1]: Leaving directory '/tmp/trizen-chris/mythtv/src/mythtv-30.0/mythtv/libs' make: *** [Makefile:68: libs] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

ChrisDennis commented on 2019-05-03 20:31

Thanks for your reply, bigcajun826.

Yes, I know about updating AUR packages, these were build-time, not run-time, errors, and I had updated everything else and rebooted.

What has worked for me is git-cloning the mythtv repo from AUR again and running makepkg --cleanbuild --install as you suggested.

bigcajun826 commented on 2019-05-03 18:48

@ChrisDennis the errors you show seem more like issues trying to run MythTV after an update. See Taijian's pinned comment.

If you have updated the rest of the system (i.e. pacman -Syu), I suggest you reboot, then try to rebuild and install MythTV again (makepkg --cleanbuild --install).

That should get your going again.

P.S. You shouldn't be symlinking library files. If you find yourself going down that route, with this package at least, you probably need to rebuild (again, see Taijian's pinned comment).

ChrisDennis commented on 2019-05-03 17:06

I can't compile MythTV today, after updating the rest of the system.

It gave these errors:

/usr/bin/ld: warning: libx264.so.155, needed by /usr/lib/libmythbase-30.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libvpx.so.5, needed by /usr/lib/libmythavcodec.so, not found (try using -rpath or -rpath-link)

so I made symbolic links from the current versions (libx264.so.157 and libvpx.so.6), and now I get

/usr/bin/ld: /usr/lib/libmythavcodec.so: undefined reference to `x264_encoder_open_155'

which looks like a hard-coded reference to something that's only in libx264.so.155.

I also see

WARNING: Failure to find: ../../../mythtv/libs/libmythbase/version.h

which may or may not be relevant.

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.

Taijian commented on 2019-03-08 15:13

@sultanoswing: I should probably sticky this, but here goes again: If a package, that an AUR package depends upon receives a major (i.e. ABI/API breaking) update, you need to rebuild the AUR package afterwards. This is what package maintainers do, and for your AUR packages, that's you. So I'd advise against symlinking anything, and to instead do the right thing: Rebuild!

sultanoswing commented on 2019-03-08 08:52

Another heads up - wouldn't start after latest libvpx update with the error: "mythfrontend: error while loading shared libraries: libvpx.so.5: cannot open shared object file: No such file or directory".

Workaround: ln -s /usr/lib/libvpx.so.6 /usr/lib/libvpx.so.5