XMLTV / xmltv

Utilities to obtain, generate, and post-process TV listings data in XMLTV format
GNU General Public License v2.0
275 stars 93 forks source link

differing timezone between channels #111

Closed joshinils closed 3 years ago

joshinils commented 4 years ago

XMLTV Version?

XMLTV module version 0.6.1 This is tv_grab_eu_xmltvse version 0.6.1

XMLTV Component?

This is tv_grab_eu_xmltvse version 0.6.1

What happened?

timestamps are differing in timezone between channels

What did you expect to happen?

every channel to be encoded with the same timezone

Did you see any warnings/errors?

no

What steps are needed to reproduce this issue?

tv_grab_eu_xmltvse --config-file .xmltv/tv_grab_eu_xmltvse.conf --output tv.xml in the directory which is cloned from: https://github.com/joshinils/tv/ ie. using https://github.com/joshinils/tv/blob/master/.xmltv/tv_grab_eu_xmltvse.conf as the config file

hd.daserste.de is apparently in utc, whereas berl.rbb-online.de is in localtime utc+2 (summertime) but the timestamp in the xml file is encoded with start="20200907140000 +0000" both have the same +0000.

Any other information?

apparently today all info for hd.daserste.de is gone, great. soo i cant really test this.

What other software are you using?

Operating System: NAME="Ubuntu" VERSION="20.04.1 LTS (Focal Fossa)"

Perl Version: This is perl 5, version 30, subversion 0 (v5.30.0) built for x86_64-linux-gnu-thread-multi (with 46 registered patches, see perl -V for more detail)

joshinils commented 4 years ago

hm, looks like half of the channels I chose are not working anymore.

garybuhrmaster commented 3 years ago

The tv_grab_eu_xmltvse grabber (after some configuration setup) essentially just pulls the xmltv files directly from xmltv.se itself (which generates them using its own mechanisms). If the schedule data is incorrect it is likely best to open tickets with the upstream (the xmltv.se site) who would likely need to correct any offset issues (and such fixes would also fix the scheduling data for other users of that upstream source).

joshinils commented 3 years ago

Right, I have done so.

honir commented 3 years ago

Closing this issue as this is a fault in the upstream data provider and @joshinils has logged a ticket there.