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.001516
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 .. 7 8 9 10 11 12 13 14 15 16 17 .. 31 Next › Last »

mark.clegg commented on 2021-08-17 20:15 (UTC) (edited on 2021-08-17 20:50 (UTC) by mark.clegg)

I'm getting this in my mythfrontend.log:

You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'offset FROM recordedseek WHERE chanid = ? AND starttime = ? AND type = ?' at line 1

2021-08-17 20:53:31.234651 E [3266/3266] CoreContext mythdb.cpp:181 (DBError) - DB Error (QueryPositionMap):
Query was:
SELECT mark, offset FROM recordedseek WHERE chanid = 10615 AND starttime = '2021-08-17T18:55:00Z' AND type = 9 ;

Seems like 'offset' has become a reserved word as of MariaDB 10.6

SELECT offset FROM recordedseek

gives the same error, where

SELECT "offset" FROM recordedseek

works...

glenb77 commented on 2021-08-16 21:02 (UTC)

thanks mark. i'll raise an issue on the mythtv-git when i get some time later on, maybe someone will have a look

mark.clegg commented on 2021-08-16 21:00 (UTC)

I haven't done any further investigation as yet, I just responded because I also see the problem editing. For what it's worth, I don't use comm flagging, or kodi. I only do manual edits in mythfrontend.

glenb77 commented on 2021-08-16 20:56 (UTC)

the thing is the seektable is there as are commercial skips. you can still go forward and back and when i look in kodi pvr i could see the skips, i had just lost the ability edit them. i assume same with mark.clegg

glenb77 commented on 2021-08-16 20:55 (UTC)

i had to revert everything back. i assume this is from the mariadb upgrade. i may put it back and look at the log. or maybe mark.clegg will do that. so maybe one of the myth devs could look at it.

mark.clegg commented on 2021-08-16 20:51 (UTC)

@glenb77: same here - 'no seektable' :-(

glenb77 commented on 2021-08-15 14:01 (UTC)

after updating mariadb and qt yesterday and rebuilding mythtv, I have run into a problem where when i want to edit cut list in frontend i get a message 'no seektable'. there is a seektable and the skips are there. rebuilding the seektable makes no difference. I have lost the ability to move and or edit the flagged breaks. Is anyone else seeing this

deadite66 commented on 2021-08-14 09:51 (UTC)

fixed qt-base has been released, mythbackend work fine for me with mariadb 10.6.4.

deadite66 commented on 2021-08-07 05:36 (UTC) (edited on 2021-08-07 05:36 (UTC) by deadite66)

https://bugs.archlinux.org/task/71753

its a qt bug, it doesn't support prepared queries metadata cache yet.

https://bugreports.qt.io/browse/QTBUG-95639

thanks to Antonio Rojas for figuring it out.

ImNtReal commented on 2021-08-06 16:31 (UTC)

I just tried a rebuild with the latest stable qt packages installed. No dice.

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 31 Next › Last »