Hello community,

here is the log from the commit of package libcryptui for openSUSE:Factory 
checked in at 2013-09-27 17:38:59
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libcryptui (Old)
 and      /work/SRC/openSUSE:Factory/.libcryptui.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "libcryptui"

Changes:
--------
--- /work/SRC/openSUSE:Factory/libcryptui/libcryptui.changes    2013-08-27 
20:51:29.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.libcryptui.new/libcryptui.changes       
2013-09-27 17:39:00.000000000 +0200
@@ -1,0 +2,7 @@
+Mon Sep 23 19:15:01 UTC 2013 - [email protected]
+
+- Update to version 3.10.0:
+  + Build fix.
+  + Updated translations.
+
+-------------------------------------------------------------------

Old:
----
  libcryptui-3.9.90.tar.xz

New:
----
  libcryptui-3.10.0.tar.xz

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

Other differences:
------------------
++++++ libcryptui.spec ++++++
--- /var/tmp/diff_new_pack.PbIa1A/_old  2013-09-27 17:39:01.000000000 +0200
+++ /var/tmp/diff_new_pack.PbIa1A/_new  2013-09-27 17:39:01.000000000 +0200
@@ -17,14 +17,14 @@
 
 
 Name:           libcryptui
-Version:        3.9.90
+Version:        3.10.0
 Release:        0
 # FIXME: find out why building introspection support for this package requires 
libtool
 Summary:        Library for prompting for PGP keys
 License:        LGPL-2.1+ and GPL-2.0+
 Group:          Productivity/Security
 Url:            http://projects.gnome.org/seahorse/
-Source:         
http://download.gnome.org/sources/libcryptui/3.9/%{name}-%{version}.tar.xz
+Source:         
http://download.gnome.org/sources/libcryptui/3.10/%{name}-%{version}.tar.xz
 BuildRequires:  gobject-introspection-devel
 BuildRequires:  gpg2
 BuildRequires:  gpgme-devel

++++++ libcryptui-3.9.90.tar.xz -> libcryptui-3.10.0.tar.xz ++++++
++++ 5065 lines of diff (skipped)

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

Reply via email to