Package: libtimedate-perl
Version: 1.1900-1
Severity: normal
With libtimedate-perl 1.1600-9:
$ perl -MDate::Parse -e \
'print gmtime(str2time("26 Apr 07 21:38:23 -0700"))."\n"'
Fri Apr 27 04:38:23 2007
This is OK. But with libtimedate-perl 1.1900-1:
$ perl -MDate::Parse -e \
'print gmtime(str2time("26 Apr 07 21:38:23 -0700"))."\n"'
Sat Apr 27 04:38:23 1907
The year is incorrect.
Even though a 2-digit year may be ambiguous (still generated by some
software unfortunately), 2007 is the correct interpretation.
I suggest to use the rule specified by the RFC 2822:
Where a two or three digit year occurs in a date, the year is to be
interpreted as follows: If a two digit year is encountered whose
value is between 00 and 49, the year is interpreted by adding 2000,
ending up with a value between 2000 and 2049. If a two digit year is
encountered with a value between 50 and 99, or any three digit year
is encountered, the year is interpreted by adding 1900.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages libtimedate-perl depends on:
ii perl 5.10.1-8 Larry Wall's Practical Extraction
libtimedate-perl recommends no packages.
libtimedate-perl suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
