Hello community, here is the log from the commit of package rubygem-pg for openSUSE:Factory checked in at 2016-10-10 16:23:23 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/rubygem-pg (Old) and /work/SRC/openSUSE:Factory/.rubygem-pg.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "rubygem-pg" Changes: -------- --- /work/SRC/openSUSE:Factory/rubygem-pg/rubygem-pg.changes 2016-04-12 19:32:53.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.rubygem-pg.new/rubygem-pg.changes 2016-10-10 16:23:24.000000000 +0200 @@ -1,0 +2,445 @@ +Thu Sep 22 04:47:40 UTC 2016 - [email protected] + +- updated to version 0.19.0 + see installed ChangeLog + + 2016-09-04 Lars Kanis <[email protected]> + + * ext/pg_connection.c: + Replace rb_ary_new_from_args() which is missing in Ruby-2.0 + + We don't really need an Array at all, but storing the values on the + stack is enough. + [4d9c4ee44d11] [tip] + + * ext/pg_connection.c: + Use the asynchronous interface for setting the default_encoding. + + This is another attempt to solve issue https://bitbucket.org/ged + /ruby-pg/issues/245 While setting the encoding per + PQsetClientEncoding was already adjusted to release the GVL in a + previous commit, it did not solve the particular issue with + pgbouncer. + + Using the async interface has the advantage, that signals or + exception events can be processed by the given thread, while a query + is running. + [a646a1394e9d] + + * spec/pg/connection_spec.rb: + Spec: Use a more effective test for default_internal. + + UFT-8 is the standard for internal_encoding anyway, so that not + setting it did not result in a failure. + [08e7e13687e7] + + 2016-08-20 Michael Granger <[email protected]> + + * certs/ged.pem, pg.gemspec: + Correct key+cert upgrade. + + Refs #241. + [7431b5c1430d] + + * README.rdoc: + Merged with upstream + [cf9ac513102e] + + 2016-08-20 Lars Kanis <[email protected]> + + * History.rdoc, lib/pg/connection.rb: + Fix wrong exception when running SQL while in #copy_data for output. + + It raised "undefined method `result_status' for nil:NilClass" + previously and raises "no COPY in progress" now. + + This also fixes the failing test of the previous commit. + [dbfc3856e543] + + * spec/pg/connection_spec.rb: + Add tests for running SQL statements while in #copy_data. + + The test for output currently fails. + [9b2b1cd54d49] + + 2016-08-18 Lars Kanis <[email protected]> + + * Rakefile: + Don't update ext/errorcodes.def with every run of rake gem. + + This fixes the previous commit. + [43a48561adde] + + 2016-08-17 Lars Kanis <[email protected]> + + * .hgignore, History.rdoc, Rakefile, ext/errorcodes.def: + Add errorcodes.def to git in order to allow build from git per + bundler. + [29ca3eed927d] + + * History.rdoc: + Update History.rdoc once more. + [6874ea8622a1] + + * README.rdoc: + Update README regarding to Ruby and PostgreSQL versions. + [73930bce99d9] + + * spec/pg/basic_type_mapping_spec.rb: + Run JSON test on PostgreSQL-9.4+, only. + + Earlier versions miss the JSONB type. + [6b23964f70c3] + + * appveyor.yml: + Update Appveyor to use Ruby 2.3 and remove 2.0 and 2.1. + [8ff3d0b07cda] + + * .travis.yml: + Remove ruby versions before 2.2, because hoe-deveiate isn't + compatible with these versions. + [73279f9db276] + + * lib/pg/basic_type_mapping.rb, lib/pg/text_decoder.rb, + lib/pg/text_encoder.rb, spec/pg/basic_type_mapping_spec.rb: + Add JSON coders and add them to BasicTypeMapForResults and + BasicTypeMapBasedOnResult + + Fixes bitbucket issue #212 . + [b76471234f7a] + + 2016-08-14 Lars Kanis <[email protected]> + + * lib/pg/basic_type_mapping.rb: + Improve documentation to PG::BasicTypeMapForQueries + [e7181c452c64] + + * History.rdoc: + Update History.rdoc + [9c3699255853] + + 2016-08-20 Michael Granger <[email protected]> + + * BSDL, README.rdoc, ext/pg.c: + Update copyright year, license files + [c77d0997b4e4] + + * README.rdoc, certs/ged.pem: + Update/upgrade my signing cert + + Fixes #241. + [741c94c3bada] + + 2016-08-17 Michael Granger <[email protected]> + + * pg.gemspec: + Bump prerelease version in the gemspec + [f7472e7a7902] + + 2016-08-14 Lars Kanis <[email protected]> + + * Merge git master + [9b7987626074] + + 2016-08-13 Lars Kanis <[email protected]> + + * Rakefile.cross: + Update OpenSSL and PostgreSQL for binary Windows gems. + [edbd5b8dbb85] + + * History.rdoc: + Update History.rdoc + [aca7b024ba0c] + + * ext/gvl_wrappers.h, ext/pg_connection.c: + Release GVL while calling PQsetClientEncoding() + + PQsetClientEncoding() is also called within PG::Connection.new which + could block due to network delay. + + This fixes bitbucket issue #245 . + [41f81b72476f] + + 2016-06-27 Michael Granger <[email protected]> + + * ext/extconf.rb: + Add __EXTENSIONS__ to Solaris/SmartOS for Ruby >= 2.3.x + + Fixes #236. + [5979b3cba237] + + 2016-04-09 Michael Granger <[email protected]> + + * .hgignore, Rakefile, pg.gemspec: + Deprecate Ruby 1.9, fix license name + [fc5828a71f2a] + + * ext/extconf.rb: + Add mechanism for trying to build without pg_config + [22a3a8ef3244] + + 2015-12-25 Lars Kanis <[email protected]> + + * ext/pg.h, ext/pg_binary_encoder.c, ext/pg_coder.c, + ext/pg_connection.c, ext/pg_copy_coder.c, ext/pg_text_encoder.c, + spec/pg/connection_spec.rb, spec/pg/type_map_by_class_spec.rb, + spec/pg/type_map_by_mri_type_spec.rb, spec/pg/type_spec.rb: + Respect character encoding of all strings sent to the server. + + Previously all strings sent to the server were sent in their + internal binary representation, without respecting the character + encoding of strings. Now the encoding of all strings is compared + with the current connection encoding and converted if they are + different. + + Since coders are independent from any database connection, this adds + a second parameter to PG::Coder#encode, that allows to define the + destination encoding, which previously was always ASCII_8BIT. This ++++ 248 more lines (skipped) ++++ between /work/SRC/openSUSE:Factory/rubygem-pg/rubygem-pg.changes ++++ and /work/SRC/openSUSE:Factory/.rubygem-pg.new/rubygem-pg.changes Old: ---- pg-0.18.4.gem New: ---- pg-0.19.0.gem ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ rubygem-pg.spec ++++++ --- /var/tmp/diff_new_pack.KY0DEe/_old 2016-10-10 16:23:26.000000000 +0200 +++ /var/tmp/diff_new_pack.KY0DEe/_new 2016-10-10 16:23:26.000000000 +0200 @@ -24,7 +24,7 @@ # Name: rubygem-pg -Version: 0.18.4 +Version: 0.19.0 Release: 0 %define mod_name pg %define mod_full_name %{mod_name}-%{version} @@ -33,7 +33,7 @@ BuildRequires: postgresql-devel # /MANUAL BuildRoot: %{_tmppath}/%{name}-%{version}-build -BuildRequires: %{rubydevel >= 1.9.3} +BuildRequires: %{rubydevel >= 2.0.0} BuildRequires: %{rubygem gem2rpm} BuildRequires: %{rubygem rdoc > 3.10} BuildRequires: ruby-macros >= 5 @@ -51,7 +51,7 @@ %description Pg is the Ruby interface to the {PostgreSQL RDBMS}[http://www.postgresql.org/]. -It works with {PostgreSQL 8.4 and +It works with {PostgreSQL 9.1 and later}[http://www.postgresql.org/support/versioning/]. A small example usage: #!/usr/bin/env ruby ++++++ pg-0.18.4.gem -> pg-0.19.0.gem ++++++ ++++ 3222 lines of diff (skipped)
