Hello community,

here is the log from the commit of package gcr for openSUSE:Factory checked in 
at 2012-03-29 11:39:43
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/gcr (Old)
 and      /work/SRC/openSUSE:Factory/.gcr.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "gcr", Maintainer is ""

Changes:
--------
--- /work/SRC/openSUSE:Factory/gcr/gcr.changes  2012-03-16 13:13:16.000000000 
+0100
+++ /work/SRC/openSUSE:Factory/.gcr.new/gcr.changes     2012-03-29 
11:39:45.000000000 +0200
@@ -1,0 +2,14 @@
+Mon Mar 26 13:20:40 UTC 2012 - [email protected]
+
+- Update to version 3.4.0:
+  + No changes.
+
+-------------------------------------------------------------------
+Mon Mar 19 19:03:30 UTC 2012 - [email protected]
+
+- Update to version 3.3.92:
+  + Fix up copyright headers.
+  + Build fix.
+  + Updated translations.
+
+-------------------------------------------------------------------

Old:
----
  gcr-3.3.90.tar.xz

New:
----
  gcr-3.4.0.tar.xz

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

Other differences:
------------------
++++++ gcr.spec ++++++
--- /var/tmp/diff_new_pack.uhi0Ha/_old  2012-03-29 11:39:46.000000000 +0200
+++ /var/tmp/diff_new_pack.uhi0Ha/_new  2012-03-29 11:39:46.000000000 +0200
@@ -17,14 +17,14 @@
 
 
 Name:           gcr
-Version:        3.3.90
+Version:        3.4.0
 Release:        0
 # FIXME: Verify if parallel build works again. Last checked in version 3.3.2
 Summary:        Library for Crypto UI related task
 License:        LGPL-2.1+
 Group:          System/Libraries
 Url:            http://www.gnome.org
-Source0:        
http://download.gnome.org/sources/gcr/3.3/%{name}-%{version}.tar.xz
+Source0:        
http://download.gnome.org/sources/gcr/3.4/%{name}-%{version}.tar.xz
 # For directory ownership
 BuildRequires:  dbus-1
 BuildRequires:  gobject-introspection-devel

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

Reply via email to