Tvheadend

So which version of Debian or OMV is that? You didn't tell us.

OpenMediaVault 2.0.11 (Stone burner) based on Debian 7.8

Ok thanks for letting us know. Therefore Debian wheezy 7.8 does not work. SO to answer your question - yes you will need to compile it yourself for the time being.

And we still need to hear what happens on Debian jessie 8.0.

Dreamcat 4 wrote:

Ok thanks for letting us know. Therefore Debian wheezy 7.8 does not work. SO to answer your question - yes you will need to compile it yourself for the time being.

And we still need to hear what happens on Debian jessie 8.0.

[EDIT]

I look into libc6 on debian a bit more, and it's newer version on jessie:

https://packages.debian.org/jessie/libc6

Also: wheezy is now denoted as 'oldstable'. Wheras jessie is now marked as 'stable'. Unfortunately for OMV there you have to wait until they eventually upgrade their base to jessie. Which may take a long time as they are tracking behind debian.

FYI if you are not too invested in OMV, then maybe consider the option of switiching over to xpenology instead, which (not for tvheadend) may give other newer / better features than OMV. Website:

http://www.xpenology.nl/

• For jessie we still wait for someone to test on jessie. In case other issues may be the case (maybe not just libc6 blocker).

Ok. We have an indication that those trusty-built ubuntu packages may be working (more-or-less) on the Debian Jessie 8.0. Which is debian's 'current stable' at this time.

[20:45] < hans_s> dreamcat4: will try the ubuntu builds in debian
[20:46] < hans_s> although, it's just a vm I set up today, and I also don't have a dvb adapter here right now, so I can't test
everything
[20:46] < hans_s> my testing was just done with a ts file I used with the pipe:// input
[21:11] < hans_s> dreamcat4: first impression: I can install and start it
[21:11] < [-T-]> who is stbenz ?
[21:12] * hans_s = stbenz
[21:13] < hans_s> dreamcat4: although the deb recommends xmltv-utils, which has a LOT of dependencies, and debian seems to
automatically install recommended packages

In regards to the xmltv, debian have an out-of-date version 0.5.63 that might be fine for some people. Others it is too old now (the grabbers for some countries). They probably eventually update their xmltv to be 0.5.66+, just not yet it seems.

xmltv is only needed for better EPG data. Regular over-the-air 'OTA' epg schedule it's not needed.

I think this is good news.

Ok. Have updated the documentation about the Auto-builds, to explain better which platforms / distros these 'ubuntu' pkgs are known to work on. It is explained here:

https://github.com/tvheadend/tvheadend-build

Have also asked someone with wiki write access (not any person specific, just generally on IRC), to please update the AptRepository langing page / downloads page, to include the necessary information. So people can know which distros it should work on.

echo "deb https://dl.bintray.com/dreamcat4/ubuntu master main" | sudo tee -a /etc/apt/sources.list

nor

echo "deb https://dl.bintray.com/dreamcat4/ubuntu unstable main" | sudo tee -a /etc/apt/sources.list

works for my ubuntu trusty-server, it can`t find any tvh packages

http://pastebin.com/kyZSkPDx

no errors ... simply no packages to update/install

this is because is fake repo
fast example
http://dl.bintray.com/dreamcat4/ubuntu/pool/main/t/tvheadend/ or http://dl.bintray.com/tvheadend/ubuntu/pool/main/t/tvheadend/
is where all debs must be
but don't be so sure
if some one try

wget http://dl.bintray.com/dreamcat4/ubuntu/pool/main/t/tvheadend/#tvheadend_4.1-182~gfb6b56c~trusty_amd64.deb

http://d29vzk4ow07wi7.cloudfront.net/b7671238535f9d33723ae5299f0dee246ad70ac6?response-content-disposition=attachment%3Bfilename%3D%22tvheadend_4.1-182%7Egfb6b56c%7Etrusty_amd64.deb%22&Policy=eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vZDI5dnprNG93MDd3aTcuY2xvdWRmcm9udC5uZXQvYjc2NzEyMzg1MzVmOWQzMzcyM2FlNTI5OWYwZGVlMjQ2YWQ3MGFjNj9yZXNwb25zZS1jb250ZW50LWRpc3Bvc2l0aW9uPWF0dGFjaG1lbnQlM0JmaWxlbmFtZSUzRCUyMnR2aGVhZGVuZF80LjEtMTgyJTdFZ2ZiNmI1NmMlN0V0cnVzdHlfYW1kNjQuZGViJTIyIiwiQ29uZGl0aW9uIjp7IkRhdGVMZXNzVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxNDMzOTc2NDAyfSwiSXBBZGRyZXNzIjp7IkFXUzpTb3VyY2VJcCI6IjAuMC4wLjAvMCJ9fX1dfQ__&Signature=lVrAVd5ScsnRa8TrSxQiHBbCCsTYuxFW71PL1KbSbn6BS0hTVxzRcwfe-96cCv2Bgqe7Y13InjU0CgUL~A2zVzr98faKZj7~lKs93K5T4UtPXkjP~ONzx8sI8-lxdq~7WMMRkxAJujkWHuaZSa~NdQynP765ANGsbwP0par8ptuaF2QJI29MuhRpm0JDBmExWljaIYR~8Pq~m637a1DhDzf0np2Dp5HHUyaNrCOjghL-UxouvOQLqYefMOKWBJZWUzMhsTlnfjSSo0uID-Ls3JyQk-clE6oVsViMpL4ZYx~T55AazwX8G-y98nFA76QU15yCRUC32OXtRZFVjxPd2A__&Key-Pair-Id=APKAIFKFWOMXM2UMTSFA

it have not a regular structure
aka

http://dl.bintray.com/tvheadend/ubuntu/(master/stable/testing/unstable/)pool/main/t/tvheadend/

basicly copy debs to old repo with is good organized

C vH wrote:

echo "deb https://dl.bintray.com/dreamcat4/ubuntu master main" | sudo tee -a /etc/apt/sources.list

nor

echo "deb https://dl.bintray.com/dreamcat4/ubuntu unstable main" | sudo tee -a /etc/apt/sources.list

works for my ubuntu trusty-server, it can`t find any tvh packages

http://pastebin.com/kyZSkPDx

no errors ... simply no packages to update/install

Sorry I am not certain your problem. The instructions do not say that you must 'sudo apt-get update' afterwards. But that is an implied common knowledge everybody knows about. I think you didn't show there (in paste) also the commands you ran to get those terminal output. We would prefer to see the full text. Not sure why you specify dreamcat4 username, when the 'tvheadend' username is meant to be the official one. It should not really matter though.

Just an example, these commands works for me:

echo "deb https://dl.bintray.com/tvheadend/ubuntu master main" | sudo tee -a /etc/apt/sources.list
sudo apt-get update
apt search tvheadend
sudo apt-get install tvheadend

You can also see here a recent rebuild (4 hours ago) on docker hub, how I install tvheadend into a 14.04.2 trusty host:

https://registry.hub.docker.com/u/dreamcat4/tvheadend/builds_history/217676/

Just click on a 'build id' to open up a the build log. And click 'Dockerfile' tab to see the apt-get commands we ran. No problems with the installation.

saen acro - your quoted wget command is not correct:

wget http://dl.bintray.com/dreamcat4/ubuntu/pool/main/t/tvheadend/tvheadend_4.1-182~gfb6b56c~trusty_amd64.deb

Corrected url ^^ works fine. No '#' in the filename.

In 10+ years Debian I think I have heard of apt-get update ;)
I have quick install it at a fresh vm and there it find the packages without any problem (same source.list).
Is there a possible problem if I switch from the old repo to the new one ? (old repo removed)
Did I need to purge remove tvh ?

C vH wrote:

Is there a possible problem if I switch from the old repo to the new one ? (old repo removed)
Did I need to purge remove tvh ?

It's possible if the old repo has a greater version number than the new one. However then apt search should show you that. More infos here: https://tvheadend.org/boards/5/topics/16656

The most infos I can get from your pastie that you commented '# aptitude update'. Not sure that 'aptitude' is the command you actually ran. But it is not is quite the same thing as 'apt-get update' afaik I don't know the details but it's not generally recommended anymore by ubuntu people so don't use it. We only test with 'apt-get update' cmd.

I think I found the problem, I got 4.1.18~gec3ba93~ utopic installed (from old repo) and the new repo reports 4.1-182~gfb6b56c~ trusty (no clue why ~utopic instead of ~trusty).
http://pastebin.com/T3LU2fep

if someone has the same problem

# wget https://dl.bintray.com/tvheadend/ubuntu/pool/main/t/tvheadend/tvheadend_4.1-182~gfb6b56c~trusty_amd64.deb
# dpkg -i tvheadend_4.1-182~gfb6b56c~trusty_amd64.deb

afterwards the updates are working again

Ok. Thanks for mentioning that!

The build distro part of the version name is what the autobuild.sh build script puts in the version string automatically. We updated the name to trusty because we want to be open and transparent about which ubuntu version we are building on now. But those part of the build scripts were not changed in any way. And it should matter or be factor in the way that the apt tools choose the newest version of tvheadend.

You seem to have got caught out in a short time window when perexg was sorting things out. He changed the separator (of the +commit #) from a dot '.' --> to a dash '-'. It was to better demark going on 3-point release numbers.

So the version '4.1.18-something' is interpreted by apt tools as being newer than '4.1-something-else'. In these cases you are unlucky. There were only a few commits strange until perexg settled upon a new version numbering scheme.

Solution seems to be uninstall --> 'apt-get remove'. Then re-install 'apt-get install'. Just like you were asking about earlier.

Dreamcat 4 this fake repo is some compromise
make some script to put correct name an location to old repo
there is normative how to make repo
but this is out of normative
not correct naming and correct path

4.1.18 is the latest version at the old repo, so everyone who wants to update from old to the new repo got the same problem !

4.1.$version latest at old , latest at new 4.1-%version

Atm we have no clean upgrade path! Is there a way to tell the dpkg that 4.1. == 4.1- ? Or something similar, it should be a solution out there if the name of a program changes.

saen acro wrote:

Dreamcat 4 this fake repo is some compromise

I disagree entirely. Everything is a compromise. I think overall we come away with many major + positives using bintray.com's online hosting service. That taken all into account outweighs the cost of hosting and maintaining our own private debian repo.

there is normative how to make repo
but this is out of normative

Ok. From a purely technical standpoint we are overall better off using the distro field for specifying the branch. Because it saves us in other ways. You have yet to prove to anybody there is a real error or technical issue caused by doing so.

Or to put it another way: If it's so terrible / dangerous / problematic to put the 'stable'... in the distro field, then how come that is also the way Google does it for their official Chrome web browser, which is being installed & used by millions of people across the world? Surely if there were some legitimate issue they also would be affected too in same fashion / same ways? Do you think the people who work at google are less knowledgable than you at choosing these things?

not correct naming and correct path

It is correct. We have listened to your concerns. When they were legitimate ones we have gone back, checked again. Places we had problems, like the metadata signing, then that has been fixed. Thank you.

"Just copy into the *apt.tvheadend.org repo"...

OK that repo is under the control of Adam Sutton. Who is hardly around anymore. He has written those scripts in python. Nobody else really knows how it works. So asking me to do something I am not actually capable of isn't going to produce the desired result. Now think for a minute: how is that better than an MIT licensed open source (fully documented) build guide, and using public bintray rest API + the help of the bintray support team? Who (bintray.com) are also paying for the money to host our project's open source .deb files at no cost whatsoever to tvheadend project. Which ways is best overall, everything considered?

Another point about it:

Copying already signed .debs from bin tray repo into apt.tvheadend.org repo. That is different URL, so we might expect it is probably going to cause some similar metadata signing error (as we saw previously). So perhaps from a technical standpoint it is NOT so convenient. It's precisely the sort of problems that bintray.com are supposed to solve for us with their special knowledge of release management issues. When managing such things in our own apt repo, we don't get bin tray guys to fix such APT repo issue. = maintenance time of us is wasted, which can be better used for making ARM builds for RPI or RPM builds for Centos / Fedora. Which one of those things is best use of resources?