Package Details: mythtv-git 35.0.r0.g2cee6aa-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.000046
First Submitted: 2023-04-10 09:11 (UTC)
Last Updated: 2025-03-02 11:54 (UTC)

Dependencies (61)

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

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

Taijian commented on 2018-02-28 16:28 (UTC)

uploaded an update. This is weird, because I could swear that originally that checksum worked for 29.1...

RuneArch commented on 2018-02-28 09:01 (UTC)

Yeah, I've stumbled into this too - didn't know that Myth had moved to the AUR now :(

I'm having the same problem as @greenbox - getting hashsum errors - locally generating the checksum, I get:

66fda29bd645b4c9a90600414193f46b99b9b8d60d033828f0eeb44e1c3820a7781d93c7010fc1e0affa83be93896231ba91409ccb7dba38190a5809752beedd

So, if that's the same that others get, then it might just be the PKGBUILD needs updating?

greenbox commented on 2018-02-27 01:45 (UTC)

I have tried to reinstall this package and I keep getting error messages on the shasum check.

Taijian commented on 2018-02-08 22:57 (UTC)

@martyg: Thank you for debugging this! I guess it was worth a shot to try it out, now we know :).

Updated the package again to hopefully fix these issues. As an aside, this also fixes the problems with the plugins-package, so these all build again.

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