Hello community,

here is the log from the commit of package telepathy-logger for 
openSUSE:Factory checked in at 2014-09-15 17:40:30
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/telepathy-logger (Old)
 and      /work/SRC/openSUSE:Factory/.telepathy-logger.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "telepathy-logger"

Changes:
--------
--- /work/SRC/openSUSE:Factory/telepathy-logger/telepathy-logger.changes        
2013-04-02 13:28:04.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.telepathy-logger.new/telepathy-logger.changes   
2014-09-15 17:40:32.000000000 +0200
@@ -1,0 +2,6 @@
+Mon Aug 25 15:24:50 UTC 2014 - [email protected]
+
+- Update to version 0.8.1:
+  + Fixes: Fix a leak in log-store-xml (fdo#54814).
+
+-------------------------------------------------------------------

Old:
----
  telepathy-logger-0.8.0.tar.bz2

New:
----
  telepathy-logger-0.8.1.tar.bz2

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

Other differences:
------------------
++++++ telepathy-logger.spec ++++++
--- /var/tmp/diff_new_pack.Qon2bi/_old  2014-09-15 17:40:33.000000000 +0200
+++ /var/tmp/diff_new_pack.Qon2bi/_new  2014-09-15 17:40:33.000000000 +0200
@@ -1,7 +1,7 @@
 #
 # spec file for package telepathy-logger
 #
-# Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2014 SUSE LINUX Products GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -17,7 +17,7 @@
 
 
 Name:           telepathy-logger
-Version:        0.8.0
+Version:        0.8.1
 Release:        0
 Summary:        Centralized Logging for the Telepathy Framework
 License:        LGPL-2.1+

++++++ telepathy-logger-0.8.0.tar.bz2 -> telepathy-logger-0.8.1.tar.bz2 ++++++
++++ 10422 lines of diff (skipped)

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

Reply via email to