I'm currently using the Raspberry Pi detailed here: https://tvheadend.org/projects/tvheadend/wiki/AptRepository However, it currently says that there are no updates to go from 3.4 to 3.4.27. I have issued apt-get update followed by apt-get upgrade with no joy.
This is partly because I forgot the rpi builds need to be manually submitted to the build system, and partly because it appears that our build env for rpi is once again broken. From what I can see raspbian keep changing things and our environment doesn't seem to cope.
I don't have time to investigate this right now I'm afraid, so if you desperately need the builds you'll need to do them yourself.
tvheadend 3.4 (on RPI) is plagued with that nasty "ATSC service name is left blank" bug that has plagued many users. I see that the bug was resolved a little while ago; but the fix never made it to the public. Is it possible to produce a RPI build sometime soon so that we can have a working backend?
Comments
Added by James Simpson over 11 years ago
Hi,
I'm currently using the Raspberry Pi detailed here: https://tvheadend.org/projects/tvheadend/wiki/AptRepository
However, it currently says that there are no updates to go from 3.4 to 3.4.27. I have issued apt-get update followed by apt-get upgrade with no joy.
Am I missing something?
Regards,
James
Added by Adam Sutton over 11 years ago
This is partly because I forgot the rpi builds need to be manually submitted to the build system, and partly because it appears that our build env for rpi is once again broken. From what I can see raspbian keep changing things and our environment doesn't seem to cope.
I don't have time to investigate this right now I'm afraid, so if you desperately need the builds you'll need to do them yourself.
Sorry
Adam
Added by James Simpson over 11 years ago
No problem Adam. Thanks for checking. I'm having no major issues any way, so I'll stay where I am for now.
Added by Chris Tremblay over 10 years ago
tvheadend 3.4 (on RPI) is plagued with that nasty "ATSC service name is left blank" bug that has plagued many users. I see that the bug was resolved a little while ago; but the fix never made it to the public. Is it possible to produce a RPI build sometime soon so that we can have a working backend?