Changelog for rubygem-passenger-doc-3.0.8-2.22.x86_64.rpm :

* Mon Aug 22 2011 mrueckertAATTsuse.de- update to version 3.0.8
* [Nginx] Upgraded preferred Nginx version to 1.0.5.
* [Nginx] Fixed various compilation problems on various platforms.
* [Nginx] We now ensure that SERVER_NAME is equal to HTTP_HOST without the port part. This is needed for Rack compliance. By default Nginx sets SERVER_NAME to whatever is specified in the server_name directive, but that\'s not necessarily the correct value. This fixes, for example, the use of the \'map\' statement in config.ru.
* [Nginx] Added the options passenger_buffer_size, passenger_buffers and passenger_busy_buffers_size. These options are similar to proxy_module\'s similarly named options. You can use these to e.g. increase the maximum header size limit.
* [Nginx] passenger_pre_start now supports virtual hosts that listen on Unix domain sockets.
* [Apache] Fixed the pcre.h compilation problem.
* [Standalone] Fixed \'passenger stop\'. It didn\'t work properly because it kept waiting for \'tail\' to exit. We now properly terminate \'tail\' as well.
* Fixed compatibility with Rake 0.9.
* Fixed various Ruby 1.9 compatibility issues.
* Various documentation improvements.
* New Union Station filter language features. It now supports status codes and response times. Please refer to https://engage.unionstationapp.com/help#filtering for more information.
* Mon Aug 22 2011 mrueckertAATTsuse.de- make sure the passenger root variable always points to the passenger version in the package. To achieve that we introduce a (mod_)passenger_root.include file which will be included from the old (mod_)passenger.conf. the new file is not marked as config(noreplace) and will be overwritten by the package.
* Mon Aug 22 2011 adrianAATTsuse.de- update to version 3.0.8
* [Nginx] Upgraded preferred Nginx version to 1.0.5.
* [Nginx] Fixed various compilation problems on various platforms.
* [Nginx] We now ensure that SERVER_NAME is equal to HTTP_HOST without the port part. This is needed for Rack compliance. By default Nginx sets SERVER_NAME to whatever is specified in the server_name directive, but that\'s not necessarily the correct value. This fixes, for example, the use of the \'map\' statement in config.ru.
* [Nginx] Added the options passenger_buffer_size, passenger_buffers and passenger_busy_buffers_size. These options are similar to proxy_module\'s similarly named options. You can use these to e.g. increase the maximum header size limit.
* [Nginx] passenger_pre_start now supports virtual hosts that listen on Unix domain sockets.
* [Apache] Fixed the pcre.h compilation problem.
* [Standalone] Fixed \'passenger stop\'. It didn\'t work properly because it kept waiting for \'tail\' to exit. We now properly terminate \'tail\' as well.
* Fixed compatibility with Rake 0.9.
* Fixed various Ruby 1.9 compatibility issues.
* Various documentation improvements.
* New Union Station filter language features. It now supports status codes and response times. Please refer to https://engage.unionstationapp.com/help#filtering for more information.- use official source tar ball now and build the gem to install
* Tue Aug 16 2011 mrueckertAATTsuse.de- buildrequire rubygem-rack-1_3 to fix the have choice problem- use the mod_full_name macro
* Wed Jun 08 2011 ammlerAATTopenttdcoop.org- add config template to -nginx subpackage
* Mon May 02 2011 mrueckertAATTsuse.de- require nginx in the -nginx subpackage
* Sun Apr 24 2011 mrueckertAATTsuse.de- fix build on devel_languages_ruby_SLE_10 use curl-devel for anything older than sle11/11.1
* Wed Apr 20 2011 adrianAATTsuse.de- add support for mod_xforward
* Thu Apr 14 2011 mrueckertAATTsuse.de- switch to use system libev
* Thu Apr 14 2011 mrueckertAATTsuse.de- update to version 3.0.7
* Upgraded preferred Nginx version to 1.0.0.
* Phusion Passenger Standalone now pre-starts application processes at startup instead of doing that at the first request.
* When sending data to Union Station, the HTTP status code is now also logged.
* Various Union Station-related stability improvements.
* The Linux OOM killer was previously erroneously disabled for all Phusion Passenger processes, including application processes. The intention was to only disable it for the Watchdog. This has been fixed, and the Watchdog is now the only process for which the OOM killer is disabled.
* Due to a typo, the dependency on file-tail was not entirely removed in 3.0.6. This has now been fixed.- fixed cleaning up the ext tree
* Tue Apr 12 2011 mrueckertAATTsuse.de- split out a devel-static package containing the 2 static libraries that you need to compile nginx with passenger support later. that saves us recompiling them in the nginx build.- clean up file lists
* Tue Apr 12 2011 mrueckertAATTsuse.de- update to version 3.0.6
* Fixed various Union Station-related stability issues.
* Fixed an issue with host name detection on certain platforms.
* Improved error logging in various parts.
* The dependency on the file-tail library has been removed.
* During installation, check whether /tmp is mounted with \'noexec\'. Phusion Passenger\'s installer relies on /tmp
*not
* being mounted with \'noexec\'. If it is then the installer will now show a helpful error message instead of bailing out in a confusing manner. Users can now tell the installer to use a different directory for storing temporary files by customizing the $TMPDIR environment variable.
* Phusion Passenger Standalone can now run Rackup files that are not named \'config.ru\'. The filename can be passed through the command line using the -R option.- additional changes from 3.0.5
* [Apache] Fixed Union Station process statistics collection Union Station users that are using Apache may notice that no process information show up in Union Station. This is because of a bug in Phusion Passenger\'s Apache version, which has now been fixed.
* [Apache] PassengerAnalytics has been renamed to UnionStationSupport This option has been renamed for consistency reasons.
* [Nginx] passenger_analytics has been renamed to union_station_support This option has been renamed for consistency reasons.
* Fixed Union Station data sending on older libcurl versions Some Union Station users have reported that their data don\'t show up. Upon investigation this turned out to be a compatibility with older libcurl versions. Affected systems include all RHEL 5 based systems, such as RHEL 5.5 and CentOS 5.5. We\'ve now fixed compatibility with older libcurl versions.
* Added support for the Union Station filter language This language can be used to limit the kind of data that\'s sent to Union Station. Please read https://engage.unionstationapp.com/help#filtering for details.
* Fixed a PassengerMaxPoolSize/passenger_max_pool_size violation bug People who host a lot of different applications on Phusion Passenger may notice that it sometimes spawns more processes than is allowed by PassengerMaxPoolSize/passenger_max_pool_size. This has been fixed.- additional changes from 3.0.4
* [Apache] Changed mod_dir workaround hook priority Phusion Passenger temporarily disables mod_dir on all Phusion Passenger-handled requests in order to avoid conflicts. In order to do this it registers some Apache hooks with the APR_HOOK_MIDDLE priority, but it turned out that this breaks some other modules like mod_python. The hook priority has been changed to APR_HOOK_LAST to match mod_dir\'s hook priorities. Issue reported by Jay Freeman.
* Added support for Union Station: http://www.unionstationapp.com/
* Some error messages have been improved.
* Fri Feb 25 2011 mrueckertAATTsuse.de- update to version 3.0.3
* [Nginx] Preferred Nginx version upgraded to 0.8.54 The previous preferred version was 0.8.53.
* PATH_INFO and REQUEST_URI now contain the original escaped URI Phusion Passenger passes the URI, as reported by Apache/Nginx, to application processes through the PATH_INFO and REQUEST_URI variables. These variables are supposed to contain the original, unescaped URI, e.g. /clubs/%C3%BC. Both Apache and Nginx thought that it would be a good idea to unescape the URI before passing it to modules like Phusion Passenger, thereby causing PATH_INFO and REQUEST_URI to contain the unescaped URI, e.g. /clubs/ü. This causes all sorts of encoding problems. We now manually re-escape the URI when setting PATH_INFO and REQUEST_URI. Issue #404.
* The installer no longer detects directories as potential commands Previously the installer would look in $PATH for everything that\'s executable, including directories. If one has /usr/lib in $PATH and a directory /usr/lib/gcc exists then the installer would recognize /usr/lib/gcc as the compiler. We now explicitly check whether the item is also a file.
* PseudoIO now responds to #to_io Phusion Passenger sets STDERR to a PseudoIO object in order to capture anything written to STDERR during application startup. This breaks some libraries which expect STDERR to respond to [#]to_io. This has now been fixed. Issue #607.
* Fixed various other minor bugs See the git commit log for details.- splitted out testsuite and documentation
* Thu Jan 20 2011 mrueckertAATTsuse.de- moved apache2 requires to the apache2 subpackage
* Thu Jan 13 2011 chrisAATTcomputersalat.de- fix spec o Group field must be present in package: rubygem-passenger-nginx
* Thu Jan 13 2011 schubiAATTnovell.com- Spit packages into - - rubygem-passenger - - rubygem-passenger-nginx - - rubygem-passenger-apache2
* Tue Dec 21 2010 chrisAATTcomputersalat.de- update to version 3.0.2
* [Nginx] Fix crash if passenger_root refers to a nonexistant directory.
* Fixed file descriptor closing issues on FreeBSD: issue #597.
* Fix the fakeroot task. Issue #592
* Update NEWS.
* Fix Nginx configure script: it didn\'t correctly change back the orginal working directory after compilation.
* NetBSD doesn\'t support llroundl() so work around it by using llround(). Issue #593.
* Fix compilation warning on NetBSD: issue #593.
* Fix use of fcntl(.., F_CLOSEM)
* Merge branch \'master\' into debian
* Add support to EventedClient for only closing the writer half of the connection.
* Add StaticString.find(substring) ... and lot more
* Tue Dec 07 2010 mrueckertAATTsuse.de- update to version 3.0.1
* Fixed malfunction after web server restart On Linux systems that have a non-standard filesystem on /tmp, Phusion Passenger could malfunction after restarting the web server because of a bug that\'s only triggered on certain filesystems. Issue #569.
* Boost upgraded to version 1.44.0. We were on 1.42.0.
* Much improved startup error messages Phusion Passenger performs many extensive checks during startup to ensure integrity. However the error message in some situation could be vague. These startup error messages have now been improved dramatically, so that if something goes wrong during startup you will now more likely know why.
* Curl < 7.12.1 is now supported The previous version fails to compile with Curl versions earlier than 7.12.1. Issue #556.
* passenger-make-enterprisey fixed This is the command that people can run after donating. It allows people to slightly modify Phusion Passenger\'s display name as a joke. In 3.0.0 it was broken because of a typo. This has been fixed.
* Removed passenger-stress-test This tool was used during the early life of Phusion Passenger for stress testing websites. Its performance has never been very good and there are much better tools for stress testing, so this tool has now been removed.
* [Apache] RailsEnv and RackEnv configuration options are now equivalent In previous versions, RailsEnv only had effect on Rails 1 and Rails 2 apps while RackEnv only had effect on Rack apps. Because Rails 3 apps are considered Rack apps, setting RailsEnv had no effect on Rails 3 apps. Because this is confusing to users, we\'ve now made RailsEnv and RackEnv equivalent. Issue #579.
* [Nginx] Fixed compilation problems on systems with unpowerful shells Most notably Solaris. Its default shell does not support some basic constructs that we used in the Nginx configure script.
* [Nginx] Upgraded default Nginx version to to 0.8.53 The previous default was 0.8.52.
* [Nginx] passenger_enabled now only accepts \'on\' or \'off\' values Previously it would recognize any value not equal to \'on\' as meaning \'off\'. This caused confusion among users who thought they could also specify \'true\', so we now throw a proper error if the value is unrecognized. Fixes issue #583.- cleaned up spec file- move passenger_native_support from ext to lib dir (bnc#657964)
* Thu Oct 28 2010 mrueckertAATTsuse.de- update to version 3.0.0 This is a major release with many changes. Please read our blog for details. http://blog.phusion.nl/2010/10/18/phusion-passenger-3-0-0-final-released/- new dependencies: rubygem-daemon_controller rubygem-file-tail libcurl
* Fri Jul 09 2010 mrueckertAATTsuse.de- mark mod_passenger.conf config(noreplace)
* Fri Jun 25 2010 mrueckertAATTsuse.de- update to version 2.2.15 - [Apache] Fixed incorrect temp dir cleanup by passenger-status On some systems, running passenger-status could print the following message: \"
*
*
* Cleaning stale folder /tmp/passenger.1234\" ...after which Phusion Passenger breaks because that directory is necessary for it to function properly. The cause of this problem has been found and has been fixed. - [Apache] Fixed some upload handling problems Previous versions of Phusion Passenger check whether the size of the received upload data matches the contents of the Content-Length header as received by the client. It turns out that there could be a mismatch e.g. because of mod_deflate input compression, so we can\'t trust Content-Length anyway and we\'re being too strict. The check has now been removed. - [Nginx] Fixed compilation issues with Nginx >= 0.7.66 Thanks to Potamianos Gregory for reporting this issue. Issue #500. - [Nginx] Default Nginx version changed to 0.7.67 The previous default version was 0.7.65. - Fixed more Bundler problems Previous versions of Phusion Passenger would preload some popular libraries such as mysql and sqlite3 in order to utilize copy-on-write optimizations better. However this behavior conflicts with Bundler so we\'ve removed it.
* Mon Jun 14 2010 mrueckertAATTsuse.de- update to version 2.2.14
* Added support for Rubinius Patch contributed by Evan Phoenix.
* Fixed a mistake in the SIGQUIT backtrace message. Patch contributed by Christoffer Sawicki.
* [Nginx] Fix a localtime() crash on FreeBSD This was caused by insufficient stack space for threads. Issue #499.- additional changes from version 2.2.13
* Fixed some Rails 3 compatibility issues that were recently introduced.
* Fixed a typo that causes config/setup_load_paths.rb not to be loaded correctly.- additional changes from version 2.2.12
* Improved Bundler support. Previous versions might not be able to correctly load gems bundled by Bundler. We\'ve also documented how our Bundler support works and how to override our support if you need special behavior. Please refer to the Phusion Passenger Users Guide, section \"Bundler support\".
* Worked around some user account handling bugs in Ruby. Issue #192.
* Fixed some Ruby 1.9 tempfile.rb compatibility problems.
* Fixed some compilation problems on some ARM Linux platforms.
* [Apache] Suppress bogus mod_xsendfile-related error messages. When mod_xsendfile is being used, Phusion Passenger might print bogus error messages like \"EPIPE\" or \"Apache stopped forwarding the backend\'s response\" to the log file. These messages are normal, are harmless and can be safely ignored, but they pollute the log file. So in this release we\'ve added code to suppress these messages when mod_xsendfile is being used. Issue #474.
* [Nginx] Fixed \"passenger_user_switching off\" permission problems If Nginx is running as root and passenger_user_switching is turned off, then Phusion Passenger would fail to initialize because of a permission problem. This has been fixed. Issue #458.
* [Nginx] Nginx >= 0.8.38 is now supported. Thanks to Sergey A. Osokin for reporting the problem.
* [Nginx] passenger-install-nginx-module upgraded It now defaults to installing Nginx 0.7.65 instead of 0.7.64.
* Fri Jun 11 2010 mrueckertAATTsuse.de- use rubygems_requires macro
* Tue Mar 16 2010 chrisAATTcomputersalat.de- update to version 2.2.11
* This release fixes a regression that appeared in 2.2.10 which only affects Apache. When under high load, Apache might freeze and stop responding to requests. It is caused by a race conditions which is why it escaped our last release testing.- fix initializer problem o do not install ApplicationPoolServerExecutable to /usr/lib/phusion_passenger leave at origin place and set correct AATTPassengerRootAATT in mod_passenger.conf
* Thu Feb 25 2010 mrueckertAATTsuse.de- update to version 2.2.10
* Fixed some Bundler compatibility problems.
* Fixed some file descriptor passing problems, which previously could lead to mysterious crashes.
* Fixed some compilation problems on newer GCC versions. Issue #430.
* Support #size method in rack.input.- for changes from 2.2.8 and 2.2.9 see /usr/lib
*/ruby/gems/1.8/gems/passenger-2.2.10/NEWS
* Wed Dec 02 2009 chrisAATTcomputersalat.de- update to version 2.2.7
* Removed forgotten debugging code in passenger-install-apache2-module, which caused it not to compile anything.- additional changes from 2.2.6
* Some /tmp cleaner programs such as tmpwatch try to remove subdirectories in /tmp/passenger.xxx after a while because they think those subdirectories are unused. This could cause Phusion Passenger to malfunction, requiring a web server restart. Measures have now been taken to prevent those tmp cleaner programs from removing anything in /tmp/passenger.xxx. Issue #365.
* When autodetecting the application type, Rack is now given more priority than Rails. This allows one to drop a config.ru file in a Rails directory and have it detected as a Rack application instead of a Rails application. Patch contributed by Sam Pohlenz: issue #338.
* The default socket backlog has been increased from \'SOMAXCONN\' (which is 128 on most platforms) to 1024. This should fix most \'helper_server.sock failed: Resource temporarily unavailable\' errors.
* Fixed compilation problems on Solaris. Issue #369 and issue #379.
* Fixed crashes on PowerPC.
* Some Ruby 1.9 compatibility fixes. Issue #398.
* The installer now displays correct dependency installation instructions for Mandriva Linux.
* [Apache] The location of the \'apxs\' and \'apr-config\' commands can now also be passed to the installer through the --apxs-path and --apr-config-path parameters, in addition to the $APXS2 and $APR_CONFIG environment variables. Issue #3.
* [Nginx] Various problems that only occur on 64-bit platforms have been fixed.
* [Nginx] The installer now installs Nginx 0.7.64 by default.- fix Passenger could not be initialized o \'/usr/lib/phusion_passenger/ApplicationPoolServerExecutable\'
* Fri Oct 16 2009 mrueckertAATTsuse.de- update to version 2.2.5 see /usr/lib
*/ruby/gems/1.8/gems/passenger-2.2.5/NEWS
* Thu Mar 26 2009 mrueckertAATTsuse.de- update to version 2.1.2 - Support for Rails 2.3 - Improved compatibility with other Apache modules, such as mod_rewrite - Ruby 1.9 support - Support for NFS setups - Various I/O handling and scaling improvements and fixes - Ability to disable Phusion Passenger for arbitrary URLs (PassengerEnabled option) - Improved application compatibility - Improved command-line admin tools - Ability to display backtraces for all threads - Improved security - More customization options for exotic systems/setups - Various usability improvements - In particular, many error messages have been improved so that end users don’t have to stare at the screen for minutes wondering what the computer is trying to tell them. There are also many small usability improvements here and there. - Various other minor improvements and bug fixes - PassengerPoolIdleTime can now be set to 0, which means that the backend application must never idle timeout. This feature has been contributed by redmar. - The passenger-status tool will now display Phusion Passenger’s own backtraces for C++ code, in order to make it possible to detect potential freezes in C++ code. - Phusion Passenger error pages now return HTTP 500 errors, as they should. - The ApplicationSpawner server and FrameworkSpawner server idle times can now be customized. - In the 2.0.x series, sometimes more backend processes might be spawned than is allowed by the ‘PassengerMaxPoolSize’ option. This has been fixed.