Hello community,

here is the log from the commit of package fcitx-unikey for openSUSE:Factory 
checked in at 2012-10-31 13:52:50
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/fcitx-unikey (Old)
 and      /work/SRC/openSUSE:Factory/.fcitx-unikey.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "fcitx-unikey", Maintainer is ""

Changes:
--------
--- /work/SRC/openSUSE:Factory/fcitx-unikey/fcitx-unikey.changes        
2012-06-26 15:36:36.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.fcitx-unikey.new/fcitx-unikey.changes   
2012-10-31 13:52:55.000000000 +0100
@@ -1,0 +2,7 @@
+Mon Oct 29 15:47:28 UTC 2012 - [email protected]
+
+- update version 0.1.1
+  * Fix some typing related bug.
+  * Add a new qt based macro editor.
+
+-------------------------------------------------------------------

Old:
----
  fcitx-unikey-0.1.0.tar.xz

New:
----
  fcitx-unikey-0.1.1.tar.bz2

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

Other differences:
------------------
++++++ fcitx-unikey.spec ++++++
--- /var/tmp/diff_new_pack.PqXxBE/_old  2012-10-31 13:52:57.000000000 +0100
+++ /var/tmp/diff_new_pack.PqXxBE/_new  2012-10-31 13:52:57.000000000 +0100
@@ -17,19 +17,18 @@
 
 
 Name:           fcitx-unikey
-Version:       0.1.0
+Version:       0.1.1
 Release:       0
 License:       GPL-3.0+
 Summary:       Vietnamese unikey support for Fcitx
 Url:   https://github.com/fcitx/fcitx-unikey
 Group: System/I18n/Chinese
-Source:        %{name}-%{version}.tar.xz
+Source:        %{name}-%{version}.tar.bz2
 BuildRequires: cmake
 BuildRequires: fcitx-devel >= 4.2.3
 BuildRequires: fdupes
 BuildRequires: gcc-c++
 BuildRequires: intltool
-BuildRequires: xz
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 
 %description

++++++ fcitx-unikey-0.1.0.tar.xz -> fcitx-unikey-0.1.1.tar.bz2 ++++++
++++ 12177 lines of diff (skipped)

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

Reply via email to