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)

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 .. 22 23 24 25 26 27 28 29 30 31 Next › Last »

Taijian commented on 2018-03-12 07:17 (UTC)

As @mark.clegg already pointed out: Unfortunately, based on the way linked library versions work, whenever one of the packages that this one is build against gets updated, you'll also have to rebuild mythtv.

In this case, x265 got updated to a new version over the weekend. The maintainer of ffmpeg in extra was notified of this and put out a rebuild version of ffmpeg alongside it. For the AUR, it does not work like this. Here, you are your own maintainer and have the rebuild your packages yourself, whenever their dependencies get updated and the linked libraries break as a consequence.

keepitsimpleengr commented on 2018-03-11 20:08 (UTC) (edited on 2018-03-11 20:12 (UTC) by keepitsimpleengr)

@mark.clegg

I use the git clone method (https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_packages)

Rebuilding on one client failed, however on a second client it was successful.

Go figure

BTW I have a third client running on Manjaro 64bit, which did not fail in this manner.

glenb77 commented on 2018-03-11 18:40 (UTC)

i had same issue over weekend. i build on a different machine then where backend runs. so first i update machine i am building on to all current on arch. then i delete directory of prior builds and create new from snapshot file. then i do makepkg. and i reinstall on all machines with myth after upgrading those. and everything works again. i also have to do same with plugins as i ran into same issue.

mark.clegg commented on 2018-03-11 18:15 (UTC)

@keepitsimpleengr: It didn't for me first time. I had to delete the previous source files, - i.e. force a clean build. I guess because no source files have changed, the rebuild finds nothing to do, unless you "clean" first.

keepitsimpleengr commented on 2018-03-11 17:42 (UTC)

@mark.cleg

Rebuilding mythtv did not work for me.

keepitsimpleengr commented on 2018-03-11 17:38 (UTC)

workaround to mythfrontend: error while loading shared libraries: libx265.so.146: cannot open shared object file: No such file or directory

$ sudo pacman -U x265-2.6-1-x86_64.pkg.tar.xz ffmpeg-1:3.4.2-1-x86_64.pk

loading packages...

warning: downgrading package x265 (2.7-1 => 2.6-1)

warning: downgrading package ffmpeg (1:3.4.2-2 => 1:3.4.2-1)

mark.clegg commented on 2018-03-11 17:37 (UTC)

Same here @keepitsimpleengr. Rebuilding and reinstalling myth fixes it.

keepitsimpleengr commented on 2018-03-11 17:19 (UTC) (edited on 2018-03-11 17:22 (UTC) by keepitsimpleengr)

-as of yesterday (3/10)

$ mythfrontend

mythfrontend: error while loading shared libraries: libx265.so.146: cannot open shared object file: No such file or directory

--

[root@KISE-005 ~]# cat /var/log/pacman.log | grep 'upgraded mythtv' | grep 2018-0 [2018-01-08 06:18] [ALPM] upgraded mythtv (1:29.0-4 -> 1:29.0-5) [2018-01-15 10:27] [ALPM] upgraded mythtv (1:29.0-5 -> 1:29.0-6) [2018-01-17 08:45] [ALPM] upgraded mythtv (1:29.0-6 -> 1:29.0-7) [2018-02-01 09:17] [ALPM] upgraded mythtv (1:29.0-7 -> 1:29.1-1) [2018-02-08 08:25] [ALPM] upgraded mythtv (1:29.1-1 -> 1:29.1-2) [2018-02-09 08:36] [ALPM] upgraded mythtv (1:29.1-2 -> 1:29.1-3) [2018-03-01 07:30] [ALPM] upgraded mythtv (1:29.1-3 -> 1:29.1-4)

[root@KISE-005 ~]# cat /var/log/pacman.log | grep libx2 | grep 2018-0

[2018-01-11 11:13] [ALPM] upgraded libx264-all (2:148.20170521-1 -> 2:152.20171224-1) [2018-02-08 07:56] [PACMAN] Running 'pacman -R libx264-10bit' [2018-02-08 07:57] [PACMAN] Running 'pacman --color auto -S extra/libx264-10bit' [2018-02-08 07:57] [PACMAN] Running 'pacman --color auto -S extra/libx264-10bit' [2018-02-13 13:12] [ALPM] upgraded libx264 (2:148.20170521-1 -> 2:152.20171224-1)

bigcajun826 commented on 2018-03-01 01:38 (UTC) (edited on 2018-03-01 01:39 (UTC) by bigcajun826)

Looks like the bundles are different from a few days ago as compared to today:

diff -r dump1/mythtv-29.1/mythtv/EXPORTED_VERSION dump2/mythtv-29.1/mythtv/EXPORTED_VERSION

2c2
< BRANCH=" (tag: v29.1)"
---
> BRANCH=" (tag: v29.1, fixes/29)"

bigcajun826 commented on 2018-03-01 01:32 (UTC) (edited on 2018-03-01 01:32 (UTC) by bigcajun826)

I think the checksum has changed. I built this package on Feb 10, 2018 and the bundle downloaded then is different than the one I just pulled today:

-rw-r--r-- 1 arch users 105616234 Feb 28 19:28 mythtv-29.1.tar.gz

-rw-r--r-- 1 arch users 105616252 Feb 10 12:32 mythtv-29.1.tar.gz.backup

not by much, but any change will give a different checksum

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 Next › Last »