Re: UK RT grabber still an hour out for me

On 28 April 2011 16:02, Neil Bird <[email protected]> wrote:
> Around about 28/04/11 10:53, Nick Morrott typed ...
>>
>> My MythTV master backend (untouched since installation) is running
>> Perl 5.8.6 and Date::Manip 5.44 on an old Fedora release. I don't see
>> any problems using the current XMLTV release.
>
>  I have:
>
> perl-XMLTV-0.5.59-84.el5.noarch.rpm
> perl-5.8.8-32.el5_5.2.i386.rpm
> perl-Date-Manip-6.14-0_15.el5.noarch.rpm
>
>
>  Could you please run my test script on your old Fedora box?

Sure - I've dropped in comments to see if I understand (at this late
hour) what is going on...

> I'll re-attach
> it (same as previous post).  It gives me (well, gave me, I've patched my
> DM5.pm now):
>
> Perl is 5.008008, Date::Manip in use is 5.60
> Input is '2011032806:00'
> First utc_offset call produced '20110328060000 +0100'
>  Implicit timezone calculated to be '+0100'

utc_offset seems to be correct here

> Date::Manip::DM5 using TZ=UTC

Your machine is (erroneously?) reporting it is currently configured
for the UTC timezone

> 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

> parse_date -> '2011032805:00:00'

Same thing here - conversion is happening from BST to UTC

> parse_local_date -> '2011032805:00:00'

No change here, as conversions is from UTC to +0000 - the same thing

> date_to_local -> '2011032805:00:00 +0100'

Seems correct based on previous cals - date_to_local knows when BST
starts/ends and is applying the +0100

> Got '20110328050000 +0100'

Hmmm...


Here's what I get (after fixing the script a bit so it would compile
on my machine). Note the differences:

Perl is 5.008006, Date::Manip in use is 5.44
Input is '2011032806:00'
First utc_offset call produced '20110328060000 +0100'
  Implicit timezone calculated to be '+0100'
Date::Manip::DM5 using TZ=BST
ParseData output: 2011033106:00:00
parse_date -> '2011032806:00:00'
parse_local_date -> '2011032806:00:00'
date_to_local -> '2011032807:00:00 +0100'
Got '20110328070000 +0100'

>  The important lines are the "Input is" and the final "Got";  note it goes
> from 06:00 [implicit BST] to 05:00 +0100.
>
>  I wonder if there's a bug that came in after DM 5.44, since I have 5.60.

I think Date::Manip 5.60 is the "pseudo-version" of DM5 that comes
with the regular DM6 release and is used when Perl is not recent
enough. My DM 5.44 is a regular 5.xx release from "a while ago" :)

There may well be a bug lurking here - I know the DST handling stuff
was updated to handle the DM6 issues that surfaced a year ago - but
these were changes for users actually using the DM6 code, rather than
the DM5 fallback support. There are a lot of MythTV users running
CentOS. so I'm surprised too more users haven't reported the issue.

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.

Cheers,
Nick

-- 
Nick Morrott

MythTV Official wiki: http://mythtv.org/wiki/
MythTV users list archive: http://www.gossamer-threads.com/lists/mythtv/users

"An investment in knowledge always pays the best interest." - Benjamin Franklin

------------------------------------------------------------------------------
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