Hello community,

here is the log from the commit of package dateutils for openSUSE:Factory 
checked in at 2013-11-04 12:45:54
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/dateutils (Old)
 and      /work/SRC/openSUSE:Factory/.dateutils.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "dateutils"

Changes:
--------
--- /work/SRC/openSUSE:Factory/dateutils/dateutils.changes      2013-07-30 
16:13:30.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.dateutils.new/dateutils.changes 2013-11-04 
12:46:08.000000000 +0100
@@ -1,0 +2,14 @@
+Tue Oct 29 16:45:20 UTC 2013 - [email protected]
+
+- bump version 0.2.6, this is a bug fix release.
+  * issue 19, -q|--quiet no longer sends some commands into an
+    inf-loop
+  * netbsd test failures are fixed (due to missing leap seconds)
+  * AIX builds are supported (getopt_long() is part of the code
+    now)
+  * internally the test harness is migrated to the cli-testing tool
+    this fixes an issue when tests are run in directories with odd
+    names (spaces, dollar signs, etc. in the path name)
+  * See info page examples and/or README. 
+
+-------------------------------------------------------------------

Old:
----
  dateutils-0.2.5.tar.xz

New:
----
  dateutils-0.2.6.tar.xz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ dateutils.spec ++++++
--- /var/tmp/diff_new_pack.vjGTyH/_old  2013-11-04 12:46:08.000000000 +0100
+++ /var/tmp/diff_new_pack.vjGTyH/_new  2013-11-04 12:46:08.000000000 +0100
@@ -16,10 +16,10 @@
 #
 
 
-%define xversion 0.2.5
+%define xversion 0.2.6
 
 Name:           dateutils
-Version:        0.2.5
+Version:        0.2.6
 Release:        0
 Summary:        Nifty command line date and time utilities
 License:        BSD-3-Clause

++++++ dateutils-0.2.5.tar.xz -> dateutils-0.2.6.tar.xz ++++++
++++ 62058 lines of diff (skipped)

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to