2014-04-20 04:39:32 by Wen Heping | Files touched by this commit (2) |
Log message:
Update to 1.08
Upstream changes:
1.08 2014-03-11
- DateTime now calls DateTime->_core_time() instead of calling Perl's time()
built-in directly. This makes it much easier to override the value of time()
that DateTime sees. This may make it easier to write tests for code that
uses DateTime .
1.07 2014-02-06
- Added a hack to get this module working on Android. RT #92671.
|
2014-01-09 09:03:45 by Wen Heping | Files touched by this commit (2) |
Log message:
Update to 1.06
Upstream changes:
1.06 2013-12-31
- DateTime's attempt to generate infinity by calculating 9**9**9 actually got
a number on some platforms, like powerpcspe. Reported by Gregor Hermann. RT
#91696.
1.05 2013-12-22
- Added a new CLDR ZZZZZ specifier, which is like ZZZ but inserts a
colon. Patch by Ricardo Signes.
- Added a new option for the truncate() method to truncate to the
"local_week". This truncates to the locale's notion of the first day \
of the
week, rather than always truncating to Monday. Patch by Christian Hansen.
1.04 2013-12-07
- Calling set_locale() or set_formatter() on an object with an ambiguous local
time could change the underlying UTC time for that object. Reported by Marta
Cuaresma Saturio. RT #90583.
|
2013-08-30 10:01:23 by Wen Heping | Files touched by this commit (2) |
Log message:
Update to 1.03
Upstream changes:
1.03 2013-04-17
- The set_time_zone() method was not returning the object when caalled with a
name that matched the current zone. Reported by Noel Maddy. RT #84699.
1.02 2013-04-15
- When a constructor method like new() or today() was called on an object,
you'd get an error message like 'Can't locate object method
"_normalize_nanoseconds" via package \
"2013-04-15T00:00:00"'. This has been
fixed to provide a sane error message. Patch by Doug Bell.
- When set_time_zone() is called with a name that matches the current time
zone, DateTime now short circuits and avoids a lot of work. Patch by Mark
Stosberg.
|
2013-05-31 14:42:58 by Thomas Klausner | Files touched by this commit (2880) |
Log message:
Bump all packages for perl-5.18, that
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
|
2013-04-03 09:09:09 by Wen Heping | Files touched by this commit (2) |
Log message:
Update to 1.01
Upstream changes:
1.01 2013-04-01
- Fixed test failures on older Perls.
1.00 2013-03-31
- Bumped the version to 1.00. This is mostly because my prior use of both X.YY
and X.YYYY versions causes trouble for some packaging systems. Plus after 10
years it's probably ready to be called 1.00. Requested by Adam. RT #82800.
- The %j specifier for strftime was not zero-padding 1 and 2 digit
numbers. Fixed by Christian Hansen. RT #84310.
- The truncate method was sloppy about validating its "to" parameter, \
so you
could pass things like "years" or "month whatever anything \
goes". The method
would accept the parameter but then not actually truncate the object. RT
#84229.
- Previously, if a call to $dt->set_time_zone() failed it would still change
the time zone of the object, leaving it in a broken state. Reported by Bill
Moseley. RT #83940.
- DateTime::Infinite objects should no longer die when methods that require a
locale are called. Instead, these methods return undef for names and
Inf/-Inf for numbers. This affects methods such as day_name() as well as
CLDR and strftime formats. When a locale-specific format is used (like the
"full" datetime format) it uses the en_US format. Reported by Paul
Boldra. RT #67550.
|
2012-11-17 17:05:42 by Wen Heping | Files touched by this commit (2) |
Log message:
Update to 0.78
Upstream changes:
0.78 2012-11-16
- Reverted the change to round nanoseconds up or down in various
situtations. Now we always round down. This avoids the case where rounding
up would require us to then increment the second value (which could then
require us to increment the minute, which could then require us to increment
the hour, which could then ...).
In other words, we don't want to round 2011-12-31T23:59:59.999999 up to
2012-01-01T00:00:00, because that would be insane.
This applies to the return values for ->microsecond, ->millisecond, and the
%N specifier for strftime.
Patch by Martin Hasch. RT #79845.
|
2012-10-08 16:42:08 by Wen Heping | Files touched by this commit (2) |
Log message:
Update to 0.77
Upstream changes:
0.77 2012-09-25
- POD changes that should make the documentation look better, especially on
the web.
|
2012-10-08 15:04:32 by Aleksej Saushev | Files touched by this commit (146) |
Log message:
Drop PKG_DESTDIR_SUPPORT setting, "user-destdir" is default these days.
|
2012-10-03 23:59:10 by Thomas Klausner | Files touched by this commit (2798) |
Log message:
Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.
I hope that's all of them.
|
2012-07-06 13:53:37 by Jens Rehsack | Files touched by this commit (2) |
Log message:
Updating package for Perl 5 module DateTime in time/p5-DateTime from 0.7400
to 0.7600.
Upstream changes:
0.76 2012-07-01
- The DateTime->subtract method ignored the end_of_month parameter. Patch by
Chris Reinhardt. RT #77844.
0.75 2012-06-11
- The epoch for years 1-999 was broken because Time::Local is \
"clever". A pox
on all clever APIs, I say! Reported by Christian Hansen. RT #77719.
- Shut up compilation warning from 5.17.x. Reported by Tom Wyant. RT #77490.
|