AptRepository » History » Version 110

« Previous - Version 110/111 (diff) - Next » - Current version
Mark Clarkstone, 2018-09-13 22:53


APT Repositories

Official Repository

The official deb packages are built using Doozer. Our repositories are provided by Doozer (on apt.tvheadend.org) and Bintray.

Repository Status

(!) 9/13/2018:

There appears to be an issue with Bintray, you may get 403 forbidden when trying to install. We're looking into it. Update: we hit our quota :(, asked bintray for assistance.

Build Types and Versions

Please read the following:-

  • You can add more than one repository (recommended)!
  • It's advised that you use release or stable, only use unstable if you want bleeding-edge & don't mind breakages.
  • If using unstable be sure to install tvheadend-dbg. If reporting crashes with unstable, please include proper debugging & trace information.

Bintray

Build Type Description Version Repo Component Notes
release The latest version marked for release 4.2.6 release-4.2
stable The latest stable code with changes/fixes between releases 4.2.6-x~githash stable-4.2
unstable This is the current development "bleeding-edge" 4.3.x unstable

Doozer

Build Type Description Version Repo Component Notes
stable The latest stable code with changes/fixes between releases 4.2.6-x~githash stable Jessie, Stretch, Trusty, Xenial and Bionic only.
unstable This is the current development "bleeding-edge" 4.3.x unstable

Supported Distributions and Architectures

The official repositories support the following distributions and architectures.

Distribution Architecture Notes
Debian Jessie "jessie" (8.x) - i386
- amd64
Debian Stretch "stretch" (9.x) - i386
- amd64
Ubuntu Xenial "xenial" (16.04) - i386
- amd64
- armhf
- arm64
- armhf/arm64 do not have transcoding support (yet).
- Ubuntu arm builds are only available from Doozer.
Trusty "trusty" (14.04) - i386
- amd64
Bionic Beaver "bionic" (18.04) - amd64
- i386
i386 is only available from Bintray

Where are the builds for my distro/arch?
At the moment the Doozer build system only has support for a limited number of build targets. New targets will be added as soon as possible. Take a look at the 3rd-party repos below or build your own.

Usage

1. Install GPG keys

Bintray

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 379CE192D401AB61 

Doozer (apt.tvheadend.org)

wget -qO- https://doozer.io/keys/tvheadend/tvheadend/pgp | sudo apt-key add -


If you see something like the following:

Executing: /tmp/apt-key-gpghome666/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 379CE192D401AB61
gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory
gpg: connecting dirmngr at '/run/user/0/gnupg/d.1234/S.dirmngr' failed: No such file or directory
gpg: keyserver receive failed: No dirmngr

You need to install dirmngr:

sudo apt-get install dirmngr

Once installed add the key again, it should succeed this time.

2. Choose build type add the repository

Bintray

echo "deb https://dl.bintray.com/tvheadend/deb DISTRO REPO-COMPONENT" | sudo tee /etc/apt/sources.list.d/tvheadend.list

Example:

echo "deb https://dl.bintray.com/tvheadend/deb xenial stable-4.2" | sudo tee /etc/apt/sources.list.d/tvheadend.list

Doozer

echo "deb http://apt.tvheadend.org/REPO-COMPONENT DISTRO main" | sudo tee -a /etc/apt/sources.list.d/tvheadend.list

Example:

echo "deb http://apt.tvheadend.org/unstable xenial main" | sudo tee -a /etc/apt/sources.list.d/tvheadend.list


  • Replace DISTRO with the distribution's code name (as quoted in Supported Distributions and Architectures). Replace REPO-COMPONENT with the desired build type.
  • Watch out for subtle differences though, be sure to check the repository has your desired build type and component.
  • Please pay special attention to the difference between stable-4.2 (on Bintray) and stable (on Doozer), and make sure you use the text in the Repo Component column and not Build Type (in the Build Types and Versions tables).

3. Refresh packages and install

sudo apt-get update
sudo apt-get install tvheadend

Note: if you install more than one suite you will only ever get packages from the one holding the most recent version number, so the order of priority would be:

unstable > stable-4.2 > stable

Help

Please open an issue or join the IRC channel to report problems with the official repository.

Unofficial Repositories

3rd-party unofficial repositories.

Ubuntu PPA

Unofficial PPAs are provided by Michael Marley that provide packages for Artful, Zesty, Yakkety, and Xenial for the amd64, arm64, armhf, i386 and ppc64el architectures.

Usage

First, pick either the Stable or Unstable build:

For the Stable PPA containing daily builds from the latest stable branch:

sudo apt-add-repository ppa:mamarley/tvheadend-git-stable

For the Unstable PPA containing daily builds from master:

sudo apt-add-repository ppa:mamarley/tvheadend-git

Then, for both:

Update your packages:

sudo apt update

Install:

sudo apt install tvheadend

Help

If you experience issues with this PPA please contact Michael on IRC (mamarley in #hts on Freenode) or Launchpad.

Raspberry Pi / Raspbian armhf

Unofficial Raspbian packages are provided by mpmc for both Raspbian Jessie and Stretch.

  • These builds are done manually and may lag behind, however I'll do my best to keep them updated until the official repo is able to provide the packages.
  • There's no transcoding support, mainly because the Pi isn't powerful enough to do software transcoding and hardware transcoding is not yet available.
  • There is no changes to the code whatsoever for these builds.
  • Make sure to enter the distro as raspbianjessie/raspbianstretch and not jessie/stretch.

Usage

To use this repository follow the official usage guide - for bintray, but change the repository URL from https://dl.bintray.com/tvheadend/deb to https://dl.bintray.com/mpmc/deb and replace DISTRO with raspbianstretch or raspbianjessie.

Example:

echo "deb https://dl.bintray.com/mpmc/deb raspbianstretch stable-4.2" | sudo tee /etc/apt/sources.list.d/tvheadend.list

Help

If you experience issues with this repository contact mpmc on github or send a message on IRC (mpmc in #hts on Freenode).