From comand at blastwave.org Fri Oct 21 20:33:29 2005 From: comand at blastwave.org (Cory Omand) Date: Fri, 21 Oct 2005 11:33:29 -0700 Subject: [csw-announce] ANNOUNCE: PHP 5.0.5 Message-ID: <43593479.8060108@blastwave.org> Packages are now available for PHP 5.0.5, including modules for Apache 1.3.x and Apache 2.0.x. Two important notes about this package set: o The ap2_modphp5 module has a direct dependency on the ap2_prefork MPM module. If you choose to run ap2_modphp5 with the ap2_worker MPM module, you do so at your own risk. If any scripts and/or modules running in such a configuration call code which is not thread safe (e.g. calling into a non-standard extension installed locally via PEAR), Bad Stuff may happen. This will likely result in the Apache child segfaulting, but effects may be more severe. If you want to run ap2_modphp5 in production, it is strongly advised to use it with ap2_prefork. o PHP extensions which have unique dependencies are packaged separately. Each of these extension packages enable and disable the modules by editing php.ini when the package is installed or removed. Note that by default, php.ini is used by all of the available SAPIs, including apache, apache2, and CLI. It is possible to create a separate copy of php.ini for each of the SAPIs -- e.g. php-apache.ini, php-cli.ini (See http://www.php.net/manual/en/configuration.php for details). If this layout is chosen, adding and removing php5_* extension packages will only update php.ini, they will *not* enable/disable modules in any SAPI-specific php.ini files. -- Cory Omand From comand at blastwave.org Mon Oct 31 23:04:31 2005 From: comand at blastwave.org (Cory Omand) Date: Mon, 31 Oct 2005 14:04:31 -0800 Subject: [csw-announce] ANNOUNCE: apache2 2.0.55 Message-ID: <436694EF.5090909@blastwave.org> Happy Halloween! New packages for apache2 version 2.0.55 are now available in unstable. The 2.0.55 is primarily a bug and security fix revision. See the list of fixes in this version at: http://www.apache.org/dist/httpd/CHANGES_2.0.55 The Blastwave apache2 packages include a number of bug fixes. Some of the bugs that are present in the current package set will likely cause issues during upgrade. On package removal, the incorrect directory is passed to the 'chroot' utility in preremove scripts for ap2_suexec, ap2_modperl, and ap2_modpython. This causes the following message to be output before files are removed: chroot("/opt/csw/apache2/sbin/apxs"): Not a directory The message is harmless, however, the module will not be disabled in httpd.conf. This will cause ap2_prefork (or ap2_worker) to be unable to properly shut down httpd in the preremove script, giving an error message indicating that the server is unable to load a loadable module (e.g. mod_suexec.so). For this upgrade, it is best to remove the existing packages manually, then install the new packages using pkg-get, rather than using the pkg-get automated upgrade mode. The proper order for removing apache2 is: CSWap2_suexec CSWapache2 CSWap2_prefork (or CSWap2_worker) CSWapache2c CSWapache2rt It is not necessary to remove modules which were installed on top of apache2 (e.g. ap2_subversion). However, the same bug which affects removal of packages like ap2_suexec also affects ap2_modperl and ap2_modpython. Updates for both of these packages are also available in unstable. During removal of the above packages, ignore any errors. After removal is complete, ensure that apache2 httpd is not running, then re-install apache2. -- Cory Omand From comand at blastwave.org Fri Oct 21 20:33:29 2005 From: comand at blastwave.org (Cory Omand) Date: Fri, 21 Oct 2005 11:33:29 -0700 Subject: [csw-announce] ANNOUNCE: PHP 5.0.5 Message-ID: <43593479.8060108@blastwave.org> Packages are now available for PHP 5.0.5, including modules for Apache 1.3.x and Apache 2.0.x. Two important notes about this package set: o The ap2_modphp5 module has a direct dependency on the ap2_prefork MPM module. If you choose to run ap2_modphp5 with the ap2_worker MPM module, you do so at your own risk. If any scripts and/or modules running in such a configuration call code which is not thread safe (e.g. calling into a non-standard extension installed locally via PEAR), Bad Stuff may happen. This will likely result in the Apache child segfaulting, but effects may be more severe. If you want to run ap2_modphp5 in production, it is strongly advised to use it with ap2_prefork. o PHP extensions which have unique dependencies are packaged separately. Each of these extension packages enable and disable the modules by editing php.ini when the package is installed or removed. Note that by default, php.ini is used by all of the available SAPIs, including apache, apache2, and CLI. It is possible to create a separate copy of php.ini for each of the SAPIs -- e.g. php-apache.ini, php-cli.ini (See http://www.php.net/manual/en/configuration.php for details). If this layout is chosen, adding and removing php5_* extension packages will only update php.ini, they will *not* enable/disable modules in any SAPI-specific php.ini files. -- Cory Omand From comand at blastwave.org Mon Oct 31 23:04:31 2005 From: comand at blastwave.org (Cory Omand) Date: Mon, 31 Oct 2005 14:04:31 -0800 Subject: [csw-announce] ANNOUNCE: apache2 2.0.55 Message-ID: <436694EF.5090909@blastwave.org> Happy Halloween! New packages for apache2 version 2.0.55 are now available in unstable. The 2.0.55 is primarily a bug and security fix revision. See the list of fixes in this version at: http://www.apache.org/dist/httpd/CHANGES_2.0.55 The Blastwave apache2 packages include a number of bug fixes. Some of the bugs that are present in the current package set will likely cause issues during upgrade. On package removal, the incorrect directory is passed to the 'chroot' utility in preremove scripts for ap2_suexec, ap2_modperl, and ap2_modpython. This causes the following message to be output before files are removed: chroot("/opt/csw/apache2/sbin/apxs"): Not a directory The message is harmless, however, the module will not be disabled in httpd.conf. This will cause ap2_prefork (or ap2_worker) to be unable to properly shut down httpd in the preremove script, giving an error message indicating that the server is unable to load a loadable module (e.g. mod_suexec.so). For this upgrade, it is best to remove the existing packages manually, then install the new packages using pkg-get, rather than using the pkg-get automated upgrade mode. The proper order for removing apache2 is: CSWap2_suexec CSWapache2 CSWap2_prefork (or CSWap2_worker) CSWapache2c CSWapache2rt It is not necessary to remove modules which were installed on top of apache2 (e.g. ap2_subversion). However, the same bug which affects removal of packages like ap2_suexec also affects ap2_modperl and ap2_modpython. Updates for both of these packages are also available in unstable. During removal of the above packages, ignore any errors. After removal is complete, ensure that apache2 httpd is not running, then re-install apache2. -- Cory Omand