#86 closed defect (fixed)
augment_timezone defaults to "Null"
Reported by: | Craig | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 1.0 |
Component: | Postprocessor | Version: | 1.x |
Keywords: | augment_timezone | Cc: | cas@… |
Description
augment_timezone is written with the assumption that it will always be used with mythtv.
i use shephere with xmltv2vdr to populate the program listings for my VDR setup, so have no mythtv config and no mythtv mysql database with a settings table to fetch the TimeOffset? value from.
this results in all xmltv records without an explicit timezone being set to GMT. in particular, this screws up listings for ABC1 & ABC2.
i've edited the augment_timezone script by adding:
$opt->{timeoffset} = '+1000';
near the start of the script. that fixes the problem, but causes shepherd to complain about augment_timezone being "tainted". it also means that i will have to make the same edit after every update of augment_timezone, and again whenever daylight savings starts or finishes.
i've also tried editing shepherd.conf to add:
'timeoffset' => '+1000'
to the config => { ... } stanza for augment_timezone. unfortunately, that is ignored and then removed the next time shepherd is run.
what's needed is a way for shepherd to manually specify augment_timezone's timeoffset option. this should be relatively easy since a_t already accepts it as a command line option.
Change History (4)
comment:1 Changed 15 years ago by
comment:2 Changed 15 years ago by
i've just run:
./shepherd --component-set augment_timezone:timeoffset='+1000'
and edited augment_timezone back to what it was.
shepherd has already run today, so i'll wait until tomorrow to find out if it works.
comment:3 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
that seems to work fine here.
comment:4 Changed 13 years ago by
Milestone: | → 1.0 |
---|
Does this help?
http://svn.whuffy.com/index.cgi/wiki/FAQ#CanIsetsomedefaultoptions