Hello community,

here is the log from the commit of package python-gobject for openSUSE:13.1 
checked in at 2013-10-15 10:44:02
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:13.1/python-gobject (Old)
 and      /work/SRC/openSUSE:13.1/.python-gobject.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-gobject"

Changes:
--------
--- /work/SRC/openSUSE:13.1/python-gobject/python-gobject.changes       
2013-09-27 18:01:31.000000000 +0200
+++ /work/SRC/openSUSE:13.1/.python-gobject.new/python-gobject.changes  
2013-10-15 10:44:02.000000000 +0200
@@ -1,0 +2,11 @@
+Mon Oct 14 11:16:43 UTC 2013 - [email protected]
+
+- Update to version 3.10.1:
+  + bgo#709926: Fix TypeError when setting drag target_list to
+    None.
+  + bgo#709223: Use qdata for wrapper retrieval in toggle reference
+    notifications.
+  + bgo#709397: Fix memory leak for caller allocated GValue out
+    arguments.
+
+-------------------------------------------------------------------
python3-gobject.changes: same change

Old:
----
  pygobject-3.10.0.tar.xz

New:
----
  pygobject-3.10.1.tar.xz

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

Other differences:
------------------
++++++ python-gobject.spec ++++++
--- /var/tmp/diff_new_pack.ScBapA/_old  2013-10-15 10:44:03.000000000 +0200
+++ /var/tmp/diff_new_pack.ScBapA/_new  2013-10-15 10:44:03.000000000 +0200
@@ -37,7 +37,7 @@
 Summary:        Python bindings for GObject
 License:        LGPL-2.1+
 Group:          Development/Libraries/Python
-Version:        3.10.0
+Version:        3.10.1
 Release:        0
 Url:            http://ftp.gnome.org/pub/GNOME/sources/pygobject/
 Source:         
http://download.gnome.org/sources/pygobject/3.10/%{_name}-%{version}.tar.xz

python3-gobject.spec: same change
++++++ pygobject-3.10.0.tar.xz -> pygobject-3.10.1.tar.xz ++++++
++++ 26710 lines of diff (skipped)

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

Reply via email to