Hello community,

here is the log from the commit of package rubygem-json_pure for 
openSUSE:Factory checked in at 2012-04-17 22:01:45
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/rubygem-json_pure (Old)
 and      /work/SRC/openSUSE:Factory/.rubygem-json_pure.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "rubygem-json_pure", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/rubygem-json_pure/rubygem-json_pure.changes      
2012-02-20 16:18:31.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.rubygem-json_pure.new/rubygem-json_pure.changes 
2012-04-17 22:01:48.000000000 +0200
@@ -1,0 +2,11 @@
+Thu Apr  5 08:15:45 UTC 2012 - [email protected]
+
+- update to 1.6.6:
+  * Propagate src encoding to values made from it (fixes 1.9 mode converting
+    everything to ascii-8bit; harmless for 1.8 mode too) (Thomas E. Enebo
+    <[email protected]>), should fix
+    https://github.com/flori/json/issues#issue/119.
+  * Fix https://github.com/flori/json/issues#issue/124 Thx to Jason Hutchens.
+  * Fix https://github.com/flori/json/issues#issue/117
+
+-------------------------------------------------------------------

Old:
----
  json_pure-1.6.5.gem

New:
----
  json_pure-1.6.6.gem

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

Other differences:
------------------
++++++ rubygem-json_pure.spec ++++++
--- /var/tmp/diff_new_pack.MLy1kS/_old  2012-04-17 22:01:49.000000000 +0200
+++ /var/tmp/diff_new_pack.MLy1kS/_new  2012-04-17 22:01:49.000000000 +0200
@@ -17,10 +17,10 @@
 
 
 Name:           rubygem-json_pure
-Version:        1.6.5
+Version:        1.6.6
 Release:        0
 Summary:        JSON Implementation for Ruby
-License:        GPL-2.0+ or Ruby
+License:        Ruby
 Group:          Development/Languages/Ruby
 Url:            http://flori.github.com/json
 %define mod_name json_pure

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

Reply via email to