Tvheadend

knock, knock, knock...penny?'

also a "knock, knock, knock" from my side.

While waiting for it should we still use jessie or would xenial be a better choice?

17.04 zesty stretch / sid
16.10 yakkety stretch / sid
16.04 xenial stretch / sid
15.10 wily jessie / sid
15.04 vivid jessie / sid
14.10 utopic jessie / sid
14.04 trusty jessie / sid
13.10 saucy wheezy / sid
13.04 raring wheezy / sid
12.10 quantal wheezy / sid
12.04 precise wheezy / sid
11.10 oneiric wheezy / sid
11.04 natty squeeze / sid
10.10 maverick squeeze / sid
10.04 lucid squeeze / sid

I've already asked for it to be added as a target on Doozer, but unfortunately people are busy, so when it'll happen is unknown, I hope it's soon though :).

Mark Clarkstone wrote:

I've already asked for it to be added as a target on Doozer, but unfortunately people are busy, so when it'll happen is unknown, I hope it's soon though :).

As said, there are already build available via deb-multimedia that I use (x86/amd64/armhf).

sure there are much builds available on deb-multimedia, but who wants to add this repo to get a lot of packages always existing in stretch...?

i just want to get the pure TVH directly from here...

rgds mad

maddis from net wrote:

i just want to get the pure TVH directly from here...

ditto :-)

Oliver Doll wrote:

maddis from net wrote:

i just want to get the pure TVH directly from here...

ditto :-)

I'm currently upgrading to stretch on my tvh server. I'll look into supplying stretch builds on my repo.

Thx - but btw: I think there's another inconsistency in the guide for Debian https://bintray.com/tvheadend/deb (and other distros as well?):

It misses to mention he stable-4.2 versions:

Official Tvheadend debian packages, including support for all current Ubuntu and Debian distributions.

4 components are available:

• release - for the latest official release
• stable - for nightly build of latest release branch (will pick up fixes quicker than release)
• unstable - for nightly build of master branch (don't use on production systems)
• obsolete - historic 3.4 build to keep older users happy

BTW2: though I'm mostly happy with the 4.1-2332~g38c9e89 version which I get offered since some time now on my Cubietruck as "stable" I sometimes have the following glitches.

• running for a quite some days tvh something dies and I have to manually restart it
• if I forget to manually stop tvh before e.g. reboot the board it seems to tend loosing it's config partly and coming up with no MUXes defined

As I just found out now, would it be worth to switch to stable-4.2?

Oliver Doll wrote:

Thx - but btw: I think there's another inconsistency in the guide for Debian https://bintray.com/tvheadend/deb (and other distros as well?):

It misses to mention he stable-4.2 versions:

Official Tvheadend debian packages, including support for all current Ubuntu and Debian distributions.

4 components are available:

• release - for the latest official release
• stable - for nightly build of latest release branch (will pick up fixes quicker than release)
• unstable - for nightly build of master branch (don't use on production systems)
• obsolete - historic 3.4 build to keep older users happy

Yes, I'm aware that needs updating, unfortunately I don't have access so can't, always follow the AptRepository page.

BTW2: though I'm mostly happy with the 4.1-2332~g38c9e89 version which I get offered since some time now on my Cubietruck as "stable" I sometimes have the following glitches.

• running for a quite some days tvh something dies and I have to manually restart it
• if I forget to manually stop tvh before e.g. reboot the board it seems to tend loosing it's config partly and coming up with no MUXes defined

As I just found out now, would it be worth to switch to stable-4.2?

Wouldn't hurt to try, just backup your config & go back if you have issues.

knock, knock, knock...penny?

what about an actual stretch-repo....?

rgds mad

hi there,

the next two weeks are gone...

heyho, it's me again.

(taken from DL-page)
Please check the Supported Distributions / Platforms list below, if your distribution isn't listed there may be an older version available, new build targets will be added as soon as possible.

what amount of time is meant with "soon"?

rgds mad

maddis from net wrote:

heyho, it's me again.

(taken from DL-page)
Please check the Supported Distributions / Platforms list below, if your distribution isn't listed there may be an older version available, new build targets will be added as soon as possible.

what amount of time is meant with "soon"?

rgds mad

Unfortunately I cannot give an answer to that. As the doozer.io service is used to build the packages, it's up to andoma to add the targets. Please join #doozer.io & ask there.

Unfortunately the repo seems to have a screwed structure even inside the currently supported OS versions: I think it always has versions for 'Intel' based platforms, but arm* versions are missing very often.

For non Intel 32bit and AMD 64 bit ;)
you need cross compilation environment and Toolchain
in case where software will be compiled on PC and run on somePI.
Other way is to run full functional linux on somePI and compile from there

the next two weeks are gone...and nothing changed...

i wrote to andoma via github, but i got no answer until now.
what should i/we do next?

rgds mad

In "English":
----------------

Hi!

You also want to join these people who are looking for the people in the debian stretch repository to find you ...

With Slys!

(Sorry, you know English, so google does not use it.)

In Hungarian:
------------------

Sziasztok!

Én is csatlakozni szeretnék azok táborához, akik kérelmezik az illetékesektől a debian stretch repository létrehozását...

Köszönettel Slys!

( Bocsánat, a silány angol tudásom miatt, google fordítót használok. )

"Build it your self, leave problems behind" ;)
https://tvheadend.org/boards/4/topics/24116

if i wanted to compile everything, i would had choosen LFS! for sure i could compile TVH, but that is not the main-intention of a well working package-management. ;)
here we've got a superior build-system with doozer.io, so why we don't support actual distributions?

atm i'm using Debian 8, and everything's fine. but i want to upgrade to Debian 9 in the next time. is "use deb-multimedia" the only answer for this question?

is there nobody else, who could contact people like andoma or perexg?!

just my 2 cents...

rgds mad

+ my 2 cents

maddis from net wrote:

is there nobody else, who could contact people like andoma or perexg?!

rgds mad

IRC is often the best/quickest way to get help (#hts on irc.freenode.net).

i don't use IRC. would you, "sean acro", be so nice to contact these guys?

rgds mad

maddis from net wrote:

i don't use IRC. would you, "sean acro", be so nice to contact these guys?

rgds mad

I've already pointed andoma to this thread on IRC. perexg can't do much about missing build targets though. The good news is I'm working on publishing builds using travis-ci/docker, but that's 64 bit only :/.

thank you for this good news @Mark.

even if its "only 64bit" (which will match my wishes)...

rgds mad

maddis from net wrote:

thank you for this good news @Mark.

even if its "only 64bit" (which will match my wishes)...

rgds mad

I've now managed to get travis-ci/docker to build tvheadend for x64 targets artful, sid and stretch. You can find them here: https://bintray.com/mpmc/deb/tvheadend/

A few notes:

1) The git hash is slightly different due to how travis-ci works.

2) This is a mix of doozer.io/travis-ci builds. You can tell them apart by the git hashes [travis-ci ones are longer]. This isn't ideal & one of the main reasons why I won't be submitting the commit that builds these as a PR to the main repo. The travis-ci builds will be based on my own tvheadend fork travis branch. This is exactly the same as the main repo apart from a few commits that deal with building! I will keep this updated with master.

If you have any crashes with these & need to open a ticket on here, mention the fact that you're using my alt repo to avoid confusion.