[Unofficial] Raspberry Pi / armhf builds

Added by Jonathan Thomson 12 months ago

As a way of giving something back to the community, I have set up a bintray repository for some Raspberry Pi / armhf builds of TVHeadend. I am by no means promising to keep this bang up to date, but I'll add releases as and when I can.

Check the changelog below for details about what packages are in this repository - the aim is to maintain a stable and unstable branch.

I have implemented a BuildBot script on the Pi that is building these files. The purpose of the BuildBot is to check out the new code, compile it into a redistributable Debian (.deb) archive and automatically publish it to Bintray. This is an ALPHA-like trial at the moment as I need to wait for a change to the 4.1 branch to check that it works end-to-end. The benefit of this is that new builds will be uploaded to Bintray within 24 hours of the code being added to Github - I'll review these timings later providing the script works as expected, with the aim of doing 4 build cycles per branch (4 stable and 4 unstable) per day - that will cut the 24 hour wait down to a maximum of 8 hours delay between Github and my Bintray repository.

To set up my this repository;

$ sudo nano /etc/apt/sources.list

add the following to the sources.list file

deb https://dl.bintray.com/djbenson/deb wheezy stable (for the stable wheezy branch)
deb https://dl.bintray.com/djbenson/deb wheezy unstable (for the unstable/nightly wheezy branch)

NOTE: Remember, even if you are running Jessie, you MUST add the wheezy repository to get my builds. I will move to Jessie at some point but for now wheezy builds work fine on Jessie and cover the two most used Raspbery Pi operating systems in use at the moment.

Save and exit (CTRL+O then CTRL+X)

The following may be necessary on a clean Debian install (thanks to Mike Somerville for this tip)

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

This adds the keys required to download software from bintray without receiving signature errors.

$ sudo apt-get update
$ sudo apt-get install tvheadend

If you get an error like this;

E: The method driver /usr/lib/apt/methods/https could not be found.
N: Is the package apt-transport-https installed?

Then run

$ sudo apt-get install apt-transport-https

Then run the above commands again.

You may get a package verification error - until I work out how to fix that, simply enter "Y" at the prompt.

Some caveats/useful information:
  1. This repository supports only armhf builds at the moment
  2. Regardless of whether you are running Wheezy or Jessie, you MUST enable only the wheezy branch to receive my builds
  3. Both stable (4.0) and unstable/git-master (4.1) branches are supported
  4. Binaries are now compiled on native Raspberry Pi hardware (Pi 1 B+) using Raspbian Wheezy, cross-compilation caused me too many headaches
  5. Due to a bug in the GCC compiler, ffmpeg_static is disabled in my builds. This shouldn't cause many issues as the Pi (even version 3) is low-powered and not really capable of reliable transcoding duties. I think (but cannot confirm) that TVHeadend will use ffmpeg if it's installed on your system despite it not being compiled into the TVHeadend binary (if somebody can confirm this I'd appreciate it)
--prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libexecdir=${prefix}/lib/tvheadend --disable-maintainer-mode --disable-dependency-tracking --disable-ffmpeg_static --enable-hdhomerun_static --enable-dvbcsa --enable-bundle

Changelog (As of 2016-11-24, builds are added to Bintray automatically so this changelog will no longer be updated with build-specific information)

2016-11-24 Enabled automated build/deployment script which will take care of adding new builds to Bintray
2016-11-23 Switched to native Raspbery Pi hardware (Pi v1 B+) instead of cross-compiling
2016-11-22 armhf build 4.1-2331-gf2371cf added to the repository
           armhf build 4.1-2330~g3a113b6 added to the repository
2016-11-18 armhf build 4.0.9-13~g64fec81 added to the repository
           armhf build 4.1-2328~gca5f094 added to the repository (see note on page 2!)
2016-09-07 armhf build 4.0.9-12~ge5400e2 added to the repository
2016-09-06 only wheezy builds will be published going forward
2016-09-06 armhf build 4.1-2236~g817f67e added to the repository
2016-07-21 armhf build 4.1-2141~g01c26fc~jessie added to repository
2016-07-19 armhf build 4.1-2141~g01c26fc added to repository
2016-07-01 armhf build 4.1-2140~gf34fac1 added to repository
2016-06-30 armhf build 4.1-2135~g631b6b5 added to repository
           armhf build 4.0.9-5~g4749320 added to repository


Replies (87)

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Jonathan Thomson 7 months ago

armhf build 4.0.9-13~g64fec81 added to the repository. Struggling to get 4.1 to build.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Jonathan Thomson 7 months ago

I've added 4.1-2328~gca5f094 to the repository BUT it may not work. This builed DOES NOT contain ffmpeg-static so you will need to have ffpmeg on your system for it to work (you may need to sudo apt-get install -f) after installing this version to fix dependencies.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Josu Lazkano 7 months ago

Hello,

I just installed this repository (jessie unstable) in my Raspberry Pi Model B (Rev 2.0, 512Mb), this the versión I installed: 4.1-2141-g01c26fc

The problema is that it doesn't start:

# /etc/init.d/tvheadend start
Starting tvheadend (via systemctl): tvheadend.service.

But there is no tvheadend process running:

# ps -e | grep tvhead

I am missing something?

I will really appreciate your help.

Best regards.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Jonathan Thomson 7 months ago

Can you try running the tvheadend binary manually;

/usr/bin/tvheadend -f -p /var/run/tvheadend.pid -u $TVH_USER -g $TVH_GROUP

You'll get a better idea of what is happening with the service.

The above assumes /etc/default/tvheadend has your username and group in, if not, replace $TVH_USER with your tvheadend user (hts?) and $TVH_GROUP with the group of the tvheadend user (hts or video?)

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Josu Lazkano 7 months ago

Thanks,

I get this:

# tvheadend -f -p /var/run/tvheadend.pid -u hts -g hts
Illegal instruction

I am missing something? Need I configure something else?

Best regards.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Josu Lazkano 7 months ago

Hello,

I want to install thveadend to share my satellite channels to Kodi clients.

I have a Raspberry Pi Model B (Rev 2.0, 512Mb) with one USB DVB-S2 device. I installed "2016-09-23-raspbian-jessie-lite.img" on it and install tvheadend this way:

Update the system:

apt-get update
apt-get upgrade
reboot

Add the unofficial repo:

apt-get install apt-transport-https
# cat /etc/apt/sources.list.d/tvheadend.list 
#tvheadend unofficial repo
deb https://dl.bintray.com/djbenson/deb jessie unstable
apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 379CE192D401AB61

Install tvheadend:

apt-get update 
apt-get install tvheadend

And this what I get when execute the service:

# tvheadend -f -p /var/run/tvheadend.pid -u hts -g hts
Illegal instruction

I am doing something wrong?

I will really appreciate your help.

Kind regards.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Jonathan Thomson 7 months ago

Hi Josu

Is it the 4.0 or 4.1 build you installed?

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Jonathan Thomson 7 months ago

I'll give a full response soon but the short answer is "no" you didn't do anything wrong, I probably did.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Josu Lazkano 7 months ago

Thanks Jonathan,

I have unstable repository for jessie: 4.1-2141-g01c26fc.

If you need some help for testing just ask for it.

Thank for your help, best regards.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by big big 7 months ago

Thanks' for your new build.
I will try these asap.

Regards,

Olivier

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Jonathan Thomson 7 months ago

Sorry about the issues guys, I am trying (with everything else I have to do in the real world) to get the builds sorted. I am going to remove the last two builds from the repository so those with broken builds can remove the current build and re-install the previous build whilst I work out how to resolve the issue.

Ideally, the builds would be built on real RPi hardware but I can't spare the hardware to build for the various RPi hardware/software variations.

Can we do a straw poll of requirements here - please reply with the answer to the following:

1) Which Raspberry Pi are you running?
2) Which version of TVHeadend do you need (4.0 or 4.1)
3) Which version of Raspbian are you running (Wheezy or Jessie)

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Josu Lazkano 7 months ago

Jonathan, you don't need to sorry, your work is so appreciated.

My requirements:

1) Raspberry Pi Model B (Rev 2.0, 512Mb)
2) 4.1 (I need Automatic IPTV network)
3) Jessie Lite

I have 2 Raspberry Pi, so I could configure one of them with a fresh Raspbian installation and give you full access (SSH). Tell me if you need it.

Best regards.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by big big 7 months ago

Don't be sorry, thanks' for your hard work.

I need TVHE 4.1 (unstable) on Jessie, for a RPI2

Regards,

Olivier

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Jonathan Thomson 7 months ago

I've pushed a new build to Bintray - not convinced the issue is resolved but if one of you could try it out I'd appreciate it. If this doesn't work I'll need to dig out a real Pi and use that.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Josu Lazkano 7 months ago

Hello,

Same happens:

# tvheadend
Illegal instruction

I install with steps from https://tvheadend.org/boards/5/topics/21528?r=23548#message-23548

This is the version I installed: 4.1.2141-g01c26fc

I could configure a rpi with a fresh install.

Regards.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Jonathan Thomson 7 months ago

Hi

I've gotten to the bottom of the issue, the cross-compiler was not compiling with the correct arm version. I've fixed that now and pushed a new build (4.1-2331~gf2371cf) which I've tested on a Raspberry Pi B+ and a Raspberry Pi 3 - both installed and ran with no issues.

One thing to note is that building with ffmpeg_static enabled is broken at the moment (due to a bug in gcc) so these builds do not have ffmpeg_static enabled. This shouldn't be a problem as even the RPi 3 is too slow for reliable transcoding. If you have ffmpeg installed on your box then I think that it should make use of it but I couldn't swear on it.

I am in the process of testing a Jessie chroot to see if I can cross-compile with everything enabled under Jessie (which has the newer version of gcc which fixes the above bug) but it's not a priority. I've literally spent the last 24 hours doing nothing only get this build working so I'm done for a bit :)

Please test and provide feedback.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Josu Lazkano 7 months ago

Thanks!

I try it again but it install the same version:

# dpkg -l | grep tvheadend
ii  tvheadend                        4.1-2141~g01c26fc              armhf        Tvheadend

I have this repo:

# cat /etc/apt/sources.list.d/tvheadend.list 
#tvheadend unofficial repo
deb https://dl.bintray.com/djbenson/deb jessie unstable

I donwload and install manually:

# dpkg -i tvheadend_4.1-2331-gf2371cf_armhf.deb 
(Reading database ... 41106 files and directories currently installed.)
Preparing to unpack tvheadend_4.1-2331-gf2371cf_armhf.deb ...
Unpacking tvheadend (4.1-2331~gf2371cf) over (4.1-2141~g01c26fc) ...
Setting up tvheadend (4.1-2331~gf2371cf) ...
Processing triggers for systemd (215-17+deb8u5) ...

And it works! I can access to the web interface!

I think that is something wrong in the repo links. The build looks good.

Thanks for your great help.

Kind regards.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Jonathan Thomson 7 months ago

Hi Josu

First thing, thank you very much for standing up the Jessie install for me - I was locked away in my office getting this to work before I realised you'd emailed me so I just wanted to say "thanks" for doing that and for offering me access to your RPi - truth is, I have every Pi ever made, it's time I'm short on :)

With regards to the above, there are no jessie specific builds any more - I did a couple but it was taking too much time to maintain wheezy 4.0, wheezy 4.1, jessie 4.0 and jessie 4.1 so I just dropped the jessie branch and now only maintain the wheezy branch. If you switch "jessie" for "wheezy" in /etc/apt/sources.list then you'll get the latest build(s) - they are compatible with jessie despite being built on wheezy.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Josu Lazkano 7 months ago

Thank again Jonathan,

Could you explain how to compile it for Jessie? I will leave all the night compiling my little rpi.

Kind regards.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by big big 7 months ago

Thanks' a lot Jonathan!

I'll test your build soon.

Regards,

Olivier

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Jonathan Thomson 7 months ago

Updated the first post to remove redundant information and also include details of my new BuildBot script which will push new builds of TVHeadend (both 4.0 and 4.1) to Bintray within hours of the source code being published by the TVHeadend team to Github.

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Nicolas Rioja 6 months ago

Hi all,
First of all, Jonathan thanks a lot for your work to bring us the Tvheadend repo for RPi users...

I´ve installed tvheadend stable (4.0.9-13~g64fec81) from the repo but I would like to switch to the 4.1 unstable version to get the SAT>IP server feature.

I have the two lines in sources.list but even commenting the stable one if I write:

dpkg -l |grep tvheadend
ii tvheadend 4.0.9-13~g64fec81 armhf Tvheadend

Only get the stable version and if I write:

apt-get install tvheadend unstable
I get an error saying that It couldn´t find the package

Could you guide me how to do it?
Thanks a lot!

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Obv B 5 months ago

Jonathan Thomson wrote:

I have implemented a BuildBot script on the Pi that is building these files. The purpose of the BuildBot is to check out the new code, compile it into a redistributable Debian (.deb) archive and automatically publish it to Bintray. This is an ALPHA-like trial at the moment as I need to wait for a change to the 4.1 branch to check that it works end-to-end. The benefit of this is that new builds will be uploaded to Bintray within 24 hours of the code being added to Github - I'll review these timings later providing the script works as expected, with the aim of doing 4 build cycles per branch (4 stable and 4 unstable) per day - that will cut the 24 hour wait down to a maximum of 8 hours delay between Github and my Bintray repository.

First, thanks for making these packaged builds available - much appreciated.

It appears that the "BuildBot" isn't completing its task. The build that apt-get downloads is 4.1-2332~g38c9e89 whereas the the latest version is 4.1-2409~g4db3eec

[email protected]:~ $ sudo apt-get download tvheadend
Get:1 https://dl.bintray.com/djbenson/deb/ wheezy/unstable tvheadend armhf 4.1-2332~g38c9e89 [17.1 MB]
Fetched 17.1 MB in 8s (1,959 kB/s)

RE: [Unofficial] Raspberry Pi / armhf builds Banana PI M3 - Added by Hallo Bosse 5 months ago

Thanks, Thanks, Thanks,

I create an Image for the Banana PI M3 with ubuntu Mate, and this repository.
Who can put it on his Server?

RE: [Unofficial] Raspberry Pi / armhf builds - Added by Robert Mast 4 months ago

I tried these repositories, but all are missing the Transcode option, so I'll still have to build a long run on my RPi1.

I want to try the transcode option to see GStreamer working with TVHeadend. Someone suggested to transcode the audio-stream to 0101 to get gstreamer to work, as the assumed working gstreamer-builds exclusively seem to work with audio on 0101.

1 2 3 4 (26-50/87)