Hello community,

here is the log from the commit of package libunistring for openSUSE:Factory 
checked in at 2017-12-10 18:15:53
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libunistring (Old)
 and      /work/SRC/openSUSE:Factory/.libunistring.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "libunistring"

Sun Dec 10 18:15:53 2017 rev:24 rq:555393 version:0.9.8

Changes:
--------
--- /work/SRC/openSUSE:Factory/libunistring/libunistring.changes        
2017-08-22 11:06:25.703417341 +0200
+++ /work/SRC/openSUSE:Factory/.libunistring.new/libunistring.changes   
2017-12-10 18:16:00.371306552 +0100
@@ -1,0 +2,10 @@
+Fri Dec  1 19:37:45 UTC 2017 - [email protected]
+
+- update to 0.9.8:
+  * The data tables and line breaking algorithm have been updated
+    to Unicode version 9.0.0
+  * In the include file unigbrk.h, the function uc_grapheme_breaks
+    has been added to accommodate the new UAX#29 rules involving 3
+    or more consecutive characters
+
+-------------------------------------------------------------------

Old:
----
  libunistring-0.9.7.tar.xz
  libunistring-0.9.7.tar.xz.sig

New:
----
  libunistring-0.9.8.tar.xz
  libunistring-0.9.8.tar.xz.sig

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

Other differences:
------------------
++++++ libunistring.spec ++++++
--- /var/tmp/diff_new_pack.f5iuhT/_old  2017-12-10 18:16:01.223265972 +0100
+++ /var/tmp/diff_new_pack.f5iuhT/_new  2017-12-10 18:16:01.223265972 +0100
@@ -18,7 +18,7 @@
 
 %define lname  libunistring2
 Name:           libunistring
-Version:        0.9.7
+Version:        0.9.8
 Release:        0
 Summary:        GNU Unicode string library
 License:        LGPL-3.0+ or GPL-2.0

++++++ libunistring-0.9.7.tar.xz -> libunistring-0.9.8.tar.xz ++++++
++++ 295000 lines of diff (skipped)

++++++ libunistring.keyring ++++++
Binary files /var/tmp/diff_new_pack.f5iuhT/_old and 
/var/tmp/diff_new_pack.f5iuhT/_new differ


Reply via email to