Hello community, here is the log from the commit of package rubygem-puma for openSUSE:Factory checked in at 2017-09-13 22:35:00 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/rubygem-puma (Old) and /work/SRC/openSUSE:Factory/.rubygem-puma.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "rubygem-puma" Wed Sep 13 22:35:00 2017 rev:27 rq:523500 version:3.10.0 Changes: -------- --- /work/SRC/openSUSE:Factory/rubygem-puma/rubygem-puma.changes 2017-07-11 08:25:18.587980053 +0200 +++ /work/SRC/openSUSE:Factory/.rubygem-puma.new/rubygem-puma.changes 2017-09-13 22:36:08.286590475 +0200 @@ -1,0 +2,35 @@ +Mon Sep 11 12:47:58 UTC 2017 - [email protected] + +- updated to version 3.10.0 + see installed History.md + + ## 3.10.0 / 2017-08-17 + + * 3 features: + * The status server has a new /gc and /gc-status command. (#1384) + * The persistent and first data timeouts are now configurable (#1111) + * Implemented RFC 2324 (#1392) + + * 12 bugfixes: + * Not really a Puma bug, but @NickolasVashchenko created a gem to workaround a Ruby bug that some users of Puma may be experiencing. See README for more. (#1347) + * Fix hangups with SSL and persistent connections. (#1334) + * Fix Rails double-binding to a port (#1383) + * Fix incorrect thread names (#1368) + * Fix issues with /etc/hosts and JRuby where localhost addresses were not correct. (#1318) + * Fix compatibility with RUBYOPT="--enable-frozen-string-literal" (#1376) + * Fixed some compiler warnings (#1388) + * We actually run the integration tests in CI now (#1390) + * No longer shipping unnecessary directories in the gemfile (#1391) + * If RUBYOPT is nil, we no longer blow up on restart. (#1385) + * Correct response to SIGINT (#1377) + * Proper exit code returned when we receive a TERM signal (#1337) + + * 3 refactors: + * Various test improvements from @grosser + * Rubocop (#1325) + * Hoe has been removed (#1395) + + * 1 known issue: + * Socket activation doesn't work in JRuby. Their fault, not ours. (#1367) + +------------------------------------------------------------------- Old: ---- puma-3.9.1.gem New: ---- puma-3.10.0.gem ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ rubygem-puma.spec ++++++ --- /var/tmp/diff_new_pack.VW2NwN/_old 2017-09-13 22:36:10.098335383 +0200 +++ /var/tmp/diff_new_pack.VW2NwN/_new 2017-09-13 22:36:10.102334820 +0200 @@ -24,7 +24,7 @@ # Name: rubygem-puma -Version: 3.9.1 +Version: 3.10.0 Release: 0 %define mod_name puma %define mod_full_name %{mod_name}-%{version} @@ -34,7 +34,6 @@ BuildRoot: %{_tmppath}/%{name}-%{version}-build BuildRequires: %{rubydevel >= 1.9.3} BuildRequires: %{rubygem gem2rpm} -BuildRequires: %{rubygem rdoc > 3.10} BuildRequires: ruby-macros >= 5 BuildRequires: update-alternatives Url: http://puma.io @@ -49,9 +48,9 @@ %description Puma is a simple, fast, threaded, and highly concurrent HTTP 1.1 server for Ruby/Rack applications. Puma is intended for use in both development and -production environments. In order to get the best throughput, it is highly -recommended that you use a Ruby implementation with real threads like -Rubinius or JRuby. +production environments. It's great for highly concurrent Ruby implementations +such as Rubinius and JRuby as well as as providing process worker support to +support CRuby well. %prep ++++++ puma-3.9.1.gem -> puma-3.10.0.gem ++++++ ++++ 2772 lines of diff (skipped)
