Re: UK RT grabber still an hour out for me

Neil Bird <[email protected]>
Newsgroups gmane.comp.tv.xmltv.general
Message-ID <[email protected]>
Around about 29/04/11 03:57, Nick Morrott typed ...
>> Date::Manip::DM5 using TZ=UTC
>
> Your machine is (erroneously?) reporting it is currently configured
> for the UTC timezone

   No, both XMLTV.pm *and* tv_grab_uk_rt force the use of UTC by calling 
Date_Init("TZ=UTC") - it's one of the things I questioned first time around 
the loop.  The "TZ=UTC" thing *only* works for DM5;  it's ignored for DM6 
(the versions I have), and it (AFAICS) prevents a lot of DM stuff working 
properly.


>> ParseData output: 2011033105:00:00
>
> Not sure why the script moves ahead 3 days here, but as your machine
> reports it is using UTC (are therefore DM is for its calculations),
> the data parsing converts the BST data to UTC

   Ah, the day thing's my fault;  I cut'n'paste my previous results in order 
to show a failed run (as my DM was then patched to work for me), but 
attached the latest test script in which I'd changed the day, so they didn't 
quite tally.


>> Got '20110328050000 +0100'
> Hmmm...

   That was my thought :)


> Here's what I get (after fixing the script a bit so it would compile
> on my machine). Note the differences:
>
> Input is '2011032806:00'
> Got '20110328070000 +0100'

   But that's not right either, is it?  The "input" represents what's come 
from the RT site, and so is implicitly BST.  So you should have got the same 
thing back, but with no colon and " +0100" tacked on the end?

   So, the current test script (the one I attached and you ran) on my 
*nobbled to work* system gives [edited down]:

Input is '2011032806:00'
Got '20110328060000 +0100'


> I am worried though that your problematic system is reporting it is in
> the wrong timezone - what output from your script do you get on your
> Fedora box that doesn't have the issue? Is it the same as mine above?
> What output from `date`? Apologies if these answers are buried in
> other threads.

   Again, it's not reporting the “wrong” timezone, it's the TZ that's been 
forced upon it:

XMLTV.pm:2111
BEGIN {
   Date::Manip::Date_Init("TZ=UTC");
}


tv_grab_uk_rt:148
# UTC required for XMLTV::DST
Date_Init('TZ=UTC');


PS - I think, when I tried, that trying to *change* the TZ where 
tv_grab_uk_rt does it fails abysmally under DM5 - it “works” here as it's 
staying the same value.  I think I posted elsewhere the hacky code needed to 
fiddle with it.

-- 
[neil@fnx ~]# rm -f .signature
[neil@fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil@fnx ~]# exit


------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
xmltv-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xmltv-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.