Skip Menu |

This queue is for tickets about the Parse-Win32Registry CPAN distribution.

Report information
The Basics
Id: 124514
Status: resolved
Priority: 0/
Queue: Parse-Win32Registry

People
Owner: jmacfarla [...] cpan.org
Requestors: bitcardbmw [...] lsmod.de
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 1.0
Fixed in: 1.1



Subject: dates misinterpreted after 2020
similar to https://rt.cpan.org/Public/Bug/Display.html?id=124508 after 2020-01-01 tests were failing because year 70 was now interpreted as 2070 The trivial fix is to apply to Parse-Win32Registry-1.0/lib/Parse/Win32Registry/Base.pm and Parse-Win32Registry-1.0/t/misc.t - my $epoch_offset = timegm(0, 0, 0, 1, 0, 70); + my $epoch_offset = timegm(0, 0, 0, 1, 0, 1970);
On 2018-02-21 09:36:46, bmwiedemann wrote: Show quoted text
> similar to https://rt.cpan.org/Public/Bug/Display.html?id=124508 > > after 2020-01-01 tests were failing because year 70 was now > interpreted as 2070 > > The trivial fix is to apply to > Parse-Win32Registry-1.0/lib/Parse/Win32Registry/Base.pm > and > Parse-Win32Registry-1.0/t/misc.t > > - my $epoch_offset = timegm(0, 0, 0, 1, 0, 70); > + my $epoch_offset = timegm(0, 0, 0, 1, 0, 1970);
It seems that the test suite started to fail in 2020 because of this problem. Sample fail report at CPAN Testers: http://www.cpantesters.org/cpan/report/e073adfa-2c9f-11ea-b244-78aeea451609
Patch applied in version 1.1.