|
Size: 10824
Comment: Added Jessie PHP 5.6.9
|
Size: 7802
Comment: Add Bullseye release info
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 21: | Line 21: |
| This page contains information and links helpful for users and packagers of PHP software in Debian. It also contains any errata for the latest stable release of Debian. It is not meant to supercede documentation provided in the PHP packages, nor is it meant as a general reference for programming in PHP. For those see the [[#moreinfo|Further Information]] section. | This page contains information and links helpful for users and packagers of PHP software in Debian. It also contains any errata for the latest stable release of Debian. It is not meant to supercede documentation provided in the PHP packages, nor is it meant as a general reference for programming in PHP. For those see the [[#Further_Information|Further Information]] section. |
| Line 34: | Line 34: |
| || [[DebianSqueeze|squeeze 6]] || 5.3.3 || || [[DebianWheezy|wheezy 7]] || 5.4.4 || || [[DebianJessie|Jessie 8]] || 5.6.9 || || [[DebianTesting|testing]] || see [[DebianPkg:testing/php5|php 5]] || || [[DebianUnstable|unstable]] || see [[DebianPkg:unstable/php5|php 5]] || |
|| [[DebianSqueeze|Squeeze 6]] || 5.3.3 || || [[DebianWheezy|Wheezy 7]] || 5.4.45 || || [[DebianJessie|Jessie 8]] || [[DebianPkg:jessie/php5|5.6.40]] || || [[DebianStretch|Stretch 9]] || [[DebianPkg:stretch/php7.0|7.0]] || || [[DebianBuster|Buster 10]] || [[DebianPkg:buster/php7.3|7.3]] || || [[DebianBullseye|Bullseye 11]] || [[DebianPkg:bullseye/php7.4|7.4]] || || [[DebianUnstable|unstable]] || [[DebianPkg:unstable/php8.0|8.0]] || |
| Line 40: | Line 42: |
| PHP4 was provided up to [[DebianEtch]] ([[http://archive.debian.net/src:php4|php 4]]). It was removed and replaced by php5 in [[DebianLenny]]. | PHP 4 was provided up to [[DebianEtch]] ([[http://archive.debian.net/src:php4|php 4]]). It was removed and replaced by php5 in [[DebianLenny]]. PHP 7.0 was added in Stretch (php7.0). |
| Line 44: | Line 46: |
| For every N where N is a php major version, a metapackage phpN exists which will require at least one functioning php server engine installed (i.e. libapache2-mod-php5, php5-cgi, etc). Beyond this, there's always: | Up until Debian 8 (Jessie), for every M where M is a php major version, a metapackage phpN exists which will require at least one functioning php server engine installed (i.e. libapache2-mod-php5, php5-cgi, etc). |
| Line 46: | Line 48: |
| {{{apt-cache search php}}} | Since Debian 9 (Stretch), for every M.N where M is a php major version and N is a php minor version, a metapackage php exists which will require a default phpM.N package which will require at least one functioning PHP server engine (i.e. libapache2-mod-php7.0, php7.0-fpm or php7.0-cgi) Beyond this, there's always: {{{ $ apt search php }}} |
| Line 55: | Line 63: |
==== Debian Jessie and below ==== |
|
| Line 65: | Line 75: |
| which for all SAPI's is actually a symlink pointing to a central directory {{{/etc/phpN/conf.d}}}. Any file found in this directory ending in .ini will be treated as a configuration file by the PHP SAPI. |
Any file found in this directory ending in .ini will be treated as a configuration file by the PHP SAPI. |
| Line 69: | Line 78: |
| The rationale with this method is that each SAPI can thus be identically configured with a minimal amount of conffile handling, but at the same time if you want to have SAPI-specific configuration, you can just remove the symlink. |
==== Debian Stretch and up ==== For each major.minor release M.N of PHP (where M is 7 and N is 0, 1, ...), each of the SAPI's (apache2/cgi/fpm/cli/phpdbg/...) have a different central configuration file {{{/etc/php/M.N/$SAPI/php.ini}}} Additionally, each SAPI is configured with the compile-time option {{{ --with-config-file-scan-dir=/etc/php/M.N/$SAPI/conf.d }}} Any file found in this directory ending in .ini will be treated as a configuration file by the PHP SAPI. The environment variable PHP_INI_SCAN_DIR can be set to override the compile-time option. |
| Line 78: | Line 97: |
| The extensions are expected to install their configuration to {{{/etc/php/M.N/mods-available}}} for each M.N tuple the extension has been compiled with and enable the extension as appropriate using {{{/usr/lib/php/php-maintscript-helper}}}. The easiest way how to package PECL extension is to use {{{dh-php}}} package and helpers included within this package. |
|
| Line 81: | Line 104: |
| See also the [[Teams/DebianPHPGroup|php group team]] | |
| Line 84: | Line 107: |
| It's highly recommended that you read README.Debian.security in /usr/share/doc/php*. | It's highly recommended that you read README.Debian.security in /usr/share/doc/php*. |
| Line 89: | Line 112: |
| * issues that require a malicious local user (unless there are compelling reasons otherwise) are ignored. | * issues that require a malicious local user (unless there are compelling reasons otherwise) are ignored. |
| Line 95: | Line 118: |
| As of version 5.2.4-1 the suhosin patch is enabled by default in Debian PHP5 packages. | == Errata == |
| Line 97: | Line 120: |
| == Jessie Testing errata == | === Stretch 9 errata === |
| Line 99: | Line 122: |
| After the release of [[DebianJessie|Jessie]], any miscellaneous information/documentation/errata for the PHP version in Jessie shall be documented here. Note that this ''is not a place for bug reports'', though you should feel free to reference BTS reports if appropriate. | Stretch 9 is now stable. No errata has been logged here for it. |
| Line 101: | Line 124: |
| == Wheezy 7 errata == | === Jessie 8 errata === |
| Line 103: | Line 126: |
| Wheezy 7 is now Stable. No errata has been logged here for it. | Jessie 8 is now oldstable. No errata has been logged here for it. |
| Line 105: | Line 128: |
| == Squeeze 6 errata == | === Wheezy 7 errata === |
| Line 107: | Line 130: |
| Squeeze 6 is now Oldstable within the security support window. No errata has been logged here for it. | Wheezy 7 is now oldoldStable. No errata has been logged here for it. |
| Line 113: | Line 136: |
| == Proposed changes == === New/Better extensions manager === At some point between Sarge and Etch the PHP packages provide a new configuration layout. This new layout makes it easier for extensions to install their configuration files without having to modify the php.ini files. The new extensions manager was first proposed in the [[http://lists.alioth.debian.org/pipermail/pkg-php-maint/2007-May/002549.html|pkg-php-maint]] list in May. This new extensions manager provides a different layout similar to the way Apache/2 (in Debian) handles the sites and modules. The main advantage of this new layout is that an extension can be enabled/disabled on a given SAPI but keep it enabled/disabled on other SAPI's. The new proposed layout looks like: {{{ /etc/php5 /conf.d /bar.ini /foo.ini <------- /cgi | symbolic link to /conf.d | /etc/php5/conf.d/foo.ini /foo.ini - /cli /conf.d /apache2 /conf.d }}} In the above example the foo extension would only be enabled for in the CGI SAPI, rather than being enabled in all SAPI's. In order to manage all the linking two new tools are provided: php5enext and php5disext. Using the same example above, after executing {{{ # php5enext all bar }}} The directories would look like: {{{ /etc/php5 /conf.d /bar.ini <---------- - - /foo.ini <------- | | | /cgi | | | | /conf.d | | | | /foo.ini - | | | /bar.ini ---- | | /cli | | /conf.d | | /bar.ini ------ | /apache2 | /conf.d | /bar.ini -------- }}} Meaning that bar.ini will be parsed by all ''known'' SAPIs (apache2, cgi, cli). ==== Status of the proposition ==== At the moment some work is being done on the ''Debian PHP Maintainers'' [[http://svn.debian.org/wsvn/pkg-php/php5/branches/rg-extension-manager/|SVN repository]]. ==== Responsible of the proposition ==== The person you should contact/blame for this proposition/mess is [[RaphaelGeissert|Raphael Geissert]] (me ;-)). ==== Impact on existing extensions ==== The next extension manager requires the postinst and postrm scripts to be created. Example postinst, shell, script: {{{ # ... # Enable extension on all SAPIs: if [ -x /usr/sbin/php5enext ]; then /usr/sbin/php5enext all FOO quiet nonfatal fi }}} Example postrm, shell, script: {{{ # ... # Disable extension on all SAPIs: if [ -x /usr/sbin/php5disext ]; then /usr/sbin/php5disext all FOO quiet nonfatal fi }}} ==== Upgrading SAPIs to the new layout ==== The new SAPI packages would upgrade their old directory layout to the new one. E.g. from: {{{ /etc/php5 /conf.d <------- /cgi | symbolic link /conf.d ---- }}} To: {{{ /etc/php5 /conf.d /cgi /conf.d // Each SAPI has it's own conf.d directory }}} ==== Upgrading extensions to the new layout ==== At the moment the SAPI packages are upgraded they will remove the $SAPI/conf.d symlink and thus disabling all the extensions. Each, existing, extension will then have to manually '''upgrade''' by calling the php5enext script. In other words: if an extension is not updated to use the new extensions manager it will be disabled on all SAPI's at the moment SAPI's are upgraded. The reason for this is because of a situation where broken symlinks would be kept (see this [[http://lists.alioth.debian.org/pipermail/pkg-php-maint/2007-May/002555.html|message by Steve]]) <<Anchor(moreinfo)>> |
|
| Line 240: | Line 147: |
| CategoryPermalink | CategoryPermalink CategoryProgramming |
Translation(s): none
PHP and Debian
note: this page is a work in progress.
Contents
Overview
From the package description:
PHP is an HTML-embedded scripting language. Much of its syntax is borrowed from C, Java and Perl with a couple of unique PHP-specific features thrown in. The goal of the language is to allow web developers to write dynamically generated pages quickly.
This page contains information and links helpful for users and packagers of PHP software in Debian. It also contains any errata for the latest stable release of Debian. It is not meant to supercede documentation provided in the PHP packages, nor is it meant as a general reference for programming in PHP. For those see the Further Information section.
The first place you should go for information
/usr/share/doc/php*. Most notably, README.Debian and NEWS.Debian, just like any other package. Note that if you are visiting this page while following the directions in that file, abort now because you're in an infinite loop 
How PHP is packaged in Debian
Available versions
Please check the Debian PTS for specific version information.
Release |
PHP version |
5.3.3 |
|
5.4.45 |
|
PHP 4 was provided up to DebianEtch (php 4). It was removed and replaced by php5 in DebianLenny. PHP 7.0 was added in Stretch (php7.0).
Available packages
Up until Debian 8 (Jessie), for every M where M is a php major version, a metapackage phpN exists which will require at least one functioning php server engine installed (i.e. libapache2-mod-php5, php5-cgi, etc).
Since Debian 9 (Stretch), for every M.N where M is a php major version and N is a php minor version, a metapackage php exists which will require a default phpM.N package which will require at least one functioning PHP server engine (i.e. libapache2-mod-php7.0, php7.0-fpm or php7.0-cgi)
Beyond this, there's always:
$ apt search php
...will give you a long list of php related packages. For more specifics on the package naming schemes, you should check the PHP draft policy in Further Information.
Developer access
See PHP/GitUsage.
Configuration layout
Debian Jessie and below
For each major release N of PHP (where N is 4 or 5), each of the 4 SAPI's (apache/apache2/cgi/cli) have a different central configuration file /etc/phpN/$SAPI/php.ini.
Additionally, each SAPI is configured with the compile-time option
--with-config-file-scan-dir=/etc/phpN/$SAPI/conf.d
Any file found in this directory ending in .ini will be treated as a configuration file by the PHP SAPI.
Debian Stretch and up
For each major.minor release M.N of PHP (where M is 7 and N is 0, 1, ...), each of the SAPI's (apache2/cgi/fpm/cli/phpdbg/...) have a different central configuration file /etc/php/M.N/$SAPI/php.ini
Additionally, each SAPI is configured with the compile-time option
--with-config-file-scan-dir=/etc/php/M.N/$SAPI/conf.d
Any file found in this directory ending in .ini will be treated as a configuration file by the PHP SAPI.
The environment variable PHP_INI_SCAN_DIR can be set to override the compile-time option.
For packagers of PHP applications/modules/libraries
You should consider taking a look at the PHP draft policy. There's also a mailing list for web applications packagers, debian-webapps@lists.debian.org . While the list is technically for webapp packaging-related issues, you should feel welcome to post purely PHP-packaging-related questions as well, as there is a significant overlap in the audience and you're more likely to get a response from here than from mailing the PHP packagers.
The extensions are expected to install their configuration to /etc/php/M.N/mods-available for each M.N tuple the extension has been compiled with and enable the extension as appropriate using /usr/lib/php/php-maintscript-helper.
The easiest way how to package PECL extension is to use dh-php package and helpers included within this package.
For those interested in helping with PHP in Debian
The first thing you should do is send an email to the Debian PHP maintainer's list, pkg-php-maint@lists.alioth.debian.org. Help is often needed and always appreciated. See also the php group team
Notes on PHP and security
It's highly recommended that you read README.Debian.security in /usr/share/doc/php*.
In short, security support for PHP places a high load on the package maintainers, because of the volume of security-related issues and the difficulty of working with the upstream authors in finding the fixes. As such, PHP security issues are typically triaged with different priorities based on the particulars of the issue.
- issues involving features that are broken as designed (safe mode, register globals, etc) are completely ignored
- issues that require a malicious local user (unless there are compelling reasons otherwise) are ignored.
- issues involving unsafe application usage (applications not filtering input before passing to certain functions) are usually given a low priority or sometimes even ignored in favor of reporting bugs against the offending applications
- issues involving remote code execution (buffer overflows, code inclusion, etc) are given the highest priority
The Debian PHP maintainers work fairly closely with the Debian security (esp. secure-testing) teams, as well as the Ubuntu PHP maintainers, so you can be generally assured that properly reported bugs tagged as security-relevant will be handled as promptly and transparently as possible.
Errata
Stretch 9 errata
Stretch 9 is now stable. No errata has been logged here for it.
Jessie 8 errata
Jessie 8 is now oldstable. No errata has been logged here for it.
Wheezy 7 errata
Wheezy 7 is now oldoldStable. No errata has been logged here for it.
Notes on Floating Point Rounding
See PHP/Rounding for some discussion of why floating point rounding does not behave as expected.
Further Information
- /usr/share/doc/php*
php-security.org, authors of hardened php and frequent auditors of php's security.
Debian PHP maintainer's list: pkg-php-maint@lists.alioth.debian.org (Browse the list)
Debian webapps mailing list: debian-webapps@lists.debian.org (Browse the list)