1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

Automatic submission by obs-autosubmit

• Files Changed
• Browse Source

- updated to 1.12
 - The last release had the wrong repo info in the metadata.
 
 - The latest historical changes in DateTime::TimeZone 1.74 caused some tests
   to fail. Reported by Slaven Rezic. RT #98483.
 
 - This release of DateTime.pm now requires the DateTime::TimeZone 1.74.

• Files Changed
• Browse Source

Split 13.2 from Factory

• Files Changed
• Browse Source

- updated to 1.10
 
 - Some tests added in 1.09 would fail on a Perl without a 64-bit
   gmtime(). Reported by Jerome Eteve. RT #95345.
 
 
 1.09   2014-05-03
 
 - A call to ->truncate( to => 'week' ) could fail but leave the object
   changed. RT #93347.
 
 - The value of ->jd() is now calculated based on ->mjd() instead of the other
   way around. This reduces floating point errors a bit when calculating MJD,
   and should have a neglible impact on the accuracy of JD. Reported by Anye
   Li. RT #92972. See the ticket for a more detailed description of what this
   fixes.
 
 - Attempting to construct a DateTime object with a year >= 5000 and a time
   zone other than floating or DST now issues a warning. This warning may go
   away once DateTime::TimeZone is made much faster. Inspired by a bug report
   from Lloyd Fournier. RT #92655.
 
 
 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 .

• Files Changed
• Browse Source

update

• Files Changed
• Browse Source

- removed obsolete patches:
  * DateTime-0.72-Build.patch (forwarded request 221731 from leonardocf)

• Files Changed
• Browse Source

- updated to 1.04
 - 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.

• Files Changed
• Browse Source

Split 13.1 from Factory

• Files Changed
• Browse Source

- updated to 1.03
 - 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.
 
 - 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.
 
 - Fixed test failures on older Perls.
 
 - 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. (forwarded request 177336 from coolo)

• Files Changed
• Browse Source

Split 12.3 from Factory

• Files Changed
• Browse Source

branched from openSUSE:Factory

• Files Changed
• Browse Source

Automatic submission by obs-autosubmit

• Files Changed
• Browse Source

• Files Changed
• Browse Source