New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add TvHeadend-Testing with TvHeadend version 3.9.512 #931

Closed
wants to merge 2 commits into
base: develop
from

Conversation

Projects
None yet
@jdierkse

jdierkse commented Apr 15, 2014

This experimental package can be used to test the latest version of TvHeadend.
It can be installed alongside the regular TvHeadend install.

@olehumborstad

This comment has been minimized.

Show comment
Hide comment
@olehumborstad

olehumborstad Apr 20, 2014

Ok, first off, I absolutely love this 👍
Kudos for making the effort of creating testing packages of tvheadend for every know platform on Synology :D
I ran this on my Synology DS1812+ (cedarview), with just one complication.
My tuner (sundtek media tv pro 3), doesn't show up under:
"Configurations" - "DVB Inputs" - "TV-adapters", as it does when I tried the same thing on ubuntu. Any clue?

olehumborstad commented Apr 20, 2014

Ok, first off, I absolutely love this 👍
Kudos for making the effort of creating testing packages of tvheadend for every know platform on Synology :D
I ran this on my Synology DS1812+ (cedarview), with just one complication.
My tuner (sundtek media tv pro 3), doesn't show up under:
"Configurations" - "DVB Inputs" - "TV-adapters", as it does when I tried the same thing on ubuntu. Any clue?

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse Apr 21, 2014

@whitehum Hmm, not sure...
Have you tried turning on debug logging and checking the logfiles?
On my own repo site (http://syno.dierkse.nl) I've uploaded packages for 542, maybe you'll have more luck with that version?

jdierkse commented Apr 21, 2014

@whitehum Hmm, not sure...
Have you tried turning on debug logging and checking the logfiles?
On my own repo site (http://syno.dierkse.nl) I've uploaded packages for 542, maybe you'll have more luck with that version?

@olehumborstad

This comment has been minimized.

Show comment
Hide comment
@olehumborstad

olehumborstad Apr 22, 2014

Sorry, I'm actually trying this with version 542.

Also there seems to be a problem with opening the help documents in debugging?

2014-04-22 20:16:30.147 webui: failed to open docs/html/config_tvhlog.html
2014-04-22 20:16:30.147 HTTP: 10.0.0.11: /docs/config_tvhlog.html -- 500

I have made a directory for the, "Debug Log Path:"
/usr/local/tvheadend-testing/var/debug/

But nothing shows up there and when i start/stop tvheadend the path is erased...?
(Everything else stores just fine...)

olehumborstad commented Apr 22, 2014

Sorry, I'm actually trying this with version 542.

Also there seems to be a problem with opening the help documents in debugging?

2014-04-22 20:16:30.147 webui: failed to open docs/html/config_tvhlog.html
2014-04-22 20:16:30.147 HTTP: 10.0.0.11: /docs/config_tvhlog.html -- 500

I have made a directory for the, "Debug Log Path:"
/usr/local/tvheadend-testing/var/debug/

But nothing shows up there and when i start/stop tvheadend the path is erased...?
(Everything else stores just fine...)

@olehumborstad

This comment has been minimized.

Show comment
Hide comment
@olehumborstad

olehumborstad Apr 23, 2014

So after sundtek support dropped by on a remote session ssh, they fixed the "problem" immediately. Everything works perfectly now. (Except the debug logging, but I dont need that now.)

They also asked me to :
can you try to get in touch with the synology tvheadend packager and tell him he should add:
if [ -e /volume1/@appstore/sundtek/opt/lib/libmediaclient.so ]; then
export LD_PRELOAD=/volume1/@appstore/sundtek/opt/lib/libmediaclient.so
fi
at the beginning of the tvheadend start-stop-script?

that would mean if our driver is installed this file will be loaded, if not .. well then the compatibility interface to our driver will not be loaded
win-win situation for everyone who needs it

olehumborstad commented Apr 23, 2014

So after sundtek support dropped by on a remote session ssh, they fixed the "problem" immediately. Everything works perfectly now. (Except the debug logging, but I dont need that now.)

They also asked me to :
can you try to get in touch with the synology tvheadend packager and tell him he should add:
if [ -e /volume1/@appstore/sundtek/opt/lib/libmediaclient.so ]; then
export LD_PRELOAD=/volume1/@appstore/sundtek/opt/lib/libmediaclient.so
fi
at the beginning of the tvheadend start-stop-script?

that would mean if our driver is installed this file will be loaded, if not .. well then the compatibility interface to our driver will not be loaded
win-win situation for everyone who needs it

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse Apr 23, 2014

@whitehum Great! I'll add the requested code.

jdierkse commented Apr 23, 2014

@whitehum Great! I'll add the requested code.

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse Apr 23, 2014

However I'm not a big fan of hardcoding "volume1" in the TvHeadend startscript... (users can choose to install packages on other volumes as well) I'll think of a way to make it nice.
For now I've created a new version (569) with this fix in on http://syno.dierkse.nl
Can you test whether it works for you?

jdierkse commented Apr 23, 2014

However I'm not a big fan of hardcoding "volume1" in the TvHeadend startscript... (users can choose to install packages on other volumes as well) I'll think of a way to make it nice.
For now I've created a new version (569) with this fix in on http://syno.dierkse.nl
Can you test whether it works for you?

@bru7us

This comment has been minimized.

Show comment
Hide comment
@bru7us

bru7us Apr 23, 2014

Contributor

/var/packages/[package]/target/

so: /var/package/sundtek/target/opt/lib/libmediaclient.so

Contributor

bru7us commented Apr 23, 2014

/var/packages/[package]/target/

so: /var/package/sundtek/target/opt/lib/libmediaclient.so

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse Apr 23, 2014

@bru7us ah, indeed! Thank you!

jdierkse commented Apr 23, 2014

@bru7us ah, indeed! Thank you!

@olehumborstad

This comment has been minimized.

Show comment
Hide comment
@olehumborstad

olehumborstad Apr 24, 2014

@jdierkse I just updated to 569-1?
Everything still works perfectly :)

olehumborstad commented Apr 24, 2014

@jdierkse I just updated to 569-1?
Everything still works perfectly :)

@olehumborstad

This comment has been minimized.

Show comment
Hide comment
@olehumborstad

olehumborstad Apr 28, 2014

This might not have anything to do with this package at all, and everything about my little understanding of ffmpeg, but I'm trying to get a smaller file from the recordings automatically.
Using the tvheadend's built-in "post-processor command" found under:
"Configuration" - "Recording" - "Digital Video Recorder":

But whatever I try to put in there only yields a 3kb file.. ?
My line:
/usr/syno/bin/ffmpeg -i %f -sn -vcodec libx264 -acodec copy "/volume1/Downloads/Tvheadend/%b"

Any suggestion? Running the exact same code (replacing %f and %b with the exact paths) in ssh works perfectly, that's why I thought I ought to check in here instead off some random forum about tvheadend and post processing.

olehumborstad commented Apr 28, 2014

This might not have anything to do with this package at all, and everything about my little understanding of ffmpeg, but I'm trying to get a smaller file from the recordings automatically.
Using the tvheadend's built-in "post-processor command" found under:
"Configuration" - "Recording" - "Digital Video Recorder":

But whatever I try to put in there only yields a 3kb file.. ?
My line:
/usr/syno/bin/ffmpeg -i %f -sn -vcodec libx264 -acodec copy "/volume1/Downloads/Tvheadend/%b"

Any suggestion? Running the exact same code (replacing %f and %b with the exact paths) in ssh works perfectly, that's why I thought I ought to check in here instead off some random forum about tvheadend and post processing.

@Dr-Bean Dr-Bean assigned piwi82 and unassigned piwi82 Apr 30, 2014

@MZman

This comment has been minimized.

Show comment
Hide comment
@MZman

MZman May 10, 2014

@jdierkse
in the new release 570-3 the new sat>ip function dont work on the ds213+
can u help me please

MZman commented May 10, 2014

@jdierkse
in the new release 570-3 the new sat>ip function dont work on the ds213+
can u help me please

@olehumborstad

This comment has been minimized.

Show comment
Hide comment
@olehumborstad

olehumborstad May 12, 2014

Also, after using this for some time now every other day I just receive a notification on xbmc:
"no input is detected". Where i have to restart my Synology in order to watch tv again, and that takes about 5 minutes. After googling i stumbled upon this (https://tvheadend.org/issues/1708), but with no other solution then a restart.
(HTS Tvheadend 3.9.570)

olehumborstad commented May 12, 2014

Also, after using this for some time now every other day I just receive a notification on xbmc:
"no input is detected". Where i have to restart my Synology in order to watch tv again, and that takes about 5 minutes. After googling i stumbled upon this (https://tvheadend.org/issues/1708), but with no other solution then a restart.
(HTS Tvheadend 3.9.570)

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse May 12, 2014

@MZman, There's still a lot of development going on in the SAT>IP area, and I've had problems building the versions beyond 3.9.570. I'll try to build a newer version this week.

jdierkse commented May 12, 2014

@MZman, There's still a lot of development going on in the SAT>IP area, and I've had problems building the versions beyond 3.9.570. I'll try to build a newer version this week.

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse May 12, 2014

@whitehum, The ffmpeg version packed with synology is seriously botched. I have to build ffmpeg for transcoding, and I can incorporate it in the tvheadend package. I will try to do this. It should work a bit better then, I guess.
When I get "No input detected" it means I have to restart my HDHomeRun driver. I'm not sure what the cause is, because it doesn't happen very often.

jdierkse commented May 12, 2014

@whitehum, The ffmpeg version packed with synology is seriously botched. I have to build ffmpeg for transcoding, and I can incorporate it in the tvheadend package. I will try to do this. It should work a bit better then, I guess.
When I get "No input detected" it means I have to restart my HDHomeRun driver. I'm not sure what the cause is, because it doesn't happen very often.

@olehumborstad

This comment has been minimized.

Show comment
Hide comment
@olehumborstad

olehumborstad May 12, 2014

I just changed coax cables now and that might've been the issue with no input, i'll get back to you on that one later if the problem returns. Otherwise if you could get the ffmpeg to work everything would be just perfect 😄 thanks again!

olehumborstad commented May 12, 2014

I just changed coax cables now and that might've been the issue with no input, i'll get back to you on that one later if the problem returns. Otherwise if you could get the ffmpeg to work everything would be just perfect 😄 thanks again!

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse May 14, 2014

@whitehum, I've uploaded the new packages to http://syno.dierkse.nl
The new packages now include the ffmpeg binaries

jdierkse commented May 14, 2014

@whitehum, I've uploaded the new packages to http://syno.dierkse.nl
The new packages now include the ffmpeg binaries

@olehumborstad

This comment has been minimized.

Show comment
Hide comment
@olehumborstad

olehumborstad May 14, 2014

Just updated now, having some issues with the tuners not re-appearing in tvheadend. Tried stopping the sundtek driver and tvheadend, still nothing. Restarting now.

The TV adapters are still not showing after a reboot.

olehumborstad commented May 14, 2014

Just updated now, having some issues with the tuners not re-appearing in tvheadend. Tried stopping the sundtek driver and tvheadend, still nothing. Restarting now.

The TV adapters are still not showing after a reboot.

@olehumborstad

This comment has been minimized.

Show comment
Hide comment
@olehumborstad

olehumborstad commented May 14, 2014

image

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse May 14, 2014

@whitehum, Strange, the only thing I've changed is that the package now includes some extra binaries. Can you check TvHeadend logging, /var/log/messages and dmesg for errors regarding your adapters?

jdierkse commented May 14, 2014

@whitehum, Strange, the only thing I've changed is that the package now includes some extra binaries. Can you check TvHeadend logging, /var/log/messages and dmesg for errors regarding your adapters?

@olehumborstad

This comment has been minimized.

Show comment
Hide comment
@olehumborstad

olehumborstad May 14, 2014

The path is wrong.

this is correct:

if [ -e /var/packages/sundtek/target/opt/lib/libmediaclient.so ]; then
export LD_PRELOAD=/var/packages/sundtek/target/opt/lib/libmediaclient.so
fi

following is wrong:

if [ -e /usr/local/sundtek/opt/lib/libmediaclient.so ]; then
export LD_PRELOAD=/usr/local/sundtek/opt/lib/libmediaclient.so
fi

After that's changed and tvheadend is restart'ed, Everything is fine. Looking forward to test the recording later :) Thanks!

olehumborstad commented May 14, 2014

The path is wrong.

this is correct:

if [ -e /var/packages/sundtek/target/opt/lib/libmediaclient.so ]; then
export LD_PRELOAD=/var/packages/sundtek/target/opt/lib/libmediaclient.so
fi

following is wrong:

if [ -e /usr/local/sundtek/opt/lib/libmediaclient.so ]; then
export LD_PRELOAD=/usr/local/sundtek/opt/lib/libmediaclient.so
fi

After that's changed and tvheadend is restart'ed, Everything is fine. Looking forward to test the recording later :) Thanks!

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse May 14, 2014

@whitehum, Whoops! Sorry for that!
I'll fix it in the next version of the packages. I'll try to build them today.

jdierkse commented May 14, 2014

@whitehum, Whoops! Sorry for that!
I'll fix it in the next version of the packages. I'll try to build them today.

@olehumborstad

This comment has been minimized.

Show comment
Hide comment
@olehumborstad

olehumborstad May 14, 2014

No sweat, cant wait to test this out 👍

olehumborstad commented May 14, 2014

No sweat, cant wait to test this out 👍

@bru7us

This comment has been minimized.

Show comment
Hide comment
@bru7us

bru7us May 14, 2014

Contributor

Actually both of those paths should be fine, most spksrc packages create a symlink on install in /usr/local/[package], so /usr/local/[package] == /var/packages/[package]/target.

@jdierkse, is that symlink missing for your packages?

Contributor

bru7us commented May 14, 2014

Actually both of those paths should be fine, most spksrc packages create a symlink on install in /usr/local/[package], so /usr/local/[package] == /var/packages/[package]/target.

@jdierkse, is that symlink missing for your packages?

@sundtek

This comment has been minimized.

Show comment
Hide comment
@sundtek

sundtek May 14, 2014

bru7us,
we fixed this in our latest Driver Package for Synology, we now also link to /usr/local/[package]
No need to change anything in your tvheadend package anymore.

thanks,
Markus

sundtek commented May 14, 2014

bru7us,
we fixed this in our latest Driver Package for Synology, we now also link to /usr/local/[package]
No need to change anything in your tvheadend package anymore.

thanks,
Markus

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost commented May 14, 2014

i have a problem with HDHomerun....
http://fotoo.pl/show.php?img=798103_hdhomerun.jpg.html

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse May 15, 2014

@sundtek, Thank's for mentioning this. I will keep my package as-is.

jdierkse commented May 15, 2014

@sundtek, Thank's for mentioning this. I will keep my package as-is.

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse May 15, 2014

@PiterEL, Unfortunately I don't speak Polish. What does the error message say?

jdierkse commented May 15, 2014

@PiterEL, Unfortunately I don't speak Polish. What does the error message say?

@Smiggel

This comment has been minimized.

Show comment
Hide comment
@Smiggel

Smiggel Jun 11, 2015

You have to setup your television provider and let it scan for services. Then you can map the channels.

Smiggel commented Jun 11, 2015

You have to setup your television provider and let it scan for services. Then you can map the channels.

@Smiggel

This comment has been minimized.

Show comment
Hide comment
@Smiggel

Smiggel Jun 12, 2015

@freddysmith1 dus you setup your tv provider in tv headend?

Smiggel commented Jun 12, 2015

@freddysmith1 dus you setup your tv provider in tv headend?

@Smiggel

This comment has been minimized.

Show comment
Hide comment
@Smiggel

Smiggel Jun 12, 2015

@freddysmith1 Good to hear. Good luck.

Smiggel commented Jun 12, 2015

@freddysmith1 Good to hear. Good luck.

@MZman

This comment has been minimized.

Show comment
Hide comment
@MZman

MZman Jun 26, 2015

@jdierkse Hi i have problem with your new package, i can not run it, so i must roll back to the old version

MZman commented Jun 26, 2015

@jdierkse Hi i have problem with your new package, i can not run it, so i must roll back to the old version

@MZman

This comment has been minimized.

Show comment
Hide comment
@MZman

MZman Jun 26, 2015

@freddysmith1 i can install it but if i want to run in the package store, i get an error it stops

MZman commented Jun 26, 2015

@freddysmith1 i can install it but if i want to run in the package store, i get an error it stops

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse Jun 26, 2015

@MZman can you please post the error that's being reported in the tvheadend.log file?

jdierkse commented Jun 26, 2015

@MZman can you please post the error that's being reported in the tvheadend.log file?

@MZman

This comment has been minimized.

Show comment
Hide comment
@MZman

MZman Jun 26, 2015

@jdierkse i have test it again but no log file

MZman commented Jun 26, 2015

@jdierkse i have test it again but no log file

@Smiggel

This comment has been minimized.

Show comment
Hide comment
@Smiggel

Smiggel Jun 26, 2015

Same issue here. I did not see the posts here. I just updated and now I can not start the package anymore. Log is empty.

Version 4.1.245 was working.

Strange thing is, that when I look in the config of TVH it says version 4.1.245 instead of .304. Seems like the update did not fully work?

Smiggel commented Jun 26, 2015

Same issue here. I did not see the posts here. I just updated and now I can not start the package anymore. Log is empty.

Version 4.1.245 was working.

Strange thing is, that when I look in the config of TVH it says version 4.1.245 instead of .304. Seems like the update did not fully work?

@MZman

This comment has been minimized.

Show comment
Hide comment
@MZman

MZman Jun 26, 2015

Change the info file in /var/packages/tvheadend-testing/ give a lower version number and install the the version

MZman commented Jun 26, 2015

Change the info file in /var/packages/tvheadend-testing/ give a lower version number and install the the version

@m4tt075

This comment has been minimized.

Show comment
Hide comment
@m4tt075

m4tt075 Jun 26, 2015

Contributor

Yep. Seems 4.1.304 wasn't stable when run as a service. See: #hts log
Should be fixed in current master, i.e. from 4.1.305 on. Better to wait for newer builds.

Contributor

m4tt075 commented Jun 26, 2015

Yep. Seems 4.1.304 wasn't stable when run as a service. See: #hts log
Should be fixed in current master, i.e. from 4.1.305 on. Better to wait for newer builds.

@Smiggel

This comment has been minimized.

Show comment
Hide comment
@Smiggel

Smiggel Jun 26, 2015

@MZman Where do i find this file exactly? I don't see it in the location you pointed out to.

Smiggel commented Jun 26, 2015

@MZman Where do i find this file exactly? I don't see it in the location you pointed out to.

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse Jun 26, 2015

Building 4.1.309 ATM.

jdierkse commented Jun 26, 2015

Building 4.1.309 ATM.

@MZman

This comment has been minimized.

Show comment
Hide comment
@MZman

MZman Jun 26, 2015

@Smiggel Go to /var/packages/tvheadend-testing/INFO with vi
And change
version="4.1.245-1"

MZman commented Jun 26, 2015

@Smiggel Go to /var/packages/tvheadend-testing/INFO with vi
And change
version="4.1.245-1"

@m4tt075

This comment has been minimized.

Show comment
Hide comment
@m4tt075

m4tt075 Jun 26, 2015

Contributor

@jdierkse
May I ask whether you have any plans to cross-compile the 4.0.x "beta" versions to make them more accessible to Synology users? I'm asking because the 4.0.x versions are supposed to become the new "stable", which would then replace the old 3.4 in the official SynoCommunity repo I suppose.
Right now the 4.0.x betas and 4.1.x alphas are still relatively close, so it is probably not so much of an issue, but as 4.1 and 4.0 are diverging it might be good for the TVH development team (perexg essentially) to have some "beta" testers too.

I know this might be additional hassle for you but wanted to ask. Grateful for what you are doing already! Either way...

Contributor

m4tt075 commented Jun 26, 2015

@jdierkse
May I ask whether you have any plans to cross-compile the 4.0.x "beta" versions to make them more accessible to Synology users? I'm asking because the 4.0.x versions are supposed to become the new "stable", which would then replace the old 3.4 in the official SynoCommunity repo I suppose.
Right now the 4.0.x betas and 4.1.x alphas are still relatively close, so it is probably not so much of an issue, but as 4.1 and 4.0 are diverging it might be good for the TVH development team (perexg essentially) to have some "beta" testers too.

I know this might be additional hassle for you but wanted to ask. Grateful for what you are doing already! Either way...

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse Jun 26, 2015

@m4tt075 That's a good point, I'll look into this this weekend. I might have to make two separate packages though to offer a choice between 4.0 and 4.1.

jdierkse commented Jun 26, 2015

@m4tt075 That's a good point, I'll look into this this weekend. I might have to make two separate packages though to offer a choice between 4.0 and 4.1.

@m4tt075

This comment has been minimized.

Show comment
Hide comment
@m4tt075

m4tt075 Jun 26, 2015

Contributor

@jdierkse That would be absolutely brilliant! We could run testing and betas in parallel, having fun AND keeping the wifes happy... :-)

Contributor

m4tt075 commented Jun 26, 2015

@jdierkse That would be absolutely brilliant! We could run testing and betas in parallel, having fun AND keeping the wifes happy... :-)

@Smiggel

This comment has been minimized.

Show comment
Hide comment
@Smiggel

Smiggel Jun 26, 2015

@MZman Thanks for the tip! It worked. I was able to install the latest previous version that was working ok, except for the EPG.

Smiggel commented Jun 26, 2015

@MZman Thanks for the tip! It worked. I was able to install the latest previous version that was working ok, except for the EPG.

@Dr-Bean

This comment has been minimized.

Show comment
Hide comment
@Dr-Bean

Dr-Bean Jun 26, 2015

Member

@jdierkse Can you open a new PR to update the current package (and possibly add a -testing package, seeing where the discussion above is going) at some point?
This PR was closed automatically because of the move to the master branch, but we probably don't want to see that continuing in perpetuity ;)

Member

Dr-Bean commented Jun 26, 2015

@jdierkse Can you open a new PR to update the current package (and possibly add a -testing package, seeing where the discussion above is going) at some point?
This PR was closed automatically because of the move to the master branch, but we probably don't want to see that continuing in perpetuity ;)

@Smiggel

This comment has been minimized.

Show comment
Hide comment
@Smiggel

Smiggel Jun 27, 2015

4.1.309 can be started again. That version works.

Smiggel commented Jun 27, 2015

4.1.309 can be started again. That version works.

@Vlaves

This comment has been minimized.

Show comment
Hide comment
@Vlaves

Vlaves Jun 28, 2015

@jdierkse: Sometimes when I update the Package it is not able to login in again. Then I need to reinstall. This only happens if I add at the Access Control an entry with "*" which could be used to also authenticate to tvheadend without username and password. Is it possible while doing an update to save the "authentication" and "password" folders and to restore them, after the update? I don't know if this could help. Thanks for ur support here :)

Vlaves commented Jun 28, 2015

@jdierkse: Sometimes when I update the Package it is not able to login in again. Then I need to reinstall. This only happens if I add at the Access Control an entry with "*" which could be used to also authenticate to tvheadend without username and password. Is it possible while doing an update to save the "authentication" and "password" folders and to restore them, after the update? I don't know if this could help. Thanks for ur support here :)

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse Jul 3, 2015

@m4tt075 I've added the TVHeadend-4.0 package to my repo.
This is built from the 4.0 branch, and is less bleeding-edge than the -testing package.
I have not tested this package in any way, but I expect it to work just fine.

jdierkse commented Jul 3, 2015

@m4tt075 I've added the TVHeadend-4.0 package to my repo.
This is built from the 4.0 branch, and is less bleeding-edge than the -testing package.
I have not tested this package in any way, but I expect it to work just fine.

@mbisanz

This comment has been minimized.

Show comment
Hide comment
@mbisanz

mbisanz Jul 3, 2015

@freddysmith1 had the same issue with 4.1.322, trying the 4.0 branch now. Thanks,@jdierkse, for your effort.

mbisanz commented Jul 3, 2015

@freddysmith1 had the same issue with 4.1.322, trying the 4.0 branch now. Thanks,@jdierkse, for your effort.

@m4tt075

This comment has been minimized.

Show comment
Hide comment
@m4tt075

m4tt075 Jul 3, 2015

Contributor

@jdierkse Thanks so much! Will test soon...
There might be an issue with the tagging / versioning though. Looks different in the 4.0.x and 4.1.x branches. See here. Am not sure whether your 4.0.1 spk corresponds to the actual 4.0.1 or the (most recent) 4.0.5 beta.

Contributor

m4tt075 commented Jul 3, 2015

@jdierkse Thanks so much! Will test soon...
There might be an issue with the tagging / versioning though. Looks different in the 4.0.x and 4.1.x branches. See here. Am not sure whether your 4.0.1 spk corresponds to the actual 4.0.1 or the (most recent) 4.0.5 beta.

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse Jul 6, 2015

@m4tt075, It's actually 4.0.5 plus some extra changes, sorry about that, forgot to update the version number.
@freddysmith1, It looks like a permissions issue, can you check that the tvheadend-4.0 user exists, and owns the /var/packages/tvheadend-4.0/target location and everything in it?

jdierkse commented Jul 6, 2015

@m4tt075, It's actually 4.0.5 plus some extra changes, sorry about that, forgot to update the version number.
@freddysmith1, It looks like a permissions issue, can you check that the tvheadend-4.0 user exists, and owns the /var/packages/tvheadend-4.0/target location and everything in it?

@mattiasdh

This comment has been minimized.

Show comment
Hide comment
@mattiasdh

mattiasdh Jul 6, 2015

@freddysmith1 I can confirm this on DS414 (armadaxp architecture), same [ ERROR]:spawn: /bin/tar: ./accesscontrol/1: Cannot open: Permission denied
Tried default (blank "admin") login and pass, and setting my own - same error. 401 Unauthorized on login screen..
@jdierkse - my linux skills are way too limited for that, can I test another version where this error might be fixed? If so, which one?
Thanks in advance!

mattiasdh commented Jul 6, 2015

@freddysmith1 I can confirm this on DS414 (armadaxp architecture), same [ ERROR]:spawn: /bin/tar: ./accesscontrol/1: Cannot open: Permission denied
Tried default (blank "admin") login and pass, and setting my own - same error. 401 Unauthorized on login screen..
@jdierkse - my linux skills are way too limited for that, can I test another version where this error might be fixed? If so, which one?
Thanks in advance!

@m4tt075

This comment has been minimized.

Show comment
Hide comment
@m4tt075

m4tt075 Jul 6, 2015

Contributor

@jdierkse No need to be sorry for anything. I have no clue how you guys are managing all this stuff next to your day jobs. Many thanks for clarifying!

@freddysmith1 @mattiasdh Can only test on the weekend, but if you want you can try the following:

ssh into your DS. Once you are in, enter

cat /etc/group

If there is a row starting with "tvheadend-4.0" in the output, the correct user should exist, if not it doesn't -> Report back
If there is a row starting with "tvheadend-testing" instead, please let us know whether you installed the tvheadened-testing package prior or in addition to tvheadend-4.0 and report this here too. Then, enter

stat /var/packages/tvheadend-4.0/target/

Check the bracket after "Uid" to see who owns this directory (should be "tvheadend-4.0") -> Report back what you see

stat /var/packages/tvheadend-4.0/target/*

will then give you the owners of the subdirectories. Please report too.

This should answer @jdierkse's questions...

Contributor

m4tt075 commented Jul 6, 2015

@jdierkse No need to be sorry for anything. I have no clue how you guys are managing all this stuff next to your day jobs. Many thanks for clarifying!

@freddysmith1 @mattiasdh Can only test on the weekend, but if you want you can try the following:

ssh into your DS. Once you are in, enter

cat /etc/group

If there is a row starting with "tvheadend-4.0" in the output, the correct user should exist, if not it doesn't -> Report back
If there is a row starting with "tvheadend-testing" instead, please let us know whether you installed the tvheadened-testing package prior or in addition to tvheadend-4.0 and report this here too. Then, enter

stat /var/packages/tvheadend-4.0/target/

Check the bracket after "Uid" to see who owns this directory (should be "tvheadend-4.0") -> Report back what you see

stat /var/packages/tvheadend-4.0/target/*

will then give you the owners of the subdirectories. Please report too.

This should answer @jdierkse's questions...

@m4tt075

This comment has been minimized.

Show comment
Hide comment
@m4tt075

m4tt075 Jul 7, 2015

Contributor

@jdierkse Couldn't wait so ran a quick(!) test tonight:
Same as with my predecessors.
The user "tvheadend-4.0" is created and appears in /etc/group, /etc/passwd, but not in /etc/shadow (unlike "tvheadend-testing", which does)
/var/packages/tvheadend-4.0/target/ is owned by "root", not "tvheadend-4.0"
The ownership of the "var" subdirectory is correct ("tvheadend-4.0"), all other subdirectories are owned by "root" again.
Not sure but the "." in the username seems to screw up "chown" commands as it interprets the "." like ":" to separate owner from group. But not familiar with busybox to be honest.

Contributor

m4tt075 commented Jul 7, 2015

@jdierkse Couldn't wait so ran a quick(!) test tonight:
Same as with my predecessors.
The user "tvheadend-4.0" is created and appears in /etc/group, /etc/passwd, but not in /etc/shadow (unlike "tvheadend-testing", which does)
/var/packages/tvheadend-4.0/target/ is owned by "root", not "tvheadend-4.0"
The ownership of the "var" subdirectory is correct ("tvheadend-4.0"), all other subdirectories are owned by "root" again.
Not sure but the "." in the username seems to screw up "chown" commands as it interprets the "." like ":" to separate owner from group. But not familiar with busybox to be honest.

@jdierkse

This comment has been minimized.

Show comment
Hide comment
@jdierkse

jdierkse Jul 8, 2015

@m4tt075 I think your point on the username might be valid.
I've started a new build of the 4.0.5 version, and changed the user to tvheadend-4_0

jdierkse commented Jul 8, 2015

@m4tt075 I think your point on the username might be valid.
I've started a new build of the 4.0.5 version, and changed the user to tvheadend-4_0

@Diaoul

This comment has been minimized.

Show comment
Hide comment
@Diaoul

Diaoul Jul 8, 2015

Member

Please reopen a PR against master so we can discuss the code quality. This is not a forum but a bug tracker.
Also in that new PR, name the user tvheadend-testing for consistency and avoid hardcoding the version number in username.
Further discussion will be done there. I lock the PR.

Member

Diaoul commented Jul 8, 2015

Please reopen a PR against master so we can discuss the code quality. This is not a forum but a bug tracker.
Also in that new PR, name the user tvheadend-testing for consistency and avoid hardcoding the version number in username.
Further discussion will be done there. I lock the PR.

@SynoCommunity SynoCommunity locked and limited conversation to collaborators Jul 8, 2015

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.