Package Details: tvheadend-git 4.3.r2354.gadef81b-1

Git Clone URL: https://aur.archlinux.org/tvheadend-git.git (read-only, click to copy)
Package Base: tvheadend-git
Description: TV streaming server and DVR
Upstream URL: https://tvheadend.org/
Keywords: dvb iptv pvr streaming tv
Licenses: GPL-3.0-or-later
Conflicts: tvheadend
Provides: tvheadend
Submitter: zman0900
Maintainer: willemw
Last Packager: willemw
Votes: 28
Popularity: 0.000004
First Submitted: 2015-08-10 20:59 (UTC)
Last Updated: 2024-08-13 12:33 (UTC)

Pinned Comments

francoism90 commented on 2021-03-21 14:16 (UTC) (edited on 2021-03-21 14:16 (UTC) by francoism90)

Warning: if you have previously used this package, you need to reinstall! Sorry for introducing breaking changes, but hopefully the introduced changes will provide a better experience for most users. :)

Backup your configs (if needed) before performing the upgrade!

Changes:

  • TVHeadend will be installed to /var/lib/tvheadend instead of /usr/share/tvheadend
  • Package will create the system user tvheadend (member of group video) with config files stored in /etc/tvheadend, it will not use a home directory anymore.
  • By using sysusers.d and tmpfiles.d permissions should be easier to manage.
  • tvheadend.service now includes -C by default.
  • Added some missing deps

If you have any questions or suggestions, please let me know. :)

luciferin commented on 2017-04-06 14:01 (UTC) (edited on 2019-08-14 12:21 (UTC) by luciferin)

I started up a wiki page for Tvheadend. Input and help is welcome.

https://wiki.archlinux.org/index.php/Tvheadend

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 17 Next › Last »

mercora commented on 2019-04-15 05:07 (UTC) (edited on 2019-04-15 05:21 (UTC) by mercora)

it should be noted that Tvheadend runs with the "hts" user using this package. That means if you try to run it with the -C flag you need to make sure its running with the same user. TBH i think this should be the default.

"If no user account exists then create one with no username and no password. Use with care as it will allow world-wide administrative access to your Tvheadend installation until you create or edit the access control from within the Tvheadend web interface."

Arch packages never activate themselves on installation automatically like they do on Debian for example. So explicit action is required to have it exposed like described. The alternative is to create a superuser file in the configuration directory that looks like this:

{ "username": "supersuser", "password": "verysecurepassword" }

So you either do that prior to starting it or start with the first-run flag anyhow. I am not sure if the superuser config file still works when using this flag though, so that might need to be checked first to make the more paranoid people among us happy.

mrclrchtr commented on 2019-04-14 14:28 (UTC)

"If you build Tvheadend from source and just execute it, it won’t let anyone in."

https://tvheadend.org/projects/tvheadend/wiki/Faq

You need to start tvheadend with "-C" the first time.

troydwill commented on 2019-04-11 09:38 (UTC)

The administration web page at http://localhost:9981 after install is requiring a username and password. What are they?

mercora commented on 2019-03-18 11:45 (UTC)

to clarify this up for me i looked it up in the code and documentation. libsystemd as said is used to support systemd specific features like socket activation and a software watchdog in this case. While the socket activation appears as of not much use, at least to me, the software watchdog could be interesting in cases where the process just locks up somehow. The library is practically available on all arch installations so it might just as well could be enabled if desired :)

francoism90 commented on 2019-03-16 14:20 (UTC)

@mercora Thanks for the info! I wasn't aware why this flag existed, it indeed seems unwanted to be enabled. :)

mercora commented on 2019-03-16 10:18 (UTC) (edited on 2019-03-18 11:27 (UTC) by mercora)

i am pretty sure libsystemd is also used for socket activation which is not used in the current systemd unit file for this package either. It therefore should be safe to disable the dependency. If you want to enable this support there is a comment in the unit file about how to make use of these features.

zman0900 commented on 2019-03-14 23:22 (UTC)

It's been quite a while ago so I don't remember the details, but I did try that flag in the past. I don't remember for sure, but I don't think it worked.

From what I can see in the service file, it sounds like this just enables some watchdog feature of systemd?
https://github.com/tvheadend/tvheadend/blob/master/rpm/tvheadend.service

Does anyone has a use for this? I'm not opposed to enabling it, but I'd rather not do it without good reason since it appears to require changes to the service file too.

francoism90 commented on 2019-03-02 14:38 (UTC)

@anthonytex That does sound useful? :)

anthonytex commented on 2019-03-02 10:52 (UTC)

@francoism90 that flag is used to enable the use of systemd's apis and access to some features like, in this case, a software watchdog provided by systemd's daemon

francoism90 commented on 2019-03-02 10:40 (UTC) (edited on 2019-03-02 10:43 (UTC) by francoism90)

Should the flag libsystemd_daemon be enabled in configure? It states libsystemd_daemon no on compile, although I still don't why, because the systemd file is being compiled.

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 17 Next › Last »