Bug#821631: php-validate: PHP 7.0 Transition
Package: php-validate Version: 0.8.5-4 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-validate package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-validate -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrMXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHQj8P/RjOexTxnmtn8FInlo3b1R2V 5D0gSzRkE/vaf8F4YLAfyHFSigOFTdqji+dGaV3oqSRsVOoZWm0qqBqiTjcfHORD OPQ5v37/Qrivhj7pTxluNGotPPtiE31lhT0ta+nxmWbYBDbJdBjbXA6vh1JLc+AS SSCAJye1EihRCI0HUujESQI9GmSEHj7kf54UaWaYRoM0PH9DfYrexcvJfyDgleZJ vwpQWrE4Ck8pw+gzNZVwVYpxQDvlRujBHwwE53hqwRktjfxKqftPa5qhDduBKcD5 tHxqPIqBW86UJEawsW6XHhYmXtfVljZz/QBd+kvnURs14XgBs5b82tSq6Ev/dcHC 3BPi91QmveLICIYx99/n3mEG8XXsGRE5mCon3tf/HCXq/YxMn2g4M4EXM4Wbt4gf ozItBOdhQAJoULzu4b7EdckASIF8JJBp1MmMiInUMBB1awyWkBBclwyfbHajoE0U MWMJ80lD03ZXTNSlOtTHjf3OG6dnv1k3mVF0TIXigxSQ5z9LV9c9aGcoeyNhPLfW INIvctFcxlTssguRYXlgexYed7D4VJxB1ZlJFPm7U1VgDenWdeNqturFS1++r36e gKHudgmvFnCg8s6QMJ5C1ECiomvrjA6uWeyIf9VxL9UHuA8Gt+sdkyYTtFZQHcJu TcvQwp/XKM++lIT/2XK+ =HDmV -END PGP SIGNATURE-
Bug#821550: php5-mongo: PHP 7.0 Transition
Package: php5-mongo Version: 1.6.10-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php5-mongo package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php5-mongo -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqQXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHw7sQAIrBPgy7h5D1sfMKcbKJ9Kp1 rVr2uKBgf94ixHVIAmGu38IqKs24Xttawe8RMevKxagj3LSHprMqSXANJ/wdemuP L8YUCk20HqKZSjOepC9BiA1LAfzl0sGGXErWRTU7qaT9c948szFpTZndIK7cujM1 ie5bEZCeH+Sj3cIQfaNbRJpmeJ+4PXN+SaTzHfDPJka3b90IiiGlMQPe7nUFS3zf mRILZcIt3s2Pbt0PoiJPhHLRbZECUqMCYmWknFqwMg/COkZbT5v/VVkgrqUDzje1 IciZMMDG0qhsx0bLRgxFe6MEFbb6lp2O8olZqKksCG1zbuBKxzS8r4GTlf6pQEqd R/wTjyt7xetPxhNlX6rzKgW3nakWmbEDpxiNHj2ft70TJJUA7SbYvo/KWO9SH1/3 /wRgtWE02ouxFqfBuRI1omD88VL5sMu3jox/QMefdpkimXuY9+MKv7+p+hbSCmh0 3x4PsyUKlY++ZvX0M5d9de4imqZGNd+75PZ7V1wTyS9cZvhPKDYz7S7BPtXyw3BR xVc/5Ug9BxN0jVHUxQ/4+Q8lKA5L430cs9zzywiBkOfSHMqpsDqJuKwMX2JbGFJV cR/rePsLFaYb9WXQ5nOudmDo6SlPpfyfiu7pAhRyItvAaEcj3xaS+jUkrobDMcdp pcFPHn3Eu0+rdEOjto1Y =Spqw -END PGP SIGNATURE-
Bug#821559: php5-symfony-debug: PHP 7.0 Transition
Package: php5-symfony-debug Version: 2.8.4+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php5-symfony-debug package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php5-symfony-debug -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqXXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH8JsP/155kpZeAMhE88m6o0jZb5C1 Gjlpxu4f4J8k44lu6bX9dmw20Uf0RUaaw5QPMMiSD4cI4nI0gmbhuNJLCrju1qJn I5gzagFFcZQJkQxBbSyqXwHPcTsK+vC4C+t+ziI/DOKtpQ6MgrvT3YKUrtbnIALb sksvaHkt+a4WgAnkiovduPIKFWf3SjMvNn2+mvop0DSpJPS7lbsQu9eIYsWRCccr 9V2lNWjVVlyFjVJq1qVgnXtK6rY8mmFml6f4qfB3Fkhqhzce9G+10yTItcH6iFKu VzapLZ/omWVEycbSvzUwoAtnfY084RfQp5MgpnRB+zOUmPW4SR/os4jl/dFLtM6k 3WpoH5jFe9XyIBXemW8+41jsaeo5Jz2lIFV8IryLSPCpda06llqK9EbtvBBdQi7g FsDtQPhPAU4Si0nDNEh+0M3Fe1dLQ9V9i4uHopTB9K+dgvu9+SAdpPp/nfdv2qkQ zI8Pj75vLPRS5zIfMH4iP5g89hioCBMayZ/LdM+csp5Ud2pZxlq/UPan8rwJFvYq nj/8uryLVqgCzt1YLulgnXm7nIBGgARot6D8ht5lwvtlKxpFGQ4S91K7BE66LTF6 JlhrgjoUCynw3wmAInB4QKMifVVFXkmcUpRtnLABWtBufcGsvz2/kjlYj7TFnNLs GoiEUntMnnD0S/gsdKMf =JAiu -END PGP SIGNATURE-
Bug#821557: php5-raphf: PHP 7.0 Transition
Package: php5-raphf Version: 1.0.4-1+b1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php5-raphf package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php5-raphf -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqVXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHwu0QAJ5DTmVEJThtFz0QdefxM8Lc 4NWKZweeuBEkGPcRVCL7Zs29IF5CqeG6D9KDLm856Jc1rVaGq9uEIzyjiieg1jhI AWnTboph2nPw3WPOm/h5TkLRhQK9Jiw8dmQjvn4LsC1MB6e1YLeSHdYbz7DAvR/r 7lkCtl4S9WEnUbtSTtHk6gSO16FUlwHKP6TGj11+i3rPm9MUjIWYouGJlNc9s8QH xsEs7IJD1PiZoXjSz+ec6w8L0NM2UdWSmku/cKtRuYVmPGO13ps4blKZVh5+L7e8 mRoSWdqXEp/iv1FV4Et7IdXt0jW+pvNCtDJJYECCwGCPqINNKY3/J/ImcMvyRjYN T+Mn4sjLTMUvwrqFjVplzQB81nrNcaan1EALB5Db2TnIhygflWoLvL0lg+gKnKIs ATS26vdL2WWbiZv4C0mEVtSIzdssWEaWH2sjMsP3RbxuKBYORbYVPsUUGRgHCTBD Gpm2moEVYf7CpsJqjFdUQWS6hu4hjHdESl5Qt2xQtDzrAVjN2k0Uc0+IH72tGdwc cJ62Y7yPKVdyY8trwiqyAO2py82KfA0AXAup36sCOjo0py9h0LAbY8VWaqb13GAW rF80ri5Pvxe5LedhEBMXo7I6ZnYLBE01ZgmZQCOaYmeK462RljiQMtMaFKBo+Xpu s23T94T/vSAaIGpDRJPg =mI85 -END PGP SIGNATURE-
Bug#821628: phpsysinfo: PHP 7.0 Transition
Package: phpsysinfo Version: 3.2.1-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The phpsysinfo package currently depends on php5 php5-xsl . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: phpsysinfo -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrKXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH/CUP/AoGnQ2NjcWex/mrXXRI2+Lx wVBcTcODzmkSTnqJG8ORMQjaCktJeEohDCWHtTPdx3RhStBNKi8KlNytT9H9zOh4 GnMx8sDvkjH45P7jY+B944X/Unv8U6RloS3ztZxXfi/cvzd+HasIOxWbM5hgGlAZ ntWx13m/HCrtWbLvJGfgAmRs54WLPDXbADcIjTt90jUb6XcGdhph2DaSMLvf+rYy HG8a4/L274sBTYuy9u8XOihR/daeHx9vlIf22oueRlAa+9WSUmRzZ8hXwXRoJCIo 9bm3ar7if0TtpWg57OR2Jyxc02wDJjJr40AatpPnntlXqzQyPAYlqB+sEFZHGHpu hD4S7TxeObG4+j983sa6yZp3hFXTMvTbFVjrZHZcE6kEG2WNF6wz43FblMxz4OF+ pwwH3gttXPxQOmaeS+XBAbiuRjasS/5SidrQKd4lGzSk9fdH8ZFogcVKQ5Vjnldi Bp7+w+BKjd4J4qrjPRjLJAYjXwzBhZGJXokZaQthYZ18EhmDg/EDc9uAzinylFcm GgIU6bxrktjDqAtVCv18JkYu+QQrOguvjG8bCk18jcSWZf2B+37UySYaQs1K9sVN oPjuhDvh3nDxPShwEalLdkv1fI1QQ3nMVr9Iw+/YNwoQQRUAho3KhvNhs3J9UX54 Fcq2Z0Hs1WQ4F1YvMLUt =9Bna -END PGP SIGNATURE-
Bug#821554: php5-propro: PHP 7.0 Transition
Package: php5-propro Version: 1.0.0-1+b1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php5-propro package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php5-propro -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqTXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH/+MQAOJAG4AkjfzyFiaWPaIXqDnb fKZ2Qu4UkvJB5iZCXKay9XW9VeKqet9qrw2OzdBMw/EP8a37TmHT/P/YiFQUWjUN y1AQygA3YEAbwGdKGJp8WH1YUUFZB187CpIE1L6rX68wks7xqxHZSI4InQSrCk3m RtnQVOwPhh/ogPAQUBbc9Mq2kPK94TpZzDr2uagmz9j5WrJTuW6+VbQDaxPIqqpw P2yp4NLcdLThVk0kSWJcVXjxQ3x2gs1o9qbADiRRW6vazFElP38QFHrNFKpROeuZ 1MBJwGZOaMblCNPtNpwIludw1BuFtF7YGxVZOeJ9kgDRoc29wGaYZHxrY1WCoCl9 tioJSF5T4UPV4VrmbtJDd8vu+JwQgDcuhpobGF2NNmJEaLzylao4+UA5xlEICt4a SVvimLmrM2tTcSNdGkRP2wD3mHH2ySgsYEcRGZQO4ibFTy5mw+XL+n2imyPEnPme 5Razdny56zjU0ll30ar/8O0OZv3xIDeRUg9GsFlJ/HokFffasky29BrggqTQgQ+o nvsedEFe3PVI6S8QsdjQQkulK2+4MniZarclAlmt83ZP0MYmOiAfh0IM2u5/jKPU yADSYsRsMpOcDrdUWafTZZOX+7ZHcmkWQ71ZyWkrBoMM+Nh477zlsAH8s1OKy81w EIff/xiICrIlh6iBX3fi =K69+ -END PGP SIGNATURE-
Bug#821528: libphp-simplepie: PHP 7.0 Transition
Package: libphp-simplepie Version: 1.3.1+dfsg-3 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The libphp-simplepie package currently depends on php5 php5-cli php5-curl php5-intl . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: libphp-simplepie -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqAXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHNWwQAMX727e+oNk8ds7tVGUw6syb bPKKIDpCLTV+gLLxiPfGLDMpzoi8z3y+Sr/P6j7lLKaWxExxPdo/l3WCfBExCP4w KKRYy5M1vsd+jGlb0jU3mTg4h/RPMoc2slUsxunw2z6e1PXQZXTXu49IkegUv1DK GF/DjLSRRFa7arZ5SW2CJ+0Ilkps64T1QuaJMHzg3yHHltLNUKIPL/1WV95Nlb5L YpijzQgnxWGx26TlevtRwJ7KUUeK7nRNDoeHA+ImsZYOL3S7PyvZ9kKmGSKf8FHL uD+1a8wKg3NVvGBDSyOEuF0svOMEVnFLDsmM+7z/Xn7NTaIP0g+W/ylGqmBJLmNs eNEWwkggXTDCjvpf6wDkOtZfj2ZuZU2dvAkk4YK1SiXRrV4NI3kO2LE08gLc+0YD gCyUNIN85NrapjCH9EJ12HYhlSpoksKwLLABb+pvvsGDW4rIibLDIjXDrfrgk9fJ VaJCLLv7I4nYxHeTNzcAkviRGcF9yiPTDhgw6RZ2jQDCkqi2q58SWUu66MqnF32J rGs6M1HGduOvQj5wwcUFz9xmlUPD6lkduQSnM9ARvbHHnHn5KaDoNn24UnysqcNY 7WckJWY1u1DddGrTa9EgGmMa6e7URaGJm8pENWv9xNRPTFTgoIPPMDkm5kdYhPTs AA6bLX6IbLasyPegc3la =ZAma -END PGP SIGNATURE-
Bug#821627: php-symfony-serializer: PHP 7.0 Transition
Package: php-symfony-serializer Version: 2.8.4+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-symfony-serializer package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-symfony-serializer -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrJXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH/HIP/3DHqN5Oxegl7aSbCvWurKRH JCMawChtslXc8I6/06MeAMTwtOdS1NEtltESM+AJhWIj2Fx5TAUGDrlVawyhHwTg RCR6IiHgMac/kfi2C6QImrK1gcwbJA/ZCSKMdC4jGrRZsgKyzXPOm+AQFr6x5A4k UOCXe1ZscXpbOMLL+IdqfVAPguEzbIyyJbdJ7rz6nQBnP9Q39+iDKsL3n6aff9ai bZYZ3J6deLmABbzcRkMlJkvc6QTo6cHkHwlcrm3EhNlnZwjlZSseNkmbPAWfFFde up99Q3f1+B9KklOvT+AZS7omwkUmrIf9e94YtFFLyYaOpO+uylStMcaTQCdQMN2U cReqxy7tNpUxZ7VpH9lsf7E4t3+Y/NvH2HZn9MvK+utXmW6kLr0bERBZERXzChD1 qlTQsnedYr1ODuXcKM37eDsDEyAw8T2bV2yub5/fh6Ux8ioiAltXOeeu+6CtcYBj WQBzjEyzIxK9u8yqmbsKiy+++D1xbEvTjGIw00hzUXouzfcyOg24c4y7lCETmvIW PconcL/N2tE1jVDkV7ps6DnFxTJmc4PWnCzXQknZuB/q+j2ruJudlTnT7CUBlTQk 4l/66LHEvLxOFBsbnb5OopR2FyaoQ00gDfN792eOY3NAvlPaviBJXLjcjE9x0s2V +0Ood0XJ1iD03c4APsdP =RD0N -END PGP SIGNATURE-
Bug#821626: php-symfony-security-http: PHP 7.0 Transition
Package: php-symfony-security-http Version: 2.8.4+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-symfony-security-http package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-symfony-security-http -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrIXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHtw8QALtAnN7C8hjRS3l+MmHikKPj DfSKjHVLCzxrCKt3tJW+FDqdPgG5fzEx1Yc6EknQhDsbc7qSo5faOgBcQmAfQ6UQ P7HTJEoVu9sc0Kn4+VIwc3alv29fwK/2UCgtC6bCEQLYqizV4ZCqOWlUQa1Brlne fWEZ3ljz8HJU9dlqJTJSiy/GvFDh2dFPS0r9YOmg8VRpPrlt9BJG4rvQtNJGn+Ng P/ERfYqsY4nyifjNAPgtuEp06iTN3obXkPq3hiAQHyBM0Te6hJsjx7GZIeC14ReX PJEDJF0Kz1rRsRmooXE923F3ZARfb6cCEijMOfoRGsVkiFe6XCAlkKB3QmA2V1m0 IFBsJmAIW8dXyzucuwdJaqBJ/do4hbKba+aG2odxYGXqaqZ76wf/3lnaVNDdhMEY OvGqFSbCMV0JuWO3iIgnt2QidWrwMIlXplv0TYgA8qmyjezDdpWWzR/OVdSkp6Dg c4AdugsESuQekMhlgdJkw2qqR+x3Y5MtcffA6EEAh2ZnqPbfuELxVOAf4stuPsov uEwnK9mo7cm+Auh/83UFJcxWPqAjHQj7PMoJWT2AZb8vOt3SSXSdhL8OHYIFD2Qd Kn+rH2FSseF0Ev0ZK10sFGHL/3YeQkmev1/1B8OOZDSuXDXiRFYvvls7Dct7gK9f EOSeYalSL7t7Liw9zpZS =QxT7 -END PGP SIGNATURE-
Bug#821619: php-symfony-http-foundation: PHP 7.0 Transition
Package: php-symfony-http-foundation Version: 2.8.4+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-symfony-http-foundation package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-symfony-http-foundation -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrDXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHqQgP/RQ9DdpZfXRAmjkpOoUNG8pU XUynbSSi1r9FJz95nDXDJ60dzWd9ZNSfTIkShtaMAJsu/lV0X4sqX+nS8USCD63M I5PrgVsZu/o1gaf1aKHm20Unf7myvo2L+H1ScVyJoCd41+hYk8wtUzpZQQv4nXPU V/iZxshp2yPa2FdFdq5dVg3O2q3FIIrswGWvmUG7qk+/p9SfDRf19S97jZLELL8u PztZjHSmy6sRpoA1ylAeZ8O4ydqZhslg/9riTX1PPOr+t3cHmXRb2oZDaU4BnXR4 eOp7dn0pUtRLSIT3wuQjfRXsC3keHizE+mwmd2KhUwaZQ6gmAW2aArYPqKD6N9kZ jEbmLGS/HUN+vA9Hqns5yAD9txPazH8i799xy/KBHuaByGhXRDeStAqkCriB456V KstL8PHQEX1+rm3H6o4Mj1hS66pxbxeYKBAXxxcmGXvSXxuGkwtWZL31I/iHDabh tuR9iwMqip+cjV3An3moLndnfFfzHE4CHVolvkaWGqIdQGxpjNpzviL16ByRx+5h NcRYs9mt+6MtpU/pF78rCNNKmRxby3EHxTfW63AI4+uRkShPkmOYzw2uaNMK+a+L d/ueBsZskIgIeDwIXo99oQ8ogJFz/9iGnMduhP3BMCRVjwSMCwQbD/qEgeHXxMbz 8K/uluiJH0Nn8ZMY0xQu =nR2N -END PGP SIGNATURE-
Bug#821625: php-symfony-security-csrf: PHP 7.0 Transition
Package: php-symfony-security-csrf Version: 2.8.4+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-symfony-security-csrf package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-symfony-security-csrf -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrIXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHsgsP/3GcjBRDBDwh0FiAbPNCGbBu VLOxByrJTtDpJv4MnEnxm9F4u47IuANPONiC57KYBQlILxo1Krnlmw/CdsJMzyXm EdxGldcVLVY2fGz0hoDaA2xCGoQHui80H5qsLP0de7jTF6BhIMhFlPdbYu45EVa8 oOZS+fVERuCPJW1Xz3K0wwe2gmaxh6RXBXFT79GL0/DrP0sHSFItC/Viy0cI7V+r FbRWLvk2IA5VdDAvv3BaRc2ds6imt9DbKWjNp4C75E/FJuF4UZm2g/6phf2r6AMx vrBGrK4VucFqSJw8AdSXbs2W0vnLKdesSfEB5jrfOZE8qsBZg/oanRIlmkCvDEpC ZZ3ginEQBSNv+WZ6MCiruQ7KWx29KCC5nL7kF3oAWQezyZk33NDNbR/znNoMiauy 4T2NrV0mP7kE593GaswDOk1avVtdrJb2YIAgxF59dIdLWK6OPF+ZtDv/gsslKF1w Y3HdT7BpNzEqb0JtSzCHhTBR/VetIcJ/50JPGsfPSwN3Jw5VhQ/nz1ykfU86Ctai nID483+mHhO8jcfk2csXXf/GJ59uV4Uoj+wZQfZSQ+T8Aj1xYkbhpGCd8i9WEBLs Y6siDsDDBj040oerJcKYmhUz4pNScliKEXr8aODchEOAj4p5gTqTy+gnD7DUSHVQ BVPk0RBnvHjd+fUCQECr =y8da -END PGP SIGNATURE-
Bug#821624: php-symfony-security-core: PHP 7.0 Transition
Package: php-symfony-security-core Version: 2.8.4+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-symfony-security-core package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-symfony-security-core -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrHXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH6nIP/1pQhSPWfXhfdnRCvZOXTcH2 g8qeQbNNytd/y2cSHpTBcSXoc+ZT+gmqx10PPvK3X9CN2183KS9BGmhxdcpf+I/2 +ks0+NpxU6BbPJWH2bsNJAzEUzA7l/ywQi49R8emZMNHqQa0rEgg49P/7R2NRvmY G4hOE0li4a+QBveSA43xbbO3hSoSj8aTbAFbO1vFvHhhkaP0JkZ6UZH7JoTPg6Xz wl1kRXPMh4RF02iGHpBo5ONr36Cnp7s+afQrWFGxXLESbg38C1xC1JOR4xXfwbru WG1RitpWeu1vKxdcv1jzljJBA7cVTlu4HvX7cklJ2vbaRqBi//n4FwccMkvKn4kD Ue2ByrVQsceaykZvLr8uY6eJK6I5MTJzlMTfHC8r6vyfD1VDKAhbcHnUK7eqtzjE cs2PWBOF8ufKcmTq5pCG1jkcS2t1LTkutJJJpq/BABlmf3Nf7R42eYfs8otYRHl/ bV1CU45McxcK0JBx7zKfDFMucmG/gXY6RGTXMdhBgDB/b5aXR42oSBQsFH8NRAIU xm3yb3Vcwk3GEfD12swKP9mKIkgNnHadoiIgQF5xJiGl7O/QYh00s6m6VM6SMT8S SRICt/9nGtdtl/ybYZeN/cEj/unFkLOdqVk3J5fvJobQ6jcEUvyq86CEeMDa0uMv Lun2Ge6WQVJ0GnzuBE2N =6h3y -END PGP SIGNATURE-
Bug#821620: php-symfony-intl: PHP 7.0 Transition
Package: php-symfony-intl Version: 2.8.4+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-symfony-intl package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-symfony-intl -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrEXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHt9AP/3D85zqJlKKuv20nFYXqX5sL 2NKcbeV5REA64y2wgYe4ebL+Bzp4fC4dqprnOL05tBrhYsgxjFRxCnP+6tvows5u y1/kdc1pFzSn82exmenuift5gQDCIRmBIuT1AXdJ2eAouIiecdhZ8FBItfQhbtcL 6DbHd+IEJUNxXJTsmCZpZoeLS/mDdOafH2TrU230JLf00yu8DRdPfIyyxa5nR10e p2Kdo4hiLqNI/sLOgJWs5HoE+axC/uuqVmTwg5PhtWqJCAklSdu3d19mp1q+K3VA 9JnlAYKOH8hifRznaeXxzxdlzfDA7Y7wsiRrUiZlYcZldH2y+/bAv4cckT3wazR1 QYvJ3WoJWc1Y3n3nKZp6+vT9Rx41f6Jgz0/vaS/x0kJqmuKKvsQy6D2mJaGzzI7T 9PViVmpfs6jzY1f9pa70O8WAV+ZxxuSlS+gXS8l5t87AV8XnNo9GYR6YLDv7+cCj A5/K+dPupv7Brtw/dOCBiqsMVYYouzS5hOXmYldyUV+N/zNzuH2x2XdhM1Q/RJs+ a5MUKAtM658jwYruP2dIBaxMwkZZdVmUt6nvDUI7IbPWmNVQTYKqPnRsGm6V6pOa YFYU3lUcL6/WPawPcatQszVN8G4cXLKhmzaEftf4r3baqZD/Chwwk96x8+uTluX1 LPXVJOK9Dqb07nXsj1Z5 =QXIY -END PGP SIGNATURE-
Bug#821623: php-symfony-security: PHP 7.0 Transition
Package: php-symfony-security Version: 2.8.4+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-symfony-security package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-symfony-security -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrGXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHbu0P/1uOqL4zA/itXM2Jw0fEP+dj clYuXh5r+Ve0B5W+Fd2N/af9hLyO/Ub755FmaVkGXJSHZ9hDdAlgCQvIySICqTag 78FGLQTxNX+LP0yolfnJ/CpCySecP7QOLkYFr42gk36UoqHRNIcO0AKLCbzYLn24 OJhGhHFso2Gipx7T6Vd2NLVvRZljYBtRNoapIz57l08aT9oV2AiylZ+NpWhT8xyl MpZqOAqy6Qo+z0TxeQxI12tHnk14wLifj0Y7rgAgyTQfOg+cZvIHkpWSTUqndcUd tQCfUndWurc7ORBFwJfntqqIhmMRIAJ8T+fmD5qCi3B8dr/BGQixNdjaAV8DG4yW cnJ+uVFsciikugOBB95NreJ4E7fXM8l2GeBjx1T/MCPGGOgNHKRZjKN3J5cy0020 K642DitGMXf9GCkvghOKPqQoeXuohjDT1lZeY179PSqlQjqV6ANjJiSd97bbLpQ8 dEeq55OgsGWrRC/4/RO/c2BhAkN7TfVkDqMQuxK1apqu7q2upsOEGMDceXSgKfmb BZw9K2Se6xwd8xvM4L10RlTnT4vG+ZtaQW6dCMngHGC6FjCspqDMsh78fvpSnDm3 qRX4yFq/8ELZy5n6OGOBOYUKarjhi/0XU7uNHZw7/eLbfXyrOFKzWzoAoS+TNZaz dOseTqWYZASoCau1wQZ5 =nWkq -END PGP SIGNATURE-
Bug#821622: php-symfony-polyfill: PHP 7.0 Transition
Package: php-symfony-polyfill Version: 1.1.1-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-symfony-polyfill package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-symfony-polyfill -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrFXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHrn0P/i6u8LT8mzUEHS3wYcTq8jb7 f54lEuhTRJmhe0RBvwWbWgLAykLq4l+pt4FmTKht+WcMGwRyp2aGthNic7kBMICA xHc5meJr0BWgYSMYl0N35r8iZCDNUZqfYHoeIHLcQLf1c58RFg6Kh72Ri/zQ5JSQ WtobK3jt6YdKnx98MEruUNAsF9WEISri07nQPcWGy429o9w3ZI7T/BaiCa9K4+vZ 2MRt0hLsD7vvBkk6nYuX70jBq6Ktl5PAJZ0Ue1xfTElz6IllIQ8NiLLxpyr9EHiF Tu625k1NX4VAcwErmD1WugE5svzeGT4SN0CmlBKCych/Z6hoMNlHXorXJz2qYzBr Lf1TNsR10oNDQozUwtZEev0krdfgTye0MZNQMaIBdcmf9HIb3m4cVuS2Ih18Xq0+ aM62V7VHUuBbucbO8rcrBjOm5ztGfvxhNTHvzGpPiMYm8ysBJVT0MmjnL8QGdeAa uBSqDCPKEhLoYNPESsomicSW7WRX/oqaM+MBzcTjBJhlUdXygFEiGnX41lB6jNUN wQJ9K9wr6NHTqCa8j8hyt4rxa0k5scpD7lwgdwLVPFdPGGpAAlZ9hEowtm+81GgD npG4D9rptBfUQLcqg123GsGYEit61MtlEQVsIgZAs/IXgZr6xT0oU3DRwqLNo4lI X6gwNxH8YkxnnXVKLvT7 =B8LX -END PGP SIGNATURE-
Bug#821621: php-symfony-ldap: PHP 7.0 Transition
Package: php-symfony-ldap Version: 2.8.4+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-symfony-ldap package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-symfony-ldap -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrFXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH9m8P/1/eju1Bbyl6fAEHhrHCmBDr 0njgs1nq7xsc3DNBNi+NeHWwSSHAW1aeGVHLECuiji6CmHI5Ega3KoPw3FhMuGQv DIIJEEs5C1BtLxiUPZa4hHy0hA1dX+SHtb5zQEJb4ttQxKNaxYaXVrTVjCvSL9iF taOCPcCToINDlEitZ44UJS31DyAUITYh7XGdLZCg/XW9qt/Mj3IKM+nhXY5+3M63 p/kRZowl9Ve0ADhwGr/El/YnIwA6DWr+Do7ERMFi5HJJ6e+XNtN3QkeWb+s4jkSL Mu8LODV5L2ZiHcE9q5yBuEBDeGjPFS57fKnIlQqyF+bjvzy7kXDzNE/dnxH1E0Du do2a3R69bn8V345fF7u+3CUnA86MoEtRW32YJlxKBzcJmTEMXzWPjNpF3JMzQjAS 0yr5QjAwYa3aEehcxZPLby24jBtG3Gjyaqwq44eHkWi2h08ijGI1lLwQ5KXjMxge Rf9wyQxhp3+tgsx+6qCVKjp8/T270aYulfk2Ge7fP/lw0KnN7urDonoW8BCcyq/o 3nTyVLc/PhcGiosyG3Hdoi5YNWuIE9kmEznoyC7C2i8IQXfRHedpE0WiBeJAOXQY JyTu2HJRAIlbEzOsAD5p4XS2WFXZD1jnYK8dwbnim6hMfZ9OEHcXLMFLXCGXlKhR LtI09iv3veaX/x2Ocvy3 =V/1/ -END PGP SIGNATURE-
Bug#821618: php-symfony: PHP 7.0 Transition
Package: php-symfony Version: 2.8.4+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-symfony package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-symfony -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrCXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH+QoP/0GdetGgUZoqZ00We3gD02Fm +8mGMTbre2+p+MDfbeoMLqXB3qkHCB6IsrkS7J2eGdp44o3hl0Z1a0KxFE+zep6I z6K25bmhxv539YPFUMHnARgRPFokKO6kFE1Zq4s+rG6NmenF5nCRpVlhncNaejjX J4XJ0POXdLVpxBVqoYlipcokrqxcjEM4ogXRk2D2LciStDHiTGYWgfi2savd+gv5 wkYAeDQ1UtGB6eJyrXCwuxGUtPrezsirwHSlL+2wKslQDYZlcDY/gFghxOIGH4QX nr2Ib9zOf0Ns5ofCihFhxgkWI8qr40b1o5yuyhNrF55iAYUYjfdGptzvsrHL3P0p E9Bz7KsutG9JF/dQC1iG0dt2bCKd5diflaYNQL9pgU0kphX9a4euQIkeIOV/D0ob /UwrkgW/JFMGwwij1qdGo4es4kXCY1iP+mXjx1ajbzuCsSzG16m+noiz/Num6Aq8 gGjkcPFK8YFh285R3SZXDq7SSUr4dCkepMDMtjLawBX4gqWIDDtaovTWyJSEovIz FgNHKN3AQAW20XdRFdihnR1f5rqveZOYoAkn4ilV+wZkX69yep4734ZwtZmtI7xj Ql9hdlW93TWl65AWa4Eo2ZgSLIxWdmT28/zNhSGOOWpnTBJqcuoxnSgSjbGYAvPh Ermv0yZXnVx6GM4xBZO7 =eGJt -END PGP SIGNATURE-
Bug#821617: php-swiftmailer: PHP 7.0 Transition
Package: php-swiftmailer Version: 5.4.1-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-swiftmailer package currently depends on php5 php5-cli php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-swiftmailer -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrCXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHOWYQAJkhMDZfIfbzuY+nkNrjlhLt 7OE4fiDelPXuuFp5FJNNc6IAc7ijjwjUV0JCPYXHVRAQDVOJKaV/M+VRhh+ZDTfb Opu7VGZ2cdDyT9aw2hZvQkA3kHp8GNtXyK9betyw0EcG2DqOv5u3oRE4sO0FjZ1t z/L3uBwv5+p6c5xvNdz8+MYW00QuDcgmCbqBsK6MZTtTN9/Gkwq7BmI0T1SKKGZg Lc/tTInEEdhAtFzLruYGe1fgJCQb+F9ktkQNMdxG8+6Jj8H216CuqP4YnTSxgtmU mEL0s4rWp9KN9iHhQJIfW/KE/dd6x6FIWm4vIqPgX37DIXULmpGymA6fxd0XE2Mu GuFZMF/dVa1E/mvWKn3IsUoubOPuMqZmzK8fEMO+4G1ciVGHb6EcWRkzdyUOJF1A fDmMgOTn15wn9CcUoVOT1FNHtBxNfBAC3GkUM2UeRCrTS9W+poCsulpnIZzkUnde JmnYi3Ut9x/twJ8SzhSY14+j+rOq2qeh2/825uMsyRt/N9bvB+BbMp0OgWzk6ZTz u9RL/dptbbUc8GqWiXGsbhLJ+02NAg1uUpxEAI4dRuLsmXNZFVTbeeov8F5raWDk wlf3F4IQ0mPzTzA+w6A1Rzseu10CCvOpoeg6HtKgi6d9IFg9+8a1S49Dxj2PYqnV N33UmdUx14whRoim6c6u =V80P -END PGP SIGNATURE-
Bug#821614: php-smb: PHP 7.0 Transition
Package: php-smb Version: 1.0.5-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-smb package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-smb -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq/XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHqF4QANG0Gju4IDa/BXWI/VR24loW 3o9aNWax/KXI14dAhG2JAbk/LZxi5XpOvwU7Id6iiDQizaNknx3veumG4l+r43nc GEmlUNu30fKX3PrIps6NaxjxISRWVqf+nYd+nlWJy1e7N+380PUBsAvmbHQH1QVO Q5ngP4vydbckuTuUXlUt3RxfsqsySg/WESWww03ag0eUXb3tvCgP1FuMHE1t08V/ PvGeJYW9NLUCMyRfzEaxHBuyzILm4wAB2Un58JKf4ld4TG+qbf4BuP9/biY+QmgK yfcx5zsheThcGjb0sZybYhNwJo8txgWIEocRamVT3kdg5ZJNhF0YExJiYfHWf0Yo ip7A/R43NGahdxz78HiaUb7Lvyp21JDFKuCQQK1pqVCxyjtv79gvj1BQkyFFWJwz DktFhJIFQmEPYG0YQkD6WveXjfLd3KeDKuY+X/6SxOHr0EpCR9Ni5BOCSo2bMVV3 StGzDKnuLLkttOBFmp4Q4PBgabS79Be0+a2rAn1xxvtAdf5Qll9Qznw5p5tO3ajn uwrhoD5m8FeuUXRupFFRXf3UP2tQjHJAnD1q+jtYyUN+cfHIJK9WhCDOZM+YIsjZ N3h5KiK4adRcb66TpQIeioOibk0EfxXuA14OdCCiDi697AdubBgE4CxTDDhDn1j/ ZPyZZ552zevmqsabS05x =hEz8 -END PGP SIGNATURE-
Bug#821612: php-securitylib: PHP 7.0 Transition
Package: php-securitylib Version: 1.0.0-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-securitylib package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-securitylib -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq+XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHB0MQAKV02ebWfYF48lInRrVF2oN9 fO7XLIaleATavl2jf6+Tk2LHLw7fnGHHPIRj1p3aUZI47mhBSeBb3bJs6NKxcztF vdG7iBA4OnEnHmC36FFGn9HP1JPkw2SoMyB3b0gv2q3kZngfeHacmbeTEjNnbuv3 XiXh5r5Hv4ImOH8TkyE6qRVNhPEwafMXnwdNDlMFbkFyglnpnZs/vcGINKHoyAbl UMSQqRsbYRWU68nD8tpDZMjIHvXbyuLpSlgdc+kKqHsXGrGpw/1WyOJ55ug0GjRM KwbIOCnxijD4XdLTSnUQLWiOokcIjlR5XOH5dLI7/CpKEjgDj2mSaj0J7QZEvXiz Mnb9Yb7aQTIOlnIKue2ov4RpB5qAFO+6Cox4mGlXDiIfQoIa0L2h4gnL+XCnxHpE yvZgWqdlR3tJDLfEkkdmtKghM/FR8Oz6/Te5BD89KMVAlXKs47IgTnWLj9FP7mpM 8bk6llY2GyeWnfUJBq0oNxgpzDGz/6XALnAywlaHF/hxX7TEJBFOz2PZF9/81dBm xxWLaMVJgp7oX6OuD4angFBKL60Ekz6Dw6V3pqwEwiTREbkBFHzX8mXg3QeDHrFN VPYr5zGFj1PDWJKAHwfegK6YWRfXo2PuNUGluwpZmhqgIj9ocqP0rNdpUqgx/4wF lcJiRGDaB8jepwT59Rvn =6y1L -END PGP SIGNATURE-
Bug#821610: php-randomlib: PHP 7.0 Transition
Package: php-randomlib Version: 1.1.0-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-randomlib package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-randomlib -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq8XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH71oQAMy/5FCToxZg2/AI1DOHv4dj Ds3Rn7pIv9PShnBxBEu0IaZktxRGoaO+/t9gJBkIdplOpJ7OFHnV5wJ67rJTFMNi sYics+5h0MR56ZW55F1dULG5RV5HPJnWw2Df4OSHDgYv3TnS1pJbgAWTuBN+Oo2i 6+yNcVL5nY+eaap3LweSNnFlSUqBORdsgKeEFqCu1h7EFk+ssUC2ACH5GrhPa/cd lZML7uZ8gVl/4F5S+bl7CQLWvWdH6jlgpwlIgk124w+3xNGuXlq5fEaKPGM9n+dz 5NaIXzYKh5pFWqsQq1zcr4AaNfSAcWDV88bU5cEsN9F9czOMZG3SadLP4NfSBDI8 mD7nkRW+yd6lIIECEVWxyAGZPobvSYJ0mOBdqxRALM6vrs8Sj1h6B1NXMEq96e3B fuWcYgfiBcZ2s+/ekjvyakTxgWLLBmLVcKApWZIwPbQyBmGjzarqwxx9ia/VntUb qCm83son0xps+yzRW1ZlFl9fLqw6mUrfz/39lNw5m14ZUVyQTRfZ9K3xHvthm9Rv p141rPlTRW+J5I5xYaGMqdGaE7dzNBKnlTRXPs33zQCWaaGfbUmliY2CT9oD2feD 9ZiKosYpU7JHYUzJkdatLDQSG1AYKFcap5nOsz28miiJArI9SbNaBS5vIy9phctQ HTCGKrY8C+I2M74wMRKY =0NYT -END PGP SIGNATURE-
Bug#821616: php-superclosure: PHP 7.0 Transition
Package: php-superclosure Version: 2.2.0-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-superclosure package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-superclosure -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrBXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHEeYQANCXZTKIjKUSQBAFkbToAG5D Y78yLkBigXzeTrtFs+uzmqpqz7nXUtMqX1RcSXqTIcrPSWR//6a0Sw/pcP94qfuk Hd2F2EUttAhkWX6TgYaAe3+Vrw9qZf3E/t4El+Y0Q2WuX21VwVMBaTanfWJ7j3JM FjqgN4VdMr/frgZVJodcn922Y8jrBODRFNCNs6GUGmjNbpIBVH7x6oSGBNKCRCNT 6amiMMGBnTNsabgzlWNQYn1t3l/3DsN+qkUIEZdlSSaUDZSFfFYFixHOSahFlkLr XndZpcTLkn2UB2E21UjsFzmv1n2aW479T8er6xQDFiNAsf/vupAXEo+Fm60MMDfE 6Um6oG4dlT63Kql+vhkqEBOqQFNZWZ+nX5RlQmdisKD+nbsVaIQVj/C0AiacEIyd AshbnM5/nIZL1WJSWejFroOO5NKhQ/OQUN/VY8Ik+BiPY6xqX3bSmHPM0QOmcelY dT8Vseh9WWbNABFS3Bx+7jSGCLxDYRgoUFVWnqRxWFdcrt2/yMMsbk7gdwvh40AB lHrNNmI9lvvOeBxsVaXcIcH7oBlFqQT/gx9gZQ77DSJesrZCzwm32O+RGmJFTnVC TY6iR46L6IvUq16sSTYFh1jonWfmCbVQpWMThCpQjFjd0WfLCvixsPq4z18z0rin E9yKGvhJSWXgzIznKWT/ =1h4o -END PGP SIGNATURE-
Bug#821609: php-punic: PHP 7.0 Transition
Package: php-punic Version: 1.6.3-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-punic package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-punic -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq8XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHU4wP+wc+jaUI3+uyH5La5xAaaD/x 6WQM02p1l/dWgZ0oJvX/me+wNdH4msQW8pZ35qAgRmMOko5uUQGnKrNfm0KLCq3S SmRCEYH/2eo6I/n+mrObsVr+RfrGhNd8CUUMUeVPs4HrSJr2EooJh8XdC96q2pCF kZrKQ1Qtt6MtFCcd9dc5rrkVdLKXCjdKNXF7CrIYr/i7MC/60bIg7Fs6dqobMaTc wofgpWCUDmZHz8TSTn6jfw7BL4Iyep4TPpIYNslNDJ2EMJFVVTGoAt14iu82glA8 z+fk1/vx902EkX+a/S0gKu2K5BWliMxkSqdV9ZQu5NT9C/UbGLAsM5/o68oqKa4G apXsQTntlj0waPnxSDqj+gYX065a8xUJ238ULCUokG5TeKUl0sp4CSXvosTQa+qS 7zscuGDdhjtc7W3zDtNy4qA3YQwYuJqdiW1SrGV+auo0dPhv9pEXo6UGKstNzGVW DUKtXAsvlDN/pHYQ8J5Hpzlst9RT91hfEKIf4iUnXjmwK9hITpgi3ISWppqnFdxx 1GYMrMkGxAea/q/6IHBa9xrOwRuXuNTu7RI+cIkKqPCWydKJiSz9HA/KqChH8lGG ZjQw2xxZNjy9hUbI7grD4cVj6px7Ag493K3fEwua3FcJxsST3Opa74njS1B+TZHE p2fE42ROKAsAfmW8/cC4 =o6NB -END PGP SIGNATURE-
Bug#821613: php-sepa-direct-debit: PHP 7.0 Transition
Package: php-sepa-direct-debit Version: 20131216-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-sepa-direct-debit package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-sepa-direct-debit -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq/XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH65kP+wfvtm0+447RVm6lLAAya1kH l577p5K1MVCjt1PZeZvKul96YWoAEGyXXSABgt1feMD+keJ6cAhakWPSkCieSUF7 VUJIj1g2rvHJEoHpnZBYG57sIyAfJS610MPgoA/d4QBLHEwCJ/GyPhp6TkuG4FKc LTLOaOUCDILAJF7et0sVTBq96ILR64Z79Or1if7hbiEfLY24yoHe1EKZAWgW6PbU B5+OX8IZZqyNxj3YI4BPLTyqzGKr9qKlGuGdSFnFNDlOn3bTquWqcuUczg0AUVKG ldzBpc1foxawzxuyb/2nO4l7mRuAfhrvIgEyTB92447je9OTc2Clqt9Cw4Dw6LNC XrigVBSKTWsncF269N7K6KtHCILnpU30MGQ9wEzcKu9xMQmOkbUDCUvVEri7q2AB t+9qfzozoT9kweKfjtdkaGVo18KxtobMnKQbX7irxej/+Co9KYM7v/irdoUMw8Mc BDsP3tBfZ82iLJM1Zv5JJmEBv1wM9rY8dGGryTLDrHB6ySpoDyKWamtLuC6+fV4d Zatk4aQjG5t2h7M9YmJwGSYdzzJzBGW3DoRkWQCM8LSn2/YD0uUtKenwmmceabW8 UtQwDJJpkN63i40fLaOi9jEzcwNpWGWhb72aR3o2FGR8qQKYTbnpuqzn/iFQpybX Gpmt9UBry9KJn+Q1viiE =Pop+ -END PGP SIGNATURE-
Bug#821608: php-psr-cache: PHP 7.0 Transition
Package: php-psr-cache Version: 1.0.0-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-psr-cache package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-psr-cache -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq7XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHPToQAL47chF6txRODdkwfR0s8zHx YNR6ULniVoxPE7gbHU+Xq1E4Hch9AW7+aNmqkzOYwOtv0QmF8aOf9+T3d++Wsp21 61Zz+Bf1DwHcAEDh0kKXgFDvd4fMplPXKNRjUHAJY/CiecgDMpk+Mvp5g49edLyW HKCpHPfQqWX3Y46f/xTQ3K1cVldewZ1qF27GtQgAh0TfE7eyeEJsy1cj3igs170h wrxMyEfJ1ct4Zi0HbrYAISQs41YlOWHub4op/6CT66JSEySDQbtJprKy/Ofe/yoc aIzOauPrguPnlw+g7OWs78oosa3/+tFurK3hysdAF/IC4bSVsl42WvcD1CPg2mGx YvFOYhbgXZMIQWhN6EUEwgDDIgafxY+8px9PmGT+ejJ+gmpQe0tPiKzxYk7GEmOV r/d3+K5rRdVVvnV7081BbD292FQk7Kl/A1tThgPeFrAh/h7bFGP9WM881dMOPz2Q 4tG5tHdkG6mNPwUh0PkqdvTEBESVdKGnIK+1Mx7sYOMaZ5unmf8bQ6PjCpxK2C8y 21COTPQTi8KnMSUMxyz8Ol5DRmIXjPJMSqrKD9+2HODdyZ5iKRW4S/rT9ol1ZPdl YO6GDVslsU/zqYEWFjUgGfYstEdK3E0LzMLW6X5Ie1XqOfv/GsMVYGxbcEtD+6VD Kp8zk3gB0sa7fqAw2sk9 =tp/r -END PGP SIGNATURE-
Bug#821611: phpreports: PHP 7.0 Transition
Package: phpreports Version: 0.5.0-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The phpreports package currently depends on php5 php5-xsl . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: phpreports -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq9XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHkiEQAJz1Ik/+/pOqDSGDnJVzbqrc WVsIl7qqKtONf1Y5orq/3AQWbHV1ME5v38bMdsyVarqhN5Wp+B2RVTmjDntBU//y jcgY8KU+kQLHMCnhV8jW684hPPKYvX1gpGGO6dCwFfoIp1f/XUGpS3NMlDsiA+lW Ukpf6EGqifyZWGCo7AN5iuJb7Gj4mkRw2bVgEaBJNo/1gh9qN7LnsXrjZo1uOZ2Z OMuozVhz4u88c8EHrmgaNnvwIwfCB5uSTQPEm3tMuAA/J6nq1NcP/W4zWXMGN3At cNoDcYztdQKV0kpeNISRgjanWxmfQQtuwex/1+Cw5jLDDH3Qm8/gzHhzVd7kXkyA KfpmPZGZLey2rvA3RZ4gr6HZ7F4HJhI62QEAUV70cRNmP8KNN7ekfC/r479O7rcm peZxcLnvmduotiYshIzveBz5VtjANzCqy1qGNrzPquS3N3z2t/Euc9fm+n810D0m Ll6FjjQKdlF89FZaJyWoJExmGIAepdZAU/CCbvzrgsaFmdx7+cyLIKv6WMp2/dLG Rz4diAH8fYfehVWqjktp3ut0wsQQArJA/cWGeq/H2uwdOBW5eK2xf+kpLezlQIhR A/Lm28cp1iEFPrCfiGkmF9EwEGxNPlcvO5gMD2l+3LkeuMx5fLWKXs59Z4fAox5c 4wHaOQtufXJ740zws1Jt =I8PV -END PGP SIGNATURE-
Bug#821615: php-streams: PHP 7.0 Transition
Package: php-streams Version: 0.2-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-streams package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-streams -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUrAXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH6VYQAJkIqB26TYS1rmeO/BCp2pNX BMx9gQaoB3RVC2lgiEeFD24X/QJLjHFAKhHUNh5Bqkio/sjIXyNqTBZEW7hQOK0P fFLE5CN8CDvd98F3lxFdERiT5nD2og38JQq7w/6P1AAhHKDgptkrc3OsziQWeuWq /FrrWqaiIACGpMjqGAruvVADEuPxSpdRXGGZVtoZJXzV4RPMJhAB76lkRVzS7hkf G+TansX5Z4bStKAIEprhowdYQ4o8fpxeNrvksRD64aWsDlBrWo1N+A0VI1vx3H4Y LGAEwJ0vzYPUPMZTUDZ/gUe+Q8oAuS5xtQ6k94RaNySi+V1xzZNWFMZGMuLcvZu3 LFrlbEewUp1dhHFiW7yYggDk3lwARFSrt/gPz3eo/k3WnEnNGVm+jqOD/sZwYyzl lM7eIMIUxU6I6SLIBanlDXVRoGVh2WQp8LNbUG24K+kano4+OpmAhJ+T9I5xeunE Cc4ZkmRwXXfb4w3D2UapUDidUjhdMA7JYGyDyUqKtKACvJZ9xSms/FlAX3+CW6mS dr887GK59997Lz9vS3ESvPd7t2sUWUvciZSV7JhNSa626DIaHfJ0sS1X4s58Mcl+ Re79Wit0eALvNppxG+j1kswsvAUx9ys2KJKuJEY08Ro4Tj5r+ASz9TfQLCIS+h9C sRegAJxAyk0X0ZKVsyae =F/m8 -END PGP SIGNATURE-
Bug#821607: php-picofeed: PHP 7.0 Transition
Package: php-picofeed Version: 0.1.19-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-picofeed package currently depends on php5 php5-cli php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-picofeed -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq6XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHpmsP/0YKlJdOY2b2vk71lKsQPJcA CCQcOPJYgn5wJxl09ShaoyVYR/Tojwg0vXTWXVU75DIGUGeF30LulcqGfeXcrgPg dufWsCWF4NGd0wIbuW2cK5SM/zPedHj+F8GoEY8S6FdMG3jQQK1zSSutIxanzn3F 1MxPTueWPWjYdSdud3Bg6ch8V5GZ2XKGgsu/vU8gFWH3cMXAU/04XJtNmSHONdhE hdsXEU/5AlpYRJ6MXcdkt/+kTl7XtVCX6+Ja2wn6CC9cP+3R+qFEuK86RKKMKJt+ eBKM3FLQn3Vbeh4LU5rx2kVL2ABU6eU/I4hqxuE1Jiji7giKw7Pw8L17CARrvd6f E5eXhTvxHFbPCmKZgYcv4YGxawJZmAzMXtxuT1UBxkK+h7LKnBsp12ZEZpX5QVVv View5mBYt7B/ivF6YUzXODLcI1tebhstCWnPQwiyU2OpyoknOXodZmCBJXynS/2L QN5HYuapVAJuLj1imNoXDLiA9WD30lefIDhktWdYvNvqgmzEpqiFdAQlbIpqLn2P j5FkgRfpSNdDfy9p4PViuvEzSy1jcAQn8SaczyUFD8Fsio4ZBy2YPT4EboxXU9jJ db9TH9rucjnAalCMZodxuA7k6vwbaVdDEhnOCrd65fE7SJj8Phv56K8n7t2PEQ/e YPtVKl9yQ5qMpSwHQoaO =262s -END PGP SIGNATURE-
Bug#821606: phppgadmin: PHP 7.0 Transition
Package: phppgadmin Version: 5.1+ds-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The phppgadmin package currently depends on libapache2-mod-php5 php5 php5-cgi php5-pgsql . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: phppgadmin -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq5XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHLVsQAIavXriOcoKvX1MtbYjjDK+1 LVlC8cvXEWpUHdB/yhqw1ctiK3osSlPKALNYDdM+3jk7ts9B+/h6tRLcQq28TdUc 2V5f7ZZqeVQYyHIDuTKK/ZE3y4NaC59+nhU3QKw5aFiRSDL6qFs0Gga8+3MIMM9K RhyzmDtFPa5E6LloBqOgBrczE+89jRRnJy4zv3CNk+y8jIagw+km8jfGWLUylB9M mSBHI5386gpgcp6bWbV32BdQIthOWKiK4TD1Roh5UsH2Ga4koozpklgEXsN7h6Ad n47fsx4bPzQtNH/PDoEQhF2XZIHiVrzNuoXt4X3mUJ50U303CfX8OAOswovchp+N sVnP6CorxZDLbHFvTMGUAhma5TWH5hJRtfYorq8RK7g9Qv+EUmhPd9OSXL6779La V3IQszpbA2YWqwLp7wdO2+1sibUWv6UDKGYXtqfqPZNcV1DzQXtTpxkAzfk+ECdt fEZhblytDNSfM3t21dyguipSwxRBCEy3sZCb5e6zb2Uek2OSbsada+76BXSXsePT 1d5ge71eWAoiyPPmIm0UO+zS7jUhaSIrrFTjK8gybiv0sm0uRqDPsR3DmAjgLMn0 kD95OYCPKWPu+EP9uXPsHCGJ9Rp1xTl4QyKsu0tDfgTxgzJ+v/jVIEkng4tGOWW2 dN/e+VUJ56D/3ojN4u8Y =vg4k -END PGP SIGNATURE-
Bug#821605: php-pdfparser: PHP 7.0 Transition
Package: php-pdfparser Version: 0.9.25+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-pdfparser package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-pdfparser -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq5XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHclwP+wXQDrLcltS7bf7j8mEBQIt9 I2JkihX66U1+207H9u6lRCarxVEuX9KGXr6hkxdm4FVQ1g78LGDFwGPypQe6Lztx iH0vdLKBQ4wWOU0aoCreybP2VAH9zDYs4dPnYns/B6ikvYOlCtpgAsO9km9/I/Xt U5ZbJKbvX2zRV4zSEXVf+5qvbtoelgFFBmMAoTSUs2ie9X3OHNm8Z5P+Z6gUejfO LH89323ZwQk0B2YHTzYF8RwVDp9Xld3vTgmtUdqSIxQ9FWi3gzYsOn41vgnTwhEr m+dadrDDaWbr8hB8J4rGuTq6TgrVHiTT6yZl7ifE83lJLw1xhJyihHYAEWyEdNPF CtyM1wBwVIUH3pD+wNWogXVrNfLBhAylp9F5r0DvH4zBn56SPXqTuMtFtY9RS/dF Fc1HeCuqzNGlTxebGXi2PwnmTS9QMTidyrfxG2xS9ZJks9DM4L+ttlNqZNIpuhRA Jr4ji160sRjxs9NmYMsKLtZ1EUxoatxAKE3I1WcQZbK8pONWtysV+aNO17/+wvCJ LQJt2ioWY0XE0qWRgvXzeGw0x5hYEIVnz2ov00JIjovhh2x0OPKGFvJwG/tbq6wA 9umINMD0CARdVn/lKUZjxmjYxoKWi+kUzaWf9elc3o855imUbp3grQc03MCfqHA7 Vy/z+IW8Q+Zl/6PWzQDp =Vfw/ -END PGP SIGNATURE-
Bug#821602: php-opencloud: PHP 7.0 Transition
Package: php-opencloud Version: 1.16.0+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-opencloud package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-opencloud -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq2XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHaRAP/3dhuUGP1mhmtyy5eDz7Nvh8 q8yZlYn3SpWNsobe8AFb3Eh45FxmL6c3hGgJOCMq3rgEi1aPQtixh4FYhvBomGwv v/TmqI6tIwJT2tKoE0699cOJL7sFp8yrkzeZvHdkn1jbxAVEQsIvhhG5ROQ+80Vt COwM3pWzmLXmUMtYQjW1jqZR3RMmjk88fjSWvhn5AicsNUvYt756cAueMYKwdWXa NQHhfsaUHULrvP46WUUl3U0DrrMqbwYggdfPhyRxexKedMZWMNWF2dcGFYnwRjdC uHWUQ0PUF7JVKvTP1StLjeKy2lgYdITCenz/fwuqAe/PJDYaO1SwwgTq754xREnZ dOkPbRp9HlrTZt36IoHCuPjMho3UMtMNw9Q2eVElpd8hUg7ALJ89GBaXZT9GA0rD r2KW/zBKToMeUITvMqckqk3WOOvMXlJf8wPr2x9AXYlIv5SoJzC3Xv4tCmjkPfb0 NDdRTdg6u9cq+GRBUggg68ezIcRkfakLgvN5NuIayvdaIDg6Dh2pDDpQHJpfOCMc FMok9xkCiAGfalF67iBUYxkViIsRWUVyNQTxYSH9Gj6qlyyPybPrSlK4DgupJEKf pUOOcnZtkx49fPPFmFIyYVYO9CotPPSytkgzAtS11eUlTvPMCPN/BeVoOkq3foNm zp2RNE6jnZ74kewrqfrq =bPM8 -END PGP SIGNATURE-
Bug#821604: php-patchwork-jsqueeze: PHP 7.0 Transition
Package: php-patchwork-jsqueeze Version: 2.0.3-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-patchwork-jsqueeze package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-patchwork-jsqueeze -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq4XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH0/8QAN0JstLOUFLefiAHQ5rxmHWV YmzG82LotoqZuClYGc5Hr2Kxd4bBsQLk6N0gnKe3QEdmRLBeZTi3g8ahtsAQuzb7 LD4quHp4VpNSzifAFXbUAcoXGw5t7v9JFeqO3kPmKMOyq4By7R3NkbLKDz8l6uId j3ASugTtdtkzvchcQDoo+nSjMIkN2pwDQpsW2cwA8s+FB17gEeYczf8wGJKDSPFR acnudKVVQus3cyDfFfPfOO90POvbyzNjyDSTFdd2byxoFsRYfJm98nAbPGH3lop2 uIJGAJeencrLS5D0RFelRNBa+GvUoMxx0ZRAT2N3h3zLA/Qk+jc95nvXNkIsqnEh djqekbz4TnKOSoxxD/SGgMWRalufAfuFkBllzpcYqLQKbDDBM3jRMZ0pdMUV6K4X 4ckBUhjOF6fGjQRg+UkDcrDBc0eB4ZyqktvfCQ65jWj5iKkIB29+T9bLZ8MXOr9q xwCepoL5NHvgGnpq05U5BmdKVjz6IDXPMCknKg7ToX/cmAV6DzHKwQjbcXJPlm/x +k2hWrkkXzCJN6JpPKK+YmTn51rUcNr21NC5DD1HhWKXZt8jpZcm4toBSagXWZv0 +TVzYsrawjPygBJMz04KCfsNihAQ8hzGT6x89n+gNKcA9bc6NXC8QaQwkP9aB8tq nFVF2KFJ3B6Huy26x31k =HDsJ -END PGP SIGNATURE-
Bug#821599: php-nette: PHP 7.0 Transition
Package: php-nette Version: 2.3.9-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-nette package currently depends on php5 php5-common php5-intl . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-nette -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq0XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHLkoP/2G7CXVgZdHNcCu8A76nGvbY sErMl28DzA1xC4TSn3Y/IudoLmfPCCa2srV3JY9oYtlPIByQ2fsAoal3w55a73X3 gXy3fHJ8VXcKeRTu+JF5PelVtTD5dCWofmeHwZmIaCcJ4EqcSaArzBXxtVh9LXvB bM8EazuYR7Fe9Umrahtd7tr2rngoAQvse6M+qShp/pcC3kQgwsGrj4mYkCIOxH7l 7Nrh3o1jgTds9/WF35OT/I/ND6/QiMMCwZwL4jPw43Emq+MK1TWyQqxX5GzBHhzQ lEqy/cQEbazQwLfL8K1c/x/OumA0A5p12SSxxxH/+SJizwq0W0waHsO4qTFvHq+B Mda0QotcLIZRfxXTx5q0FB7mtcJiasuIpLj/DZjEPMCqfBXsCXML2x6sVcVj5+7n oX+ZpY8vSjrHMyolZYQBZZetqeB0DzaI7QBpc6tTX4ENK4LFw6U/RaH9limy4yIH 97BRG8GIxAMpbIyKPTXfoB/h0S9xm7UuFYHQLZgY+up+3ZIBzfhr6VVyrFmYK6kZ J2aWJasUUPIMlW9a0h1D46oCUmw5FoZ5un6Lh8OdogA68oBa2t9nbnLoJoUMwXUY vtKO7pd9Z/FeaFRkXKYCPQ6WILrIJpZe19f8s4buH1JdlXIb1oG8V80TNdYNLs1U QQZE7m7RLrjGFubSsDMh =Tmsa -END PGP SIGNATURE-
Bug#821592: phpmyadmin: PHP 7.0 Transition
Package: phpmyadmin Version: 4:4.6.0-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The phpmyadmin package currently depends on libapache2-mod-php5 libapache2-mod-php5filter php5 php5-cgi php5-cli php5-common php5-fpm php5-mysql php5-mysqlnd . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: phpmyadmin -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqvXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHkdUQANSkSd4xM8RdmrzIVDY3Mv5U 2ZsTsgQp9rnBP8fNw8tIYKHcPvYPkGk0kwfE2RtzeDOcSK8GPWOHiuxyww23ouMn t4V7FkUd1dOrnQrHmRnAyKwgD/1I+3gwVb41pgGv2mshb3SJRPbPbJ9vKUdav0B4 j/ZZp00xOh72eUUvO1MrI4oLtSg/0OLb3rQWHZnoqUXiAHT+O3CoDbmmCRTbNyWa dOq+jnpVgMlw/42SSpESL8dOsgLUJ2qJGd/rs7p579WJsMPBYxnm4/HC5clflpfl uEauIiJtU0XGOLy8l5tH4nO14/HN3liz79+gsxD7gnR5HFTDOSRBU/p0zZT+55Oy QSBRdN12oT2awYA/Y1FcrCpTHGls5ecxDgppEcb6JLUDjhtP2sTLM5ClOMBl1nm4 oqOhpg8YjTPOLm8EHMWfKKnPZmy4GjM80b9wfgg+bgzLRyzRLGo2rgVSSljAcOJL F9wN5LOf6VltSIs4yh5+cRQdBS8muwXD1CNYgGe7+er5YRV6oZrThr1/gXxVzK/V iDQGNcy1if5znLhX78c654t5pH7BlOEQdTS5/yAYjoM23M48ZgLxw7Kqvv3JbJXv rtB38/d5600S05g5NYlc2TmuFGenv8SYtokzBmowCbaZSmZu3BghlmBpTS4IeVzH aELjGh79RQKfAgK8F+Bx =gH/l -END PGP SIGNATURE-
Bug#821596: php-net-ldap: PHP 7.0 Transition
Package: php-net-ldap Version: 1:1.1.5-3 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-net-ldap package currently depends on php5 php5-ldap . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-net-ldap -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqyXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH1gUQAJq7BQF0OP3ImfsexQOwDMHh mdHbjSRmDObZETcOpvToyTPrOurH9C9cNb/3HZgK97/tqmSm/sZ4rvv784JNJbaI tDGDU6DxpRdbmMiXkC6eolvCojDgq5vb45H94juNBKXy7NYWOdY4LUDyIBFf9e9k yb6E0eoK1WyFXYEGMnLqKGPUQeog+nhj6SQp5oyWvlv+ox7p94RmvWC4uah5thA9 JUN6ChrxKhZN7/lv6SL0AWnmKbngsOWg3pk/V7iYfOE15jauopnK5V5e7nCnxHRI eI+GmAsqIt9A6PmTl5mPmRTRyd7eqUUP6isk2kd47TPssWTlSaUvtFGBR9qBrwl2 pJZUFq5h+BghkyrDTTi2OWqDe5trSCf+1l3SOfAaTUtn89SfohFRRsJciic83+WS 2Qutjj0Db9pShXAkxoEcaRW3CiVMMju1zG9LH8rUQ4HHNdOitT4qnE1QpkBiCLqJ dq58kjBWDN4keTZP5MS1fcovS5JBp/p7/uhR/Q4giDnSrCchHuKXuFmzTucFAfNt tHPIlxEm6l8oohI8VPe+6Ylcbo23L/grTH6ZCInV493nFq73+Ca8FG+V2MFX9Kp8 m/I0MYvOWLi3NpnSSuTqw247SNCky1n5kL3OqjPIvCYGa4G7y6gYwttQSJYHgGIn FisAhDIo9GTafC+LrN1b =X1IL -END PGP SIGNATURE-
Bug#821594: php-net-imap: PHP 7.0 Transition
Package: php-net-imap Version: 1:1.1.3-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-net-imap package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-net-imap -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqxXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH3mUQAIg5DY/cZ9ELkxElx3NFVgMx TEz8UfNZLd7nE0eUKW5LuvcmAtejAg8q3Bc4cE2v9dfcgUswkcC1BP4ylNS9S+m3 SbUTK+ILcxG2495N86LtXjtK8BZlATUaNv5EWxVWzUromiA8we58sV74+MROWHqF C2AUVGRm62FOUvL9GkXVqJ+lOHgnuM4BFzL+Ms29Uefyzm/ZxGpzgtXGk92h1utP H/1ZGuxx4604CLtsWHJ3Fs6v4RtWvHeifFxqY75x/GyyyA71+7sHNon9zvp2wv19 8m5erLovU5E4BEmcoLFICiJrVAPpkALHkAw310gxjfqNXSCXGHjZFYTyWSjBS09q Vz5/RuwWlg8xM++mPfnh0skeZKNDh0gvI/WDF6KM93iaWHf0aySS3m6rJM4N6wC+ 8JL8A8oacTN6LyuSDCkQtmhzVfDt1dScsXxmUVMdJGZUjY6pG50ZMtKhI09wKR7f y+58E2BAJ8WT9aC5VSR2k5uPsRfxQ5rhUTBoXLFaOt+IW/WBW4RE+2HWP7tEXct6 JdQgi8GZ3F8dvpaivAvb5KnfAgLncU1dczSEWkBRoG8KooOwFFootjavddYM1qo/ BoD5NbUYSXx+NnrnBgUmgxFZqd4PNo5jlwQt/KIa7UzbyMdpneN3R5JAjncp+PtD f81UovdzNBREH4w+mdzn =GeAm -END PGP SIGNATURE-
Bug#821598: php-net-smartirc: PHP 7.0 Transition
Package: php-net-smartirc Version: 1.1.7-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-net-smartirc package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-net-smartirc -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqzXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHe3QQALZNYZ7niI7qCGacD242ZQD+ 0ABTwnKuinWDwqFH8kujp3u5qshREi94Lv41Hl8L41nFK+fUjUfCC+77Q4OAgEkB YOWwKbQsblIzP2yMd+sdgjaeqvuPFKrGfxZW0eLFBdiY5QZIMFoC+BWMr6R9K6wV 6aY+N2cG2xxUYMPCOGHa+9pDLyF+wQfGtDVh968wKO4RnXQ3Tnef6qUoCMY4wm4Y aJ8rWY1bEaySGMDBsNUSgCXXPPB+ujiLwWhfQa9VJX1fu4S+/nDDMudvUiBY/NF1 4Gfegi9fFksMLLBZQdzh60QVlb55RokC34YpMyJTFApXRRR9bk5gZp3Agcd0bttY mETZ7DVU/10mKif7RIX23NGmXuGix/oMg1ksYbJNe+SqmUbg6c/wLPFwPg8x9yiG 7m2sHb03Y2J0t4yppSORiF+cQpuRFopqz3mrWVUg9yAzR7jYRVLDy4uS0/R4Gv1F /dkcqLzkVIvHkLxXkX3yYsFncemAeRV2Fl5QOWLPsuHxVLqJ1Pe5MlHonFWzDTxK Npgr0d83On8eYmetvjVJZtUqFq8KetgHP2c5w7BhAeYw5DRp+rmuFmYASVizWS3z W68SSZYUxlSrNodNpC78ZMNtX0WumyBSy894ZEGo6MeulorRfCn/5wi5ADPiLX/D YmCXUfHGCJOGdBNr0ZDF =0XeT -END PGP SIGNATURE-
Bug#821603: php-openid: PHP 7.0 Transition
Package: php-openid Version: 2.2.2-1.2 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-openid package currently depends on php5 php5-curl php5-gmp . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-openid -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq3XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHMAsP/irYCLiNu0N5me9f4m3IQp8M zvIpAXZbCbTo+paoPDBwZ7bzh0q94l+h2Le+v2cGSV3oZb2ko1iPNwIdQZcSmgGp Lu6S46s7AyUAdgOvswdPNL7gyC9tpxXW+RsmOBmpJ6vWKvRckLKdip4kZGPuH7S5 4r0kEqLiDPsaa1d1X3N6Pc9dxFk7VdAAsCMFlUJ2rYpXxZByt6WDoL3lb6RSloRU tf4r2NSSDsfZlZ3I48zbdzsRzk8NAr5Wp8R0MkkFQACYuSWTxrx5zXh61R3t3usB y7EnmXguk8QNkZLQ9pN8kg2N4NEdx2I7rCOfzk2OuUDQe+DZ4Y7daTIt70clKMCF Yjf2vC14cjouqc2+LSAiGaR7zwkoAzhrCf8fsSKy2MwNV5GMXTg82gNNFYZrcrdU q6qbJwidNn1aZ9RiqwpqxhhOm6BQTEQVlQMk8wJtOrIrzPgJRe0tmtahvjWEHybf Dc11ckuRW8V8niaR4N57ZorJVAbWCAglzuq/H0DHiiAiAjI/tL4zEzjlGF0EgBnO 1kqbJFZMPfAKAUoNYV2MoYnxD5zCzSj70Zeq6nnzyAzLeIUjdLItxp8BBvg5BDRX w/1weYZICHzPicv+jpdIjRkFKYiu7ACrD/K58eVY0S2LybRt+2bsFCTMuxexe1nc 0Brxyv2WUQ3u6pAqu29F =UH7W -END PGP SIGNATURE-
Bug#821595: php-net-ipv6: PHP 7.0 Transition
Package: php-net-ipv6 Version: 1.3.0b1-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-net-ipv6 package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-net-ipv6 -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqxXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHRVEP/j8NHO7qQKfaFtyINUivH71K 9FAieuta3ZOS0GsPBMwph5okXaws+eH/Ig5A86jXzf4CEIs01FJf16dmwjTWSgy5 WLPfm18ducAXF3mZXHFnNoowqFXW3da9Z6yWgC7qC83uBXo9GekU4cEdY/RmeWO2 +6+cC5hlm8N7hxuYGxSKTgqwCBbqXrS1onIgPXNCs4Rn46IJCwKfWh1E1Dl5kX6c ++pWtsfjUDyYrl79pTf5lf5+5LItULNDX61mHP9Defvca1VQJ4hMM4XBfpvzSlk+ AXc7PzrISwtYUZDvgg+6SQIavzJDXU8zAG9QWSMy4etuMdbvrsuJs2k5aUuhPT1F eS/X7DqBrP7gHEBXisCDrV7VFKHNGd4SYHQlEsne03xvkfpjxE3ClVjR0gV/W0g0 NfiqYnr62/6jQS+W1MOphfWqISWOSnoA2DrYZQA9tmi/nFGLKiQ5iOkSeraHxi9E nLpQYV/6H7ofo/f8SYQkZTbJnlXEqWROJeTqb5allX7fbjtUVMLcrW6KZoh+DlC3 0U3YYJFgql7petbeHj6zLAW3EZR6tIHlIGhNzojjhwDbe41WB5uiXBVLZJdb65Nc 3iRfcI7JrlfEocToPZHNXzCPwuRhfYG9Ojc7CsHco+8/yJO1Z/3utr3dcQhiBVXz F33qZ9fZhyoarb/YCUit =xNgc -END PGP SIGNATURE-
Bug#821593: php-net-ftp: PHP 7.0 Transition
Package: php-net-ftp Version: 1:1.4.0-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-net-ftp package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-net-ftp -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqwXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHnasP/jaZhnGxYyjSh8SjUhCx5lWm BNz8/lZCdN7FQ3YY0H6QtIECoLXiP06qmMrn98+RnsNhyBkCAT5089Q/sTCqaUIB Lxi3/p2LIfT8CHQLGy2peOOSSu1o4uBWprPEuKV8M2eIc9IBY3aguzamTCu33rml yU/q2JhXKg/fbMUkre7zGLv87wOoZKa27o2qAR+WM/Ag7CHsXowvx5B8CdQQNWCg paRmw7tr7/r6bvBItRLDPTFPAAHcYqd2o7Yz73SCsD5flgMha1SfWaVlVjy1gZ5F ERTfn9XvvmGPnpVvjmVQGNbfDfIrK/ZDAwwWtyGXcgfnHK56b3gzq58xp7njlpNm zIaOf4/bhoF2E3dClatzfeuKQ1Gj7hlW40ZxSN3IkaNCdvyQ01WctYk4xjeOOPv7 kBWc7GsLcEyJyLJufS2TsPVqAEeZIKDDzN8f/F4Lc7mbeA64+eZ+uhyyuFJBxsMp N0cdWpr5xk/wMhI+srgU7VEbvdrEiGJ+SGA4qmv6VrQ2r9fKMl1HuppONGpUrlue XUcY2Xy9l84YQYccES+CKR38EuQwUTb8zXzqip9yF68A+fLGTRFY+o2OjSDG6gEc TqU9rUOCapdiJfzA5o5jKEmeMTr1VWNnnYDl90bndUw7vXmzP3BL9AJmzY/5wGc/ 3TdQZUWiYZLZf0Iur2qT =k23w -END PGP SIGNATURE-
Bug#821600: php-net-url2: PHP 7.0 Transition
Package: php-net-url2 Version: 2.2.0-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-net-url2 package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-net-url2 -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq1XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHEYQQALTDbEaime7zrAhGY4CMgaZO jFDhAQvuMpxNn39dYpbzX1rtdiiylaXQLR37jbOst7cqWz4j9uy4arH0BbRa4ku3 KLI43ymVEbzgus7PzNDVGhrUmvw3yOhnVG+Y318fFfo3K5aseViLoOzCdO/MSIB9 TA9CPJKjc9WCJvQExLFJWI3hTP1tNkz8ukLZwX8TUHT8Wo+Zu1OfXOZ1nwcwJpDI 7NBaeMrXxTXotKAmTnLNqQ+vobNlwLmhJJNuqVsZs0c+0kfeA3JR9uwD7YV80rt6 KHhF1glHrek/KBDop6W/xFIA8pxoG7hepCwGeBSqdcC/gN1TQWuGVGv63GDaQ8Kq 3n6DFqG2xRa9n2m4k/vN20HQIsU0EHVRJusWPSyJ+3y5hNwDZNeuTQGKC550/YkF 8EXoja0Xx7F9KmoBcRI3Sp0Dv2rTNJEZN4SwUYNVz/UTfXo7uHY4qaBIecFfStwu YGJna7PirGz1z+9rEG7S2EF4sQoigAXWRlWADejy+heLLA5YKynzOegbIrbRVcsa Aqc4mRsDvBluD/WIuFQ8UlKekNZIzKXu6q3zfI0zczJg4ZPYEYbL8EqbsHAQ4SCn Ylg6o/QwTNF+VyBzfRTekZXI6li8729HJxaiyib+8ls2Ia15rXm0ZCg5FEKryC4I CJig5p0CPPWU2msgGZ32 =my1I -END PGP SIGNATURE-
Bug#821597: php-net-publicsuffix: PHP 7.0 Transition
Package: php-net-publicsuffix Version: 0.1-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-net-publicsuffix package currently depends on php5 php5-cli . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-net-publicsuffix -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqzXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHyjAQAO0sEXmlGJ5rsBn5G+M6kL4K ho9KaU/cF3JHH7Ffwov/5+NCftvhlhU6LieIlt9ai8I9O5aVWzGomitAk693akZQ Yk+C5FLMUkYv0tPAWeOaFqYPo6pyVKCYYFvYNca6Wm19SVJ1nHsFNYTviT+4lPUR EZ7ihO6LDrPbYAb3kObUZRNfsi8lPQZUrLrZyE/PgxPBGPr40D2N3gZnKJ+mY8xO xCWJMbRKJMgkMROSkqi80FMnPz2sDsYYbTmcr3UDeFdFVKEuseNmuLJvCLk20akP fLm/+OJWa58sEACD2mXTQxinflMSIDL/ejvuenq09LZFZWxpAdqTA89WevzCCQD0 4J3wzSp1PTHaJwpHL82+PHKXdbfUteS+FEQk9wb/o7x56ITdfsierlCJ6uxW/+Xx tlbVoF6Sbg5NjRJtljnryB3SQZ2pvJqAQKMH1O51TJz4J6Ihw7xRNDUOZKedn84y MUf7X3TBNAJCebApHNrSPC+5tLIIEVJbIxl9uUinPnfqQJLDVs+ILDfp6I5dg2Xk usAta5WkQfBHcjfipCo2nWMp0QYvLxnV9OyHmnoEAbV1xQpUyPRAUDBXOzfU6ksr zULNQEbcbA1fuLQBGITAKT1/5Yq3Gn7+MaX9mfIboGTyioT3dcymnXMfh8vHgeep ZMUfTLLq6+Y11XUuFroc =a4WS -END PGP SIGNATURE-
Bug#821601: php-net-whois: PHP 7.0 Transition
Package: php-net-whois Version: 1.0.5-3 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-net-whois package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-net-whois -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUq2XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHWv0P/iM9WxG2pKErRlv1IOvvCmOt 6drS5QZ0gCVSnTFBpRJl/wY80tss991UAYJ3QMPQufJVPQBS4wENxA7tinLd8d/z w56IXVIZhkHMDrx0OnpOdvtGj+TJouoYUnn5gYsx2m13DDjd0SMrzyCdETmK5/+U og9wk4xhsCsiBvqA4l9E7KFRX5C3qOs3BilBhkgMQIGtCoemOLdR2S+P48PGBQw1 dSGOXyVoz0tRsFhRc0jLDyq0k22yEKgyvtZbEF3Y7SxpPhLhE+UQgXWuxuYhkBAh Hcc5GEp8AIL04zq7l8TlPHQorfKURoHzutztiyoELP/On+Bhgx64w83fqUtMJycF 38nip4YLGSSaBK0VNQ4D+/5AYHa3dwkZNFYd2KXUUgDRerVPxLUH4jrdCPXMb3Av 9Ksb5T9Az6FrcA4rSNzhwirQpZMHZcDIMdzkq2GlMme2oeYDaEcfz8kK8evMdTCA b2kM2uRAbemLH6zh3DKGX6Sc8rQwDgITls+/KHAdm4WPFCyPuX49DKQ33x4YqBj0 cdHvIlRGwNnszbihI6PP0kmwOqxDT08Jd9l9X8I7qRrKZXvCwuBd0E48ni3n4Zt5 wLMu5Vtz0+RcH9v9mEbkQwT6GTVF3PdYH7D159Vc12zh7TNDpcOrsCD1O/U85U0B rB1PB5CwE6haj1hPZZLe =fyRu -END PGP SIGNATURE-
Bug#821590: php-markdown: PHP 7.0 Transition
Package: php-markdown Version: 1.6.0-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-markdown package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-markdown -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUquXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHsQ0P/jyDiGhr1Zjle1YqHNZ8u40b BM7tEGyVmnnEIEFkFDOQCGJ64NscEkxAUH3w+2dGaYUJqnxgUkZZEQaFW7oT7exi NjwgrBkqPriP/w+QR6J8xt1YH/JTWQHl38Rj/cRGy8ASdUhK+nZli/lv5dCX83HH /7KHP4EtagB+4faA8ylmmir1MiUjT1g6+u35S6Uq5TIwUj7AlhZSl0N8fRQdotPu THL+lGyUnEkrQ9lUph84I2TbIh4ukCIHhfAKfeSnK7NA0yDn5Yi0iZEYP9wFp/GU R0awvLQ5kR9hyKtrODiqqi4I4E9WTqCUQA2WZeS4i5vGFIKlVcGVV4Lx37Tgnz9h YUcejEdZkERBoFFIQEikN9yw3Y/9ABRy0RIMs0gLJJbi+N3G90p0uSXUaWIkvhIz TXoVk1fwJieRs41A8KGbWYR4gZ/J2ySaC4aeZuuG4z7yGCfUTQg5TyIoTZgR0QLM d0ErT+B0FdygcGyHWAxZ8cUZcwAvENB+acW3NQjL0NeZUFb3ls2GvuGkJfaICnsL bWdhp8ELwmxsW/jfeRRzyMRRlIZvoH1jvhBZFpHNJ0miHdtOiDAiHCaxpJAMRCer 3fxw60yA0szy99qLBflrcWCfm1q0NrrwyeX2zhnvyfTLtBgmdFD32mVtD77AdIID LI6MMYHinrnKWcMT2wR6 =Sler -END PGP SIGNATURE-
Bug#821591: php-mf2: PHP 7.0 Transition
Package: php-mf2 Version: 0.2.12-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-mf2 package currently depends on php5 php5-cli php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-mf2 -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUquXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH6hYQAOZZuZayk8actCQR94efIImG ojoykwPsZDhSxlwI9uJaSfhVMlJRYIHkT2i0TFFfitcUxjElZNF7OzulVdcG+Idl nz+8wsaPJkyA65ta+2JybPnjXS/W5fFB9yz9NU1H6jkgADiyGnFWURqhROow3NrE 3XK0+WZ9WiZ5MfVvYXguWr2I911WcdFVFh2N5PC0xQNqpfQrDuccC4Cnp0txp8KR 22C9rnoLjFnPqN4/cXCWxChyKND58jl2EctF4xO2JPhhZG5kfv4ZqoFc1p0QwMCm wZsuSrdPFmccnKBuK2f3vUSFXy4T+0Z3lYTMayWq3YzTRuctlieuB8a73AX6WPE1 CxYpT9bgOtaQCTrJyXTBZA/zClbchHzjChjL6doeeQhKi9nlTlYMwWC0fWnXzOei Cp7OcTnH5j75CvbHcutKw0RYrGuavJtcRsXLJ42COvtAMf0vrXkdae64grqdYWM+ ORpgXyrzPHVcB9R+z0uyuhh/GzGeC1aRDnozUS6hY7Ijly3CCNxcLTYJzzimw52M 8LHNvBUXjzMLLMV24U71OgL07vb0w1hA+GfPg2B2OP7AZlXdP3qQJPepgvO5rPN6 dd4IMiEmCTYgKS4PByFsiSsDkyqTkHcSs6bg5ieO7Z4K1LfCoBcYEUUxlN86Jaoh l9Aw02o6NZcJGjs/IgnT =DX2+ -END PGP SIGNATURE-
Bug#821588: php-mail-mbox: PHP 7.0 Transition
Package: php-mail-mbox Version: 0.6.3-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-mail-mbox package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-mail-mbox -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqsXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH9tAP/0iotfR8Dv1mfV3C0J+h7FYp 106sYt+upYJeSxntQ4W0MuVpgHvesTvbmVpPsk72q+te8AacNIHCbX3ScT9syTcv WyAIfEGIPGjimqbUDUZr6tYchlwL6JhsIF42R7NB+FrD/zr98cWJtn9cgBE/v2yh 31e3gu+kIh30gXR3aj+RhXnatbllfgfje6u0bUF0sfbOrf5Y7ac5YvUlUlwBOPnD UJyjgu91lYqIecteqf+XaQbyt5aLG3OGY5Jd7g4jFAP+iJ6B5+HwamcQ2MFrSxYy 1uGnAAqnfj5+rnFoRhgOpTmwG8VxcyJiSiKCzAp19OYEdBwdwHawwMaHHypSzuSY ylIyNz7c6+SEJR1xV4T2tUxWRAlwGKtIj4G6qeVStuCtDNa7iQKp4EPAb5U4O1qi AGU45Uf7i81EsD85Ts3B1VeIy0VMDLZBOrBqjM7M4hY2DuJ0+nLB5dFynw6HicOl l/S26k1ZauDuhUhqs4Mh/c94lWvLAnrKQWJ/aWgTNrYFqoWc5dQRA//ZD5Y1DwKw vyZ2sr6Gu9OnjMAWfrIFVwtv9cbMjdCMZ58ApfRT462IilnYzImEREKTNoJS/ZO2 rWFdMJUes16ZhoMVWG/ai+t7Kt8WLCW/vm9tB0hPz7bb/sHCiv3pYToqeAOIX82K IS8037G9IRMWUgUdwUPK =gHK5 -END PGP SIGNATURE-
Bug#821589: php-mail-mimedecode: PHP 7.0 Transition
Package: php-mail-mimedecode Version: 1.5.5-3 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-mail-mimedecode package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-mail-mimedecode -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqtXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHW1kQANk+CPqx4NjoG/relbyufzTb OLmGK3uCk4bdmqZ+XtQVOtK6IZGSHcZJYpGBg3zmeqCngNEVeGdzmFs0vFcXg59F ZSbFpvg5cQ0AEr/bomDOnpsDDxMki56XmJtnyMhNAPuUmpzzn1HsavDacRwh72/6 n4/iOJ+fr25gu0VEeU8Up+/q+ZkmcUjBRYQGEpbX7NJq1pMhnuVok/iTFv6MyqMI 2B10SXxYXBbcPh9U9kI/Vox5QlBXCh/pf3INx4DtWyweoqnXbnG2FPuMq4OBl3y9 i6+jO8k/u/Vp1f0mPkbF+3HNY+jHu4t47qpYRmkbZtquusl1TjUUWISkd54eXMNw Oj9bGbcYrp5Nqef2T2ousZmFy3EnIfQJcYX5Hlgf0rrObTzaJJbTmfcRVSgd2Eoq 7T4QLQOmWpR/GeNlsu+ymMYcfI/fyLKwoISaPdFzmuiPPpf49fx+A8SOuDzfFLHE YVZ0ROcTMxc+DiatJRlhqVvoAZq6fzE4ImJj10aqJroCC29JCH4paqa+pb/Em2yZ GlEA9zNHH9wKulO+QU9549jH01tAAN+us5McKPI/oTLgMS3dzXwEp7XsJ7fb0nrY xxpE4cQbgZQLEGcL+G+t0ns14Ftg9oW5Nkoa/5vcxo8eHezOplR7sqkXo2I5UN5u BCQ75IyoHbJyO46XiDcE =0pTV -END PGP SIGNATURE-
Bug#821587: php-letodms-lucene: PHP 7.0 Transition
Package: php-letodms-lucene Version: 1.1.1-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-letodms-lucene package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-letodms-lucene -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqrXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH9VwQAN75JUbAHZdL/RrkmKIumVRq /kOMZiu4cHLz1fYaHAPM/KdGAFrFw3soJzvahkLaWNxKXjE0dYzMK+yojXb4rVuB KJdyR0wtgrnIcmjQFAhQWNmYXbkzee2+jbjzaXXVofVw+/n606G0gNx+b3KS58GB t+pXYcDxXit38ivsKVN481Jq4PCpxFCXhuU5Hb37r1pNNC3LcxCDtUu4Px+8C7mj R3spZpk/dBUz1G5wxUz5814o97QGudAo7OGFXaKVvqU9IlMZ5ZvpEn+d/U9ElM3U K5JORSXEEWl9kcmbIWAuSkMTGdse9AlXWcxCgUyo/3/gok1w2tkd/2G+ErjeneY3 yhHdmi9BSVUait86EVK4wYnv+lYC2HHRf81KwpA9C8snW973aIs6ATUaXvqRzUjT bsEPeDlZE0x2w5FEL3DPQ6yHaeG6wR32Put3ABFd6C/6YuVHUoksGsQp4D9PUf86 a5uaSnLqTN93Axr0jzf71/FdLljxKvVRr8jA86G8HP7WCTyfdIalomE/auP0O4wA H5GWbAKp8C5XLjFX59QPliscHJJpMxwAZLrz0roYcBvWSp9MltlkQryPjtIH5OLI hlA810tMKYz+vHuKO4ur4bPDzeGc/DFU8Vo/Y6QyVTrAPWSVrtEXcZIF8o2Nb3AR 4C7Gw5O2IB00+ENsP7mq =q/qb -END PGP SIGNATURE-
Bug#821579: php-icinga: PHP 7.0 Transition
Package: php-icinga Version: 2.2.0-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-icinga package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-icinga -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqlXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHHGoQALS3E6JN2Z8AM9iVUMHh4uQe q2EmEM8OhPKwKjWxPaQ0HxeIj+wKzpB6yadvXhg3/Yjz+OveRxLiGiEZjEVpIoIl SQE45oU9vMbXuKDHiVEuJo72CAAiyRajWhSi0qaqRvRZ58MYiabV+qJlluNMtSxb qALBIn91ZxXZU17LoHOr1eUntdTOabKJ8wwybnOK/zrDKoix3XOg1LBZA0e7L+wb Uj+2ZyGWQfT5uz8E7gLUKwhSJQ8iLMEDh5732FnmaIWwqQHLn9tzczPjCk/ncurT ICKVeUNki+NYXnDBDJLkTafepsXKTb3t5RLBqYa7ER5QRQ223dIyrHMMU5plUwTU yy7NUql1bGUzOa8+D5qYYUz+FeYDMsTCyALDg+ag8nURkeRMTd9VfbIu5icC9tgp +scw7gOD4iN1nwgginnme15m2laSxiM17upF3CjAJjiuLIxAO63QSLOuB+hCkAfM +5Wu969OpEC/avpjvMsnE29QA5mJHj5dCuuIKPfdi9/Xfv8GoyK1I1kCmJReLOQ0 omEg1W5pm0WJvKdVfkFKzK8roMd/8hmYv6xLIcwjoVB9W0tofVgsz/R2lBXoVw/H kmGbC6gq9GBjeZ6otOcOSwN+l45AV3zXr5LxXBgEZAIiFKoqDDYrXZpRIJixH5q/ tGgfjaK9vneiT6eWauXr =uX7W -END PGP SIGNATURE-
Bug#821578: php-google-auth: PHP 7.0 Transition
Package: php-google-auth Version: 0.6-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-google-auth package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-google-auth -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqlXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHtqoP/AmpBTVLTYlGLm/A/7k9v/sW LrRcSlHUDz5EF67Gk5ZIyPnAa1Sq8j0HqTwJPuRJSrHyOokKySNaRme6iy9TAEf9 auLdRxq6VzPPKsjGhANnleHmtEKqNuCZMuHCf64wQkHojecYGuk7O24C89uwDGoB 8zfNtJTGnXTipik9zzN2do18c+YJV8TknEQtp1NLPX6BYu+Jv95ol4awx68P6BSl 1kTTPtIITxUFnDClcPwHYVDAE1AxQbE/T5NkPtWuCtoM6cI9L4zmoIrU95sFfJXm 2NKJxh/nO8fEzHuxdgf8aIjAoCbCwAtKujzVi1pTgpDH1zBjVjhIZY8vDQ3VOruO s4NJm4hajBIWkJED3tr4MOavEiVYexFIbqEpOVDhvpLyEuRfiYYs44J5DIUkhCY6 qwhsSUgLNv6+cnks6q3MM5rN7FXKXjZCJrp5BuqdgfoHR8wBHZuI2Xsgaky53K9K 2HfHtLgym0l1JIGoqfS7h5jhmTHO5PKGGm4EA0svWPJMqQr+sCA8t4gQAkt423HV 7Rc6c//P8CfstDvkOwR8XF2LQ0mXVogStV8G4shX3o4fVi2PTmtlNnkYiJurZnZV YIUON5/qO/vBYZjdylpa5B/IPjrRWZ7hTS3SN/+LiW7QPZN1oA11hcV+/c2k0Ko0 20r+H3YEUXVi+7pmUg5w =ZxQ7 -END PGP SIGNATURE-
Bug#821582: php-jwt: PHP 7.0 Transition
Package: php-jwt Version: 3.0.0-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-jwt package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-jwt -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqoXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHP+wQAJtUGdXTqPMiI37cU5yGZEUk GrjEOgofkGddBCCj71WJXI69wh8DwYFm2sntgJ07cfN2kEoZY8LKaXyQE/6rjyqQ we1StQagWj8f/kr/twxf8byI5bPYaQqU+vIz7RssYM1rWasZRT6djqFjg9aSMn7X RX6niLNNOO4NKkYOpdG3uewu7cfsDwgREtbAr9nU2OVF0sMgcWzmK7MxbWGU9/4+ gb4hjyUqJJrxOuI0keUKThTZ5SDNhQJm4on7Yk6wPcyY2eLbV5BUjIZCC8HOywB3 4SJ18dWuNhype7TJfBz38uhDtDY9o29SfssLdxz0btzcZjtFHyge+C+FdnXCnRmL zkEdAgYY6krVxcwHfVNyBLG6Uiu/1XXAJX5IMolcrjhhUXt98d5pYRUSsZFVAGyV PQmEy+luURR3/zpRyuSWamC6rmWgd15Yh2qDjLSqH2c4l5c4ZUuQTlo6xVEKSgoi my4IjqisnjdhTlEK2aulqxelToLrIkZ2DccADvppYlRpQ3dqpUSusgjDTuOApBJ5 LyWCwuUkiqmRXbUObMetlNDJFU4zuw2xvuq4dtGMTMBeeaPDJKgvcZ48SDZ14DHi PaI22SH0AoMsnlXZ5d8qSZLaNx8Ptcv8tzZSYPn/hvWXo6uxwssmpuKk3yL8ImyH oqXgV3QBFh6X4Jh6bkEO =dfaA -END PGP SIGNATURE-
Bug#821580: php-irods-prods: PHP 7.0 Transition
Package: php-irods-prods Version: 3.3.0~beta1-2 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-irods-prods package currently depends on php5 php5-cli . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-irods-prods -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqmXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH7F8P/RQ4XWuylhMA0E6lCasNARTX spxiB7vsquZ657ZTJNySP2tCweHIZn3XvEILvzpyavbZEfGW1FmPUI3GNlGMv+FN zlDIKwSjpvKwvUl0s0hs3ZVCERnBTxG1gImgpWKEKKB26yBGQMAH10ILlojtZxCJ d3AKXIExiNwBdywGqZXd98omzuz60D2JtfFn6cZHS0x3JRn6xfhFqT/toncYpXiF xof3Uq9XPStsyJ5e8eqjhJmhtlpwRrR0LXEANWwJ0Gcd10ZTKsdVUmud5pO0vuNi 6iylZ70QdaI/HeU5TNsu3a2pqJZAbhI9VkyhEzEHiH1NFJKNZS97gj3Wfk1bu8BX D+UmSBogpbjafIhZzhXksbyGAPUtTfDMJ3Vfw8dHEMnijyD9RKRQkAXUbjXsgHld hmFdbEhrGSWXz3jVhH54DXFyW9UE5smUk6TiuMbfBso1TsS0oadx9UesIG0FnWiL LMAhOohUz1TJFU51/oCp7kGZvBwfkpConWr2jUs35MMNkitYkGOA3TfDcEYNZTeQ uWhODkwjVZ9Ic/WkvoWAXah41G/4/ubQOqzQFS6gD6O7dszAkFqCodJfbs4SHSu3 +qqLcFfvRUk/2IUpHfuD2k2CMJuITd2Ykqi6iNWZPpF2wcal7mxKzq4kbRyHt9nH BKhLGqKWFidyOc7eYJ3N =FRxe -END PGP SIGNATURE-
Bug#821581: php-json-patch: PHP 7.0 Transition
Package: php-json-patch Version: 0.1.0-2 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-json-patch package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-json-patch -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqnXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHTx0QAOVWyj+Wt4lFBO9coI11+FDD E0+JLfhQ0dVBuZeMAAgv6tds9EQoWz8UnTNrCnoTgObfg5NQWv+cdOY4uATOFh0A GDYcJCzBRa1+U40x8X0iuHve2vJY/Fam+HT6+XTTFnh+3Vxsw7KcjfEyHX5pXusu e8dmXuEP3eqCPHV/+OI/b+KNCKP4MLCGIa1HeUHei+euD1uHqkzLNWz0StNyfHGt dvAKgTX40CtDWRBjBb1VbrcjoE/elJYdd0ADBUED8E5gb12ju8dG/YnRAmMk9LnM C0UMsPpq1aVgptxhrvV8w8xmM+cr6CGeW/Un31tydMiKqZCHYF2ucJ/NeDJX2N3A 97sJp8dSYl8sGs0vyHjyfiglYRFxUqcGvSAcYussmh/ZdIcIVjf7xZAm1sly2Ux5 7ifSGL+QZMYhQJvzTqRbCGW6hdcTJyQJgUhAS6hL6ch6ujHMAJZ9IhRS5puNgziN lFz2Y4hcgM8b3IZ6n+Ln+NiH+cU7nG3efXgGqzd4x2jvQ8zl4Pd/vfHAfcSy+HLP ovAnrqXIPG+TNIE6SwuK6W7fFb1aKZigYITyATIKduzy+Pp0eNawG3a1jojdUiHW 2j0STltfTHOxuFkfChsMK4iKYwgdDXrJ6hbKdzabyAOol0pQ+s/q/xU32TKK7XIS Dt/0q0rgqUk803o9SSDx =QGnk -END PGP SIGNATURE-
Bug#821570: php-cssmin: PHP 7.0 Transition
Package: php-cssmin Version: 3.0.4-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-cssmin package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-cssmin -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqfXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHm0gQAJeaAIFyaFsB0mksiPY84oz6 SHHWfX+x0SfkAy7mn8WavrWrzWK6Q3Mx+FEUWy9vfmj+rJVdpw3dFs+rvIiUgzb2 aXyd59lt4G4oBFZK3yiu5qM2/KezVYU/aukttdCatjYg7K2SX5Nu+lA4YvABqdvv x8GL7PenJj0pf9dWhZzeSjq1fERnru2n/b6BYpIteUF55IA6RGhxPm898ZgppNqi LNJ/S/BqJjpLF2BjGv4m3/6ZwDX0A1+vthD/DOcnjPyquWDJqZgJcM0qiEmasuXv Xm1lj4oLpPAGcXW7PbOCTpEVvbnhdC6ksXA0mulac1vwPq14O6go741ePqkvklWD JZCby3y8Ud6lY079QhobEzerdCPH6QAueH/kcylvoBesIIfg674Z5NZK9GDknI6m Lxy5vX2Z3LIuE/KSyP1E6or5N2bOONG9+Kw3MImnYkDhceqYFma5j3SoBD0YZ053 HUg1jYqJ9gIo+/26K85oIiUbLlR2cTpGyoSeWjwbAVUJguYFp6STytO/KHAn7ZFF cSPcb0FCqS4s4frLPPKWtR+DH904oRH7lqmvxMmFEzcXhyLifMcE1Y/1iBm+rOhC SxWgJhhE85r08AtAFlsCdzkG1TY4S13AfG98M3Dl8l3Zu7iM371dkLuntmEuK5iP J7NbausxzogudrJqtaSM =RYjZ -END PGP SIGNATURE-
Bug#821563: php-apigen-theme-default: PHP 7.0 Transition
Package: php-apigen-theme-default Version: 1.0.2+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-apigen-theme-default package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-apigen-theme-default -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqaXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHxhIP+wQ/zY9wT6AjdkHfzp7SJphC 7QCE4WBo6PSau31KMrbtFbVo5jpvjZ24uB2Ms2m5WM5KLviFK1D1V+YqwNTHlSB3 cTSwans7J9lKv/4gF/LvvgalJA3TK4oD3fooaNXhu0/iKjLNXjYlEIxiJu2MO68V fz6Ilw0FjZoKmRTmYUrjj4R5+19YVF9AtLUdfVGK3r89hb4IgHUaChc9IRW2dRNN kQysNzqd/fm8IRdVFe3RIIN3ETizQze6WOosoecjHRYG1ldv81kyYaKbnvrenI6Z JLY4tE7gOpOulB4rcD/jvHUb7OTyNRU01qEoVwfNTLo/PGWyX8fQ6cwfVL4u27bP L6jTNzZIVqhl4IjmpkjK9/bcE//h/SM1YFNp6L6OLCMu61SCst/tR6uqGYD3OyVY FtcYAhnbGss6bsuMYwSHm38SgCS/JcpsgG/VP3pL/SnMqjBZG0m7R/V/9WBiTeO0 Tmdz3C1Xb0VZROoulFfvCXyc8tbdrM50dYWvFLxWISWWrosXzl0FwYCqEe4N+Siy DlW1zM07a+EH/yiFCX28w8AdPsfhPbcUWzQhL/0lkmAJV4d/6foEs1zCPP7vvrae RhEdsSL01CAmWmGzr1j5DLsc8DZ2o2ECyTQSDP4nznfykR+4gQeYGGxAqKBzmrjA yHjAfODuJCGIK77thQxF =o280 -END PGP SIGNATURE-
Bug#821568: php-cas: PHP 7.0 Transition
Package: php-cas Version: 1.3.3-2 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-cas package currently depends on php5 php5-common php5-curl . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-cas -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqdXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHS6YQAKwsjIktdxkxeyFYJOK4tQay C7myXCc+sA/yEOrVd3oUXGCWuifEnICTPHEmXeyqc3nRYKF2OkFiWhTyXawEsU5V aJSouM7hvsLPnTTDvR5c8aYS2uk+9AMTWbr3j9RMGyULIy0zxC11xJdA9L/0aVTO MP8S4PXcP+vs29jd92DH54hdHTpSTs80IBx5SFGujlCOH+bmJdZJyo+wUhensEgm dpGhr3UlJWi4E4G5FfIcuWWdaCu+CguaLsCEbqEA5gQmfgC97uY9PP/yVIjty/YI zqbVrIs7uty3Afrnl+izaui6GQb4nkz+HVL1GCLo0Aca+lDga2+zeo/x3UwtIPj9 KOjXE8dHmt/kfcAbcQC/vr5BlNp5oM3h5hXJE0ctcDJHdG7OgiYB3beKPsCfzqAL AW0Zu0DwhnjN2Tl4Rtc3qEiSlGGYC914oCLsup3KKQEGGPvPPh8af54SVf923k2i sQepifgNMZpPdyjwrBsZVYTU435uuRqyIdqZXxV/PC5f991uV6DfvU3wbHZR7AOk lGx6dwPBfgokwu0CgQHAMYMMlk7bFdH01jZbgAXl4+yDW5Z+4BrCrUbSE4AnLcBs YN2amJAqn2ztnMrOYXBQNWLx8YNfx83lPJ/Qfj99I+uEpVAR0/yFQGMPz5uRPZec KU/GvSoUBwJhEaWg1WZ4 =8dfb -END PGP SIGNATURE-
Bug#821566: phpbb3: PHP 7.0 Transition
Package: phpbb3 Version: 3.0.14-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The phpbb3 package currently depends on libapache2-mod-php5 php5 php5-cgi php5-cli php5-gd php5-mysql php5-odbc php5-pgsql php5-sqlite php5-sybase . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: phpbb3 -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqcXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHEgMP/A4e6mlPmcFGewFGF0rNG2a8 mSr3fr0RCX1bgWfYCgz9fUTOgNf3kogXdonuHvRZahHapmeCugxISLIatcYsdEKW Cb+JOynhS/zdL6yGdlMoI2vhrLxt+oi98DUDuuFMWuiKuN5zHSI/W8EUVylbVO0h cr7modPG7bVxDEL5EdEdtXVALMQ5luCA+DxgNzUTLcyDi/+ydKQuQVfoB9nDv0Yg AA+MSg7wOH6YchadG5A27qvNOffgCkysrqf0z7VYNqzAFv5Gpo6NZ+Wcg80nPH/G cQK6O/o5Y5q6GHMfwfKBNqJl+162c+wTYbhEuhE3CySu6hhc5cKyK+YDaX8wllLp EmZ+eKgTk0hxySufOyFPC70wKG2opsxIl/qgaJo/PiYY5Ga1fUZBreoStwdBQ6ij 8Dezp1x7bXn/nSqVYX42TAhqe+v0xnGRDPi1x6GpRI96D+J8jTWWMn6tQY0u531n usAEibYLSLT6HilnEz/0Qkjdxc7GM/FzeV7TB21er0s6RlDQ48wGw4MBAVQycJj2 ChALTkHempSvxBw7KSINjRj3ZewVBWlpx9uo+oHBV44RsfZBayLHKxLbBKvfI9b6 CR1NEYdCPKVZa518xVbhtksM5MNZDafP5I0wQ+Z3hGBc6DHpClEJOvUWMHG/jiT3 HpFLLsGyFvlqRGscdurs =TAN/ -END PGP SIGNATURE-
Bug#821564: php-assetic: PHP 7.0 Transition
Package: php-assetic Version: 1.3.2-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-assetic package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-assetic -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqaXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHnYgP/2Z2TrMcNwalwj0tbStfgdSG 2v6bS069C+j/qiQjfQ0e3eSWMARRXpvixG3BZlVIkIZwqgRfdx+sbpuK/b2iwkVI WDd9L2AZMHEODcPUbWP1m4YTMBRGcbNa/AIaDOPi6rQsg3kxA4tR0kCLv+L/QLbI nI7T5tIa+A3JfaJ5owKLxyVr7zYbhXptxhpPrxl0CxXKfJax+5MJtdj5CHK5eQDX 2PQrF7j60Oi/oqEhb9XvembouJiGZr8pGdpG6nGH1kAvsNEAH/a66YaJA4CClPgs WwMFGrwmycLQQsGafA1e+QcmgIOuEQNdEq/giY6PygGushU2IuHRG+L2EEfuP0ls VqaQ47zEI8F4ExNQ/RgXIJUs73RA2mJMqMZj1+sZnp5/eQwVG59Ml9SkyOOhO8ZW jV0CQv+2wLvO/UQjPEzA9NuSbvD2PkeSUUCQ5Bm8LWrGDtF3uGpoEhX8JfEXhuwu 04mKsQdu3oI7s1MVxzYgoH3Qby+tTS8N3UvA+9jLRzs65VLAPherDMT8Pw860I/g S78vg+4KOkiAZCNQMUdQ4WhxjowqlFNAns/ig1FdxNhJuhscZpzsyR5u4ZQcfbh8 SjQ7myR0osvo8WQIolGpW96Mkc4t3zuvqNoEYb7xhwCBhSI2H7lIQVhxGcOsF53c 8hxkc2a1jx2cKUyvKle6 =lMVP -END PGP SIGNATURE-
Bug#821574: php-fpdf: PHP 7.0 Transition
Package: php-fpdf Version: 3:1.8.1.dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-fpdf package currently depends on php5 php5-cli . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-fpdf -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqiXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH8a0QAISR5udaN2NW5Jur12pP/zMt y3WrvV9kMdNz8EBX8BFGAgiHzzpqoOU/OFsh5UZbqQQsfvF5J2eBQQpvc5KkwAsC SuzBVuOZI8kQjhU/4/kw9WwKBihwzwSZTIUzm6ufaUfzttpS7RmWbw8fbORbEMn0 jC5O1urlLskMtCCK9qoSI4Iy6SvzNRzbohtZD1Rk5iV50dPw//7bsC2AcDB6lwam pa757IXyaoWbTAgAejgBBoLozCSt+kqBjwbC8jV20cCyXrdpo6D9dme6P0hBC+yl tEKyVfik0xKNtJIKTI7jbteedYLYTxQXMqyqhZqFRRnge1WAsz9jKhIpyRU1WT9F n7d1nHLd6DYcNBtSzA7HTwuw3k51Y43J7dlNaQMFYWjhV7LA+HcYXBxzw+OY/aHB pFf3vItHADIjwOUvqunkZyU11KfWnjPQvdyUVkNiPdMxW1ZFSfNxa2tw7c0qOGOa yh+N0KLde+khznCXsLVviUNuiEifstOK0aC1kfUpOpD7HVaDy6Ee9iwI21Z9UumT PxL1IrsTiujzh56ngYP57gC8wO4oB9RxEPn5lOT2r7KJCXMdrbOu5+uCpTsa1VRW FcIZ/gykA9aEIQcBhHRl2RblLyMuagHtO8tMWIiKw97OUvwISmLKQLfawkdk+zc2 hFrCl8CBEdaSuDmL1aIZ =P1D7 -END PGP SIGNATURE-
Bug#821561: php-apigen: PHP 7.0 Transition
Package: php-apigen Version: 4.1.2-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php-apigen package currently depends on php5 php5-cli php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php-apigen -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqYXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHah0P/0ZG6WNIdMSquCUIMdXb5mS5 Ph1NIKEg3ErgP0LBPG54BMM3KPPPz1zao+nVOmbRJlVIsckWmGLmD/EqFcNuzuTJ 5rjfxlOKIfxrJf3oDCwN8831p5AbFVcG8dtTiCr2fU/5MgHRtHQldYzj8vs0HnZm qq7AHrYVPsCP2hoT3d7I176wjPYdS7eJB+57p9m3BWerj7mNpmajPBSUXA34z3/Z 5zzu36L4UMB0/gqujdfcK4L3eDaAdvLeJWe9udyLtS0rEatWBl3+IVLU6keRYBtS Bu9BGiigPWJtaVha1u1g5Tzmqy5VcQxIY18RBvhg8/yqxxFNrFBJUrd1grff2AAh kX5iDWBpitpTLBR1NuZdLjs7RaDQAGIKeBUVYmFpyHg+Nb+NMLrt5qJbc0vIITuG teADCKkjMjS+Kbkd3kyPRWoDrjKv/W1+4nFPLiAoNb1UvDQ/QYDJLb8+MXKUUkNr u3PZTVfqgt5DP9uqTlAjPLYYwwS4/yYuJCoLdYWhDs8u3S1edBQoaIL4Q/w2RXHn 6y0+IMukemFk4Q9IQmuY/SP4EGnnf6MTP7bhauW81GfElg1KOh6dGjmaPupXMcO7 78IoAU2Z69P2O/IYg6vqlhAi3SiRDQIon2CL+7Wjer7yXHkhgiOb+K6TjkzW10ph a4Hy/z76mnRHL2ocBJ8G =oLgE -END PGP SIGNATURE-
Bug#821555: php5-ps: PHP 7.0 Transition
Package: php5-ps Version: 1.3.7-1+b2 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php5-ps package currently depends on php5 php5-gd . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php5-ps -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqUXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHTfcQAKe6l//NqI2sx1Af7pYnCzNd ELW8HiyGyoKLVFToFJgzhv4hpV8tlb6KX85C0lP8bQwJXlq9mQySdTX2pV+Z57+Z eyq9pflvgQjvolxL13VMcM4UNZGdiqGrxo7D+f0M8fiDD41FwK5nuUo/0VVcogjB 3R33L+q/OeUrRgt/Lh4a4mUs/2MvJSE6AqhECEUpmWcnNNNvvbhYRIcVK651K1D7 zdHjFbcuCziH+HIIyS3FsDL2b/8OJO2KY6+l8n6ocxL0hDcz5Fvxj3HHDR75Vt7e jXOdg4iQJ3CSL3A0Udi+i4PPQA04sm6Hb29cIE7qS75Yu4xvinONaLmVS7AeaRHe ptaW8CaBuCeS8N79n6eHwpnt3rycQLOVfuCuu4Q9XOB6acTyAE2VwUP61Bjr7vK/ 4GetkrgZkIJLtD5lI/nrmJ3T4CcodtwknRvc0quNoHXoGnh3fjpghPzwQ58F68Os SIVLPCpdIGlkq1EAuYtl6Z34VPyuS3OCjOBI+FhjwPV9YVsBfVa6EHAxCUKPlhkP Gmf1DYI52iuuXmqZF+mJ2pOkic44lLPl47e8wMnvW0L5zm4AdYvUVDxmpooKZAdL Olrs9G5pJ8hFzZ1Bauxpo0b+d+la+x8F6iXq9FANLVKc98lOA465XGYMlZVZ+wju /AemtZBqFJS+uDtYrC7q =g4zr -END PGP SIGNATURE-
Bug#821556: php5-pspell: PHP 7.0 Transition
Package: php5-pspell Version: 5.6.20+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php5-pspell package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php5-pspell -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqUXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHsmwQAM2T/MHNlWYqXfCfqroH/FQY Tgir6mOIXk+ADc0/CzwPyzT0rsBtKGVwu69MJve2rErSiSCtSVr4fwwzHGb71b0i 7GPbtxHx7YGe6Xe/4/jVs3GIXBqZmaxeuhvHBLisy7gdO4zYttxd0peUA+zI7eD/ 3ibQ2x9hfN8Vt9hai2pEJHPKvOKEsywq3ZT9Dgq2kAFUNv7Gs6ycIg4DVjfnh12A l0al4uarrvf+/WhEsGVqgGeeJ58h7W5q0skuxw0EkLEP8UlUd/kl8HObvmw0s53C jZXip5SL2ABq6jLJiyuPmQFKKtUILxoQdJVyt/nvv991EfSHeV9c7kwJwrU3eL9h 4DI/FrPEOou/QbFL2oWIYopMNxDAkRqsLBa1HckKn44AaKt8PkGPz/cLrooolUx1 1cMaMwYWOISLmf1LjueoQYLqUDskC0O/e2/LmNT/R+XqCP88fBQRMnxHhjkXud4q K1XbrVofmhRx3qHTBZi5v6YxH2KzjZ3077S6jHHVLF/wfonT+Mmv3PQaWki7hHf3 AXAk0m98ZDDCCLT+yl5QsyK96cE23QTqE6c2irbaPGpbnYlKfF8BX3O7gau7SDqp 0UYNHB4aZ6cB2ovbFttCH+gv+eVezDoVmz2x5QzmAUrrswel3P6fxpJ4DvhX2Ny2 EUbsnqROMvBuDjK6ZIxu =zHMA -END PGP SIGNATURE-
Bug#821553: php5-pinba: PHP 7.0 Transition
Package: php5-pinba Version: 1.0.0-2+b4 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php5-pinba package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php5-pinba -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqSXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHcIAQAJW+GpYLV4idWl+NHu7nZdW2 qc3+zbtsOXsYv0gA9oDI8jtkPT9Ulp0r7E0IW8PHf6wZJPG8ZHhHVD2q8z7V7OXs o9r8c4CBbdfQEB/GZRf16FC1MG737H4dVD9+pWb1+iA7B3lcLGvi7bc+7GezLhO9 MMWQEw1M4vOpCHMNplPM1l7ZV8Y4i/HN9x1gS7alFTyVa/fZTQvowU4xttMdlQYA bPi+armB+y8Cw2Zkr87wrNLL5EVj0tuvN4H8XOBRDs/3dt5M+JaX1CK5C2fVh320 vGAiARUSGAuutCYXYSi5qHI8NnFq1mvMNWyS0BMPfTaZXUv47jXKBJdUx4/bCa8k kn10f+Dcp4P6CeMQ2Xe1cvCSn9rOjHzTyXdp4s4M7hZUPgkk4upHhFcXBR0ZHYXM UFZN60HXd/CawOajRDwRXrza1xPfYzRq/4rUl4pdbLCJ89sTu//LolfmiTZ0uuw9 +bAAwG2Rmr98yYLN1XPhVKZi5VFlkDYOZOYsGat0+Aj7nvbu6LuOswTGd+rg0ViR hRGBns8yJaPvq7LzzUMqShs93Q/4r74khr6fpJYeMKg66WPLofzOWjUweY6GW2wG 0vhzyFDoM62uXN3DqUg0zm3a+tobjJZuo3SijnvFouTYcsLy7gAYIeD54Wl0bnW3 ntdCldxwyQXo0I7ihhw+ =7hUP -END PGP SIGNATURE-
Bug#821547: php5-lasso: PHP 7.0 Transition
Package: php5-lasso Version: 2.5.0-4 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php5-lasso package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php5-lasso -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqOXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHqvkQAMkc+r1C0eQAJX6TRO8+2tmJ +64YWJaNru+PJP/k2enDfnuhd6WKkAfvfMginNy30KvA1QYbk+Puirje+lqk8+PE 7Yt4XpST3hgB47NEuDEc9fFtkuTBNiu/YReW61fgMi/ZL2wZySzgwHX/KSC+cV91 JM7eBEs3btzsg3Rmi0EuojIIwGsWruo5vjwHILBFVqUYxFr6l5jPIsl26XUUh1ZX lHHR41hf+J56WZrTMYfyH6aENuv4vUEImQawT/qq0zM1kmWlDymdfzA2JbrCE6ea ycMqjOglBzeDbdzrRmxmYPBXnDXyB/4MsbiEXdchsXEqk35YSR/AXy1carPrwIBT g/pSrZJ1b0kWOPuNRklq1Gy6x9Brg9DunKGCSzEUOpnReK0X7ApPdxzir3kGxtit wo405QE3z3vzwxXQjrfWmSdMbqqMXVCaFbx8CUff5E50gs7wlfkG1to7brPIUH7q GEAP5uPCZdnfIHuZZGsgKd6v6bozlZh4b3xzXb3hU9u1S9uUDex6aUm78SrpaD7R RREKKLNWEKHq6wP4+VHzJIWE++Z19kvxZaK5luVhXb9jWfdUbPFNGRfvhkiYYG6B sEoJ24HbjzD4prt4aan/DhPfNS8jvxxsqoI21hi9cVOI2odKerhDNdObysSxap2m CtwyFfIE486CATreo+rH =IgCa -END PGP SIGNATURE-
Bug#821549: php5-midgard2: PHP 7.0 Transition
Package: php5-midgard2 Version: 10.05.7-1+b3 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php5-midgard2 package currently depends on php5 php5-cgi php5-cli . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php5-midgard2 -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqPXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHkZ0P/j07eFN6GRQ9cf0yaI6cYqJb QWYZjnlJmRv506/eQ7TMGULzQDQo/d4VNGt5Wl6vJA1R3JpepBwcLM4kBDoNA5+h K7gg8blxyHsw7akCqiLR7K1KDXugzek6uwfYYSmBoQKIKpwW1wNKl6c/bSx4d+PN xCbqFX1mhiIgbtxNvH+v3pO1qeE6115qPVT8kwjbzg92YD+W9pRT478dHk57LX+S AwQylULai1ba5AeDYJ55ZawvZqY4PL31aCcic+ASQiHa4A1e9YeLa2eoMbEthvzN sBISOVfkPUEmtG5UFtW61HuK3y4oBPF2Z5GAL2eYpOMkSQwhWEqeCDk6FKY/7YVE bUTuyMRYqdmNNN4/OHvDf8HW5ikzrhPxmWC0M7wG0sGpz5E62kPBa524DasRyQ6F YxEKfr6tqC1QdAQPRg/eqYZ+ZDI9Dumlm4y/Dm89lGTCN6+xOh2kti5VxKlkG++v ABhhPpxPGagtWL/sUJ3GPCMEJUi7o2Ba7TdoKnWW8Kw7G2A6YxLglXpyCg7l0hSy 1CvcghpervyennjKzhPe8m5OC2CLYYHMa1xeEIz7A0tN2cHXCjxLzs3+QkBF4PIb 9bhbrTcuQkV+WxrP4mozhay/7ioohye2Qcz5BQIkbJ4kHzpf7despKkCcuabbOUg vNta0yDzhgHn41EJB3ms =LE9V -END PGP SIGNATURE-
Bug#821552: php5-pecl-http-dev: PHP 7.0 Transition
Package: php5-pecl-http-dev Version: 2.0.4-1+b1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php5-pecl-http-dev package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php5-pecl-http-dev -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqRXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHtSAQAIo4AlQxtbfCLs5dMZBIeXSs SiBrkdo8/YvhuxtFaIlz+a/QFDU3D2gx/90hP3mI+o0v9rwKksfLZpYrQlmed3iG Ayf4dC8lNmoyt+hmTGrqFBEXVT1KfB3wQ5p/gobjPQ6bW6sDIcJP0jVg1jMdyvQF J5ORlyxOwlIXbzZD1f7rcta1Z7rZnFaiVdOMVTsmOjx/M793ZafFWpDY2Ph7xK8x mwcXOP9MKPfuryliFPykNVhzn+DneKIRzWpMN/MVucQk8V6ZMQayv4MhOEwHajkq VgHTlkn4+S/pcTS0Gb7RAE/A8j76bdTea8hxPA3O7jqN8tk6pl/Zz29jAmxPr39Z vI0dXZHBRjO6R2i+oojRIE2bJ7OyvvZUwNFGlcog/P27vcVCv8IgujrZoASyxxMr HNcg8JPBURZ2EfWnVNVV5C44o5UU5T+Auppz0PN1EC614JzsWezW1zsSc8UltkCc 3/Xhd6R6mwvM+OF+HIXahRiHYWEeg1uAJZC5qjgiiL60Hmd4XTkPWStX6sLC4NZZ alQly9IGQe5efn5zW42SzTXNBy726fW8MdV+VhmPeKSEo93Io99BXPm0PZKUOP2/ dPw6IvIe5EaG0ARTEc35AjZMTwDxpZHGNz7wznZaKD1Tr2gFjl9qORgmvHqjG04v io6pSiY2Qkk4NhUbl7z7 =4rkB -END PGP SIGNATURE-
Bug#821558: php5-raphf-dev: PHP 7.0 Transition
Package: php5-raphf-dev Version: 1.0.4-1+b1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php5-raphf-dev package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php5-raphf-dev -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqWXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHgRwP/RyW4TCtTf8knMcqjO0awFws Y8ge0wDz9f00sYQNTAes8Zfh6/s5GYc4jEEMOEAZSefBlwgFL89mlJE++2+XfKNg 6PyRvupwdOHZKKwP3D/KXRx787B5RF1V0FtOSJ/VhWhp4zQnH+AvPCSxmUmE47Xy E9MbwxbWGVKB2zlTbbE9SOqOwhX8Yv3sl8q0Y/zrUSwUX3LYDSFuNmbNYqxYhzbY CDCMu9Xb7bz1QuiS3mH339oJvwyNRTWTRlZM3qi1E+V4FGAtsvQmz6yAhTsngrmE amBfGFvSt+7kFGNnB8bntyUvJ61/RBxOKmq0IIqEQn3Jjru8Mj7lWpZJDwMserzC 3vxTWtwqwXWe/H8cTIDuAYf8NL8o2+R9EK16L7WqFIZV9+J4BHjX3b4pVAffLaRX dT799x/BGaflf4axJVQKLWzgRA2XB9c+K7svgoHZyeEKp4pk3iIrqFAPZy5D658f YBdk8rUqLR8nr3Qnr9wcoMa+fEM2fYiPVZY+H+P+JAH82eK1w7JAgTK2BDdbzrGu nNh2oNZqAdbnbzOpAxPPyfstpZgIvnvkKjFMjz90FR4sRs8AeO/ZeBB6Xf+TOGUz XAz/WlHEnPBBcKOT4J2UF/QzdRCoWMAnDTHQG8AXEshtR5J8P2/v1pRbG+pXuK29 Tm/xktqbgF3sToSkdCcr =p/IA -END PGP SIGNATURE-
Bug#821560: php5-tidy: PHP 7.0 Transition
Package: php5-tidy Version: 5.6.20+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php5-tidy package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php5-tidy -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqXXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHEbEP/iZblgpVUCJHmUt/QtJPO/45 w43uvRocjs9LS6b4j9i3RhidLXvoFnorb0M/dTbbpMcYi6M8sin8uvvg6ziUeeD1 2Kdt0NRUrifMD4jqAi76NYo8NAdTO7DPEPujhOjSiHYYHlh0QYDJSQKyGoc7RXyx qAylr4Bfd7RgdHyg7JFX2gAfcEodrjXjnFV4ZxcchRGQkVIk+qwHAbHTWfmwxcGZ S7HM7eCTFAs5+VNbvKLDVwnlqrFVgqt78+iYidTEEaMwTQH6O9Il2orFXvSwZdIm xi5gz7OIdZC2N3AypDGH8jrsM9lr3UAnYSWJt7BHB7+pnTPjeVaODaaE1zwiXrcD yFQxLwWFQflTJ8OuRxoVEdZREgngptLzWn2OE9jFi1ZShLWShoo9Q04QrF+WRbKD XRD4lmcJTmMZp+sWpGOxtHVZmOHohPZUKYD4a1seL3E0Bu9ytfT/Tf6UcM81/Pqo bwRTlNedxC0qoFbzfaqX2yjSvge9WaMJLCvkI/CZW9YorhBRWk2mxh7M9vEMXnOI JvjXI5EeMMEs7r1BaaPSp43PCPVASaqZERKVf+NCBOpificjvq1MM2bvf5+hCeBB JGWPPqcvSfnnYiZ0nbGumtTN7YeIee0uwZ4jUAACRbQCNk33MVs2EaXqLnZdWWUb QmtfjaXjqLefYdQg/iym =VRlz -END PGP SIGNATURE-
Bug#821548: php5-librdf: PHP 7.0 Transition
Package: php5-librdf Version: 1.0.17.1+dfsg-1.2+b3 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php5-librdf package currently depends on php5 php5-cli . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php5-librdf -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqOXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHE0sP+QEqC8d9SOeTjRw1GSIWkmjB hqcGUj26ZvK1yVs2rrfHshSUT7oMxKKoUE5x29P+CJrKrz/XjmZ/HSMRowRYa32l Vkd2DVTXX2XhjQsz9gPwiCJZVK2TuX4BX0wQ96XPhq+ZdX/Ce+mao5Be1n360gQs mLQzd8CUCjCu6qDbYHa5m//dp/Qbzh6Is9gjCgPPQD4uAcnifKk/FCB6mzJ8iZoY ZZK4wI2QLv2/L32vAhD9p/q/0QbaAcRztNamM1qIS3IXZSQeaEyH203Dw8TGgzE+ sD56sMG4vQAIgFW9qCILzKYj6ZRZ9EiAPN79ZjwmJoyBhuRrYWkfOFwgskkkSzlr v3V1KwL/FL5VWIM6oZuSMSYohSnlwODXipNRHhqp/wRvLWEh8uRch6Y2UHDSmKRq iwy62pAwdFwObfcWrYLpwN91KcqgAHgK9nhlN4HyPx8PHxPG9t2/NVa/fZsCLNxo 4GErR/VTKL8Aweg8fiYdnFc+1pYLa8HvuYsQSd/z0gFe6IwG71ffb8htLOyIDX73 fJ86+5ldFfNnQ0xVLr/TRBwi3kfkwv2lj3xQbq7oR/txu+RsCoUm4ZI5o4D8xTjT s9BOASyoqdlYkZjXoxE5KTavWPNkDLQ/2FrMcHpmZpTTd4lhsE+cLYgphdDoamPN AYVkkP2TF4SlL5MDNF2X =tijB -END PGP SIGNATURE-
Bug#821546: php5-imagick: PHP 7.0 Transition
Package: php5-imagick Version: 3.3.0~rc2-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The php5-imagick package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: php5-imagick -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqNXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHLXsQANmGbmfq59Mcg9yTm7NFR62L EgQpMXgz3u5p3n1GMYnTxpnIVbL7tW82ig+6o13a8WFFYblgTKvGtavs0gB/tlJ1 5eiRh8f5/+v6nzYqX0LfNxTtTsBgV0TSr0tsq649YrZHGb5GKYpcIVE9ek8UyLCI 5JQ9xm9xmJxsTwR/azV8n1F9nmRC9nXkmviCRvq4gr0WLvXHEJjZeS+qBA9n97KD ernWmzLpyAgf5CvHRqksCQCZ9RGEH6qMv5RvK1sEGD/NQ1QCUK17SLfnmeX/ryuk OT+A5Srcnx4Q+zsWEEpkieWmnkSettxHR6wPIP930G13AeYyy9PFlGmaZU6I76TC pe0mxCBEJiEuPLcrXhU/Y5TTP6CjXnEMzC+ZG+50L6VstqUqXyuO31yt9b5LZhew 6EinNF4jEtYuyIhjSS1+1xUpBcSWluvS/TBeblwutlpcwoKvZ5pUWC33SA7UbqaD dUHzyjO2cUnhx7YDp8bFozSDbpUc71NdY39luBnONHURZHwtd3Ke9skbZRg5KJat 2lxoT+fWVJIRmk4gyclQYRGsqllFKkWjGAbhxbAd/4wCJImYP3mIRMB6qDb56jti Jdb/09+tmUdkJFYMavZisrr4sUNgOxWFBo9TrKFbZwOp7PDiVVJvGXb0Jz2v7pxC U91bb97OAJA0So4cXBBo =KFg1 -END PGP SIGNATURE-
Bug#821543: phabricator: PHP 7.0 Transition
Package: phabricator Version: 0~git20160124-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The phabricator package currently depends on libapache2-mod-php5 libapache2-mod-php5filter php5 php5-cli php5-curl php5-fpm php5-mysql php5-mysqlnd . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: phabricator -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqLXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHe8AQAMUhfZrZq/REIEx7OMoCbtRe KpG2ywJr+f6XeHqnnJGTYcMnP30Hkeh1L6y1eqME9VgfIsvoSuJfqvhUNwo2HMVu FbTyxjt/9oME/jN7JRMW2m5j9SXFeRrajPFxU5ckweurSn44YGYFD+PPzxHRGVYw Ww1ASEl2R8PY2AOuk/LU4do04WdGOEgTjYnvXVJHIMGXS/Uc4lHfQUrsiBIHS13m WQN3k3Eucwb82dZthl1ywuPKcTPuNQszgprpOVeYDlsK/OjslYMccdPZOjdQU/vK Z1GJpT1gJo4JYKOWb2Nku6WYFnZJ9Kbzx6GSSVJsL1iAZAOv4W3cst7odBgbVYQf yT2SbdZ4zziLkQOrTA95i3js9hOUUoWpPlPn3ZblWXSedeBVPLPEF5tE4mNKvzT4 ijWdI9iTg5ODg/L7OeggGvTjb766OKgvaEb4Ql+twxjvtmqN1ZchqMeqAF6ci3dM xf7D8fLEZuIlyFKRLc2tRZxJSz1Y2f4EdGi7fI5yEj5Ko5tL9rq9cdaBeHIPBBB0 zHJ7/GlC4FbBraDc1MP3DrUwU+TuSajduATEV7GHImDzREVhfK+041tpDo7UbDxe /d29LVU6o41ri4mmrWUtYSwBTKo1H/HX63tUsVXkntP0TTFf4ZMCHQFUR3veEe0M NVgTQM25Dl1J+XuECP0C =kTG3 -END PGP SIGNATURE-
Bug#821535: nagios3-cgi: PHP 7.0 Transition
Package: nagios3-cgi Version: 3.5.1.dfsg-2.1+b1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The nagios3-cgi package currently depends on libapache2-mod-php5 php5 php5-cgi . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: nagios3-cgi -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqFXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHirMP/RzM8bz7IcHxRzPHtZn/cFYj wK6v7ueWneT9javdginBajd++atSy8il8dOkyVl248/JRqVodQvVMnYAtQ0bicgA 4mNOXq2+LkMqE9sGQhHMYI/lnJNbnZL+zDrrGrYDJtLzkWndw6YmtPDTw10eSWoe z/VKO5D0hiFDEfH49/8HWk95aEUongazQKyGqBKuTwe651OLzfmoLrSyEWCUzk8X 44/PKvXOgGMnmOmxx8RW/dbhur2Vk19KUtYDz6Vwv1yq8dnk83M1H8Y68ogIpsgC UYR2EGtRZBOhFfNYbWQ9l0pv+5fxY+V5QSJb/nT6URFD0b5IkKMLrnNBbiZj/fHj YzPT6jSdvPEjz6U+eJ8S7Ff9aKGA90VAKnxjMK9eg4YtmKcS88zx78nEXl+TCXYm pACw2Lte7OwzLYbCj/38D8/WExKztZXfJFxkFvXXkd6IT0hLiQq+Y4Tbamj3ItQu +do3o6wUJvAk9Svl/ki5sDvecf8fcGk+WoVSnDlq+DamYRaLswWiY+Jnme5K7s6N B+vY1j7/v05gSykCyasu8PvOd1OUD/2Bs3UwydU80azt/RSvEXOkg/X3ewt3EJpF izADCBthJ50vMFky2x/x8uZdcruNHS5SNQcBM5A83ColY7TZGdhwFQE4zw6go2Jc rfojjmeZ8/POEJMq0afw =/5M/ -END PGP SIGNATURE-
Bug#821538: nordugrid-arc-ldap-monitor: PHP 7.0 Transition
Package: nordugrid-arc-ldap-monitor Version: 5.0.5-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The nordugrid-arc-ldap-monitor package currently depends on php5 php5-common php5-gd php5-ldap . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: nordugrid-arc-ldap-monitor -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqHXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHtOkQAMkq6s5FP2ozaVDwZPwVrUcY Hmx+/ow0MKeDHTvaxAy5LSVfZzNGLiAKNrWAC8GaxW890nvPLbwR/EzftLDbcnX9 c6LbP3Wz+MWce/y0MLKE7P/qPgzTt+1vBNBr1HgvccgGyQdtBjhQ9TladbWmQzXA na8F1TC79k3qtsSfl/qREAPyjsl17PRltcQLals0dcPZVDbYChJy820YXpsgpwPE PqXre+dmzkX9UqegliKJYOJuTk3Q5iQik2ZpTxxdSbCb+ePkS5QEw3frcPHVv7yl NYlbdXJXA0h01ii4IIky31C2ZYjlRTQaLP/t9ei/QS+Uv30245myellyIsXPGx3T dJMrlNFLBrJLbJQ5MJCNnucgtVEqU23W5UPozP5m9QMX4UBcwoPRjmgcaF0kGCWF yxCl120reCEq80MIaVLN3vpXnzv/wUFa8VO7SXTfPNuScMYe7kw9V/DtpblEv6bf 9FUGqywZM7986dw/ygIyx1Z0SF1pJcVck9rrto4hVUrkjEfuQnSmBuzExQWSidGP KZoZ6sllmokj7IXe0/H8A+ew9BxdKPOybMH9JQB/bK57IUN7W6ziqThoV9/KxKha fj44GRxQY+Mrx597YlxGCAu1rHcC4uU11eFAdKlPzapv7Du5oQohzCFiic+8BzCj PgvdhFvlVhGZnrkZUTtq =Vy7e -END PGP SIGNATURE-
Bug#821542: pgsnap: PHP 7.0 Transition
Package: pgsnap Version: 0.7.0-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The pgsnap package currently depends on php5 php5-cli php5-pgsql . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: pgsnap -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqKXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH/PAQAIstnuU0jQ2VlCeIOqnMvW2U /v3vivmRFE7N5+QeirT6hSUdcg+/LuHTn8qASVGhV/hDj9oeSdT7bohIb0nJMpD8 hf9t2jd+M+fqiY3XHjNRHUipdCXLl4mVrDwuXlRwslO1dYsVt3kwUqE6pwF9b3Wa OXobxNkOHhaCc/jWTf+aJE9AHjFY5+OfrnaZJ4RTJP2ureRcTyrNqLAqscCgb9Hz SbaDX5IQQH8qz41LJPratXEV0Z+F96SBIkv9Na4w4AODOf9U2793VlBY7UCdcJt7 cnZu6g3a8oHdh6+xppB3fHdATrpoD0WqUlIens2KDpc3r/gAOQfdQ2G5sl6TifkE vaIedND8fhBySeviFeLDRSNRUUeynGDgLmPCzViAXMI5VMfpppVvSzwyIRmxFIe5 K6ei1mu533QoyKMMJS53wuTOTceNi/amwLKx3DIAXpQsAYQIvKaFl7lDFY8I46Lu PwhLy/GrW60+HBNXFxQGPnbOWaF7gZ+J0rtZw4McYFy/muI3kZgETbwe4qngmVxt 7WtIqltea4+9I/LgfJiKnkF63Lfv2xQ3Xdg4gsjpNZrGyeK6axVnyY92UlDD4PBR I7IDCQi6gLphnw1zpn+8ylBcptYXGTbG+v4wChlrl5XClRte7+QnQ9zIhlQupBma B/4Hfl6M3HYcNGKuq29s =GcAK -END PGP SIGNATURE-
Bug#821537: netmrg: PHP 7.0 Transition
Package: netmrg Version: 0.20-7 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The netmrg package currently depends on php5 php5-cgi php5-cli php5-mysql . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: netmrg -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqGXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHvSYP/0n/MGjLzIxNH3/IujLHpw0M MkFAXd13a2ZaZiRGCQzJJrvKfJ2vstBa1jcmXWyBbCAHqY6kZ0pNuA3+CK6UbXRR bw8aYaCGM7c/07TAlixDQjdfIP9hMPkBoupKER7Vpqvmk+yPIOscNxl/zeTaRS6E rdXPAaDh3jMgurHcPzkBaKurWTOr3bdSd9FAF9GEFMKVXxu2JtghWXI5X0imvzoK P4EAIiyCGZ/yk+kvXDb4kvEjIIVQOkgEwbbGjPO3SiE0zNgKBESXUsu89iau5xHD kg8qU1CwFEaZQ63iM3RTt6yPuL0OeTmn3fvzvix+SeFBVKOSmi/XmRy94WqxDb+x vuTC5GNRnajaOmuC+xBTop96Krf5LpQ2uwuaPobNSZgaFAvC07IBjOW8wtDEjn3D fYGvnc1jdclG1W6S0U3AahhIh9R2Dda1PakIQHt2Vkpd88cgs4//7o3fsVkTlj2Q G7t3jNzpSE7j/5zE0AmcVJoe8+qastaPd66dkbWxhMazlmS1y5Wysd8wI7OoiPej id1SaJeVUKcUpcgfDtaLzYokKaFt5Rnt3a6B+SePnTjasLnKAwIIVtIiGNp+893d dABrZf7ue/cJ/GTiu3sNnfWylzUv2Kx8mj6+GBJO7MHcZ8madyzKwneaVfC1SO4B nN/YJ8iXDKmdz3FH4R5h =VAAX -END PGP SIGNATURE-
Bug#821534: moodle: PHP 7.0 Transition
Package: moodle Version: 2.7.13+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The moodle package currently depends on libapache2-mod-php5 php5 php5-cgi php5-cli php5-curl php5-fpm php5-gd php5-mysql php5-pgsql . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: moodle -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqEXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHKc0QANXt3IKtvYLGtiz6WN0Xe6bw Ll+pEnQEmBhLZ8S4QHoAmlSdBlNopAPPrQXvSXB6yw7D7umbTaGo+/M+464idRcp GDtarovofQmcIUXyvj/Vkkr/udq4UunSBM3o0cBIBpf1h6vxa2yPl+qyhCKwy/hM vDO7Iey5qX0WAIHhfD34aQrVwVJt94eOS7LPH2r20moWK4RqqIYrh1sFaiNo1g0r GWKSWOEuORfVrA9iMwluTXw2CdF6/Fn66/yiIwflHFX7nB2VawZwloLzSLSNntvL GED94rihFsGsjcJDbAdLWuNyhTxhgrAq3B4NSrbL6UFl9Umyw/bHoaEpAzwxwO4/ W3I5jIKgLjRulvn/GpV7Jt6mC/iHbi7jyn4vmrztJm+b9DqWXByhYn4ZPPwOXTpu ZuQnDb1LsN6J4LxgnAvlvDB8MP9nU48geM0lS5EYzCWQGNhyENmK8U7sdlLjeexs L5YDYeQavgrPjBshqa2wYP/0XxoPAax2uPbEnrkZiYIJZPFo9MwwOFvlPoG52hBK YZmuDj6r6jXnPv/l3BAsrGK8jrdigAdwRwuH+C3OZmYxWCRH7Ak9o9bX8tz/ZK56 S9V6qcaFXw/Fm9St8USmCzWPbiPS8evKhaMbrQnHtlNK8McdtBAiFRbiNsU2lrfI 1YscuQGv7gP+oo/b1Ot6 =ClCj -END PGP SIGNATURE-
Bug#821540: owncloud: PHP 7.0 Transition
Package: owncloud Version: 7.0.13~dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The owncloud package currently depends on php5 php5-cli php5-gd php5-mysql php5-pgsql php5-sqlite . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: owncloud -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqIXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHCJ4P+gLMg3PGGgXkHvWOSjg+GmbL O+mqGPzZz/N/RmxoPA8xIHv1XgIkATOF3WPWaStjHPvOElLzLaq1hNrwAswjaIgW B7F3Uj8BrsfN2BEVEomp/VMZEQPlPX2EBK3sfB0Z9IpQTBSVk2/Kb/hvFP9zpkve wmQD2g8e7fju1pUALVy0VZXKFjg+t+H9KDZ+56adPyZG8E6uJN0UWlmLzRI3b4B5 fzimRylmWgLKXEXNpe5UDD1Rqvz2n8ayPC0PaczyOVSncVcZPku8P8a0NzQJcP9j IZmmLm6E1vR1Ol3X8JaVuSNgroC/E1sn2HqZ3z+EMRJjRMop94ruV8JmiUtMFpah grSatibueR82vMC8F+wlVIRGcat8p4cZeWvYZQG/1vSPmUXBQgTllAGiggiDEWK2 eAbBfJAiTSvPzly35v7i+xmkWH12fLFFjEPz1dwLTh+ZXQhyz5V7ssT/rJZM9ylF zUgmSmIZ8VVxBZ4G3z/jyH1liaT8KTf5wjDOmVKULPxJ7cwSLMgiwLzdTJrL6IjP 4/CBNQ8bZ34HkqvQQz4w8ip3JyXRloDZULvyPmWSNZRDA6AWikYAXS2eKVTdzkL+ CBsbYfShMY+gs7k95gbRERuXF+0+0jAKU7GVEvrlh0ugjXfFg0wL+yIahv2WDS5Q QTYWpMN6iIMrmEO0EinO =fZz3 -END PGP SIGNATURE-
Bug#821545: phoronix-test-suite: PHP 7.0 Transition
Package: phoronix-test-suite Version: 5.2.1-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The phoronix-test-suite package currently depends on php5 php5-cli php5-gd . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: phoronix-test-suite -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqMXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH3psQAJsbHK6c8fODPadmedjCOQmj FyGhqFE93AMdkYfsIjuzkVpZUS0GrDuX1m4m9O75Wf/W27jjfa58JiDOe/ty5iK4 l7Hr8o0Q2eahufduijBZr05/xrh/PsVjYv9445SX5wspSfpfAFSvM9Y7WqI4Wo0J PpofPYeL68fHnZY41MJf0VtGG5gFGj6n1mvjGfRy+Caf0A+pGCKU8oPBIb8Moq3O k5dPooZgWuYj0TEhXey8q5fiT5AiGf3/+pZk2Dh33CT0Oy5OpIFM8HIWMHukPjSg gSTy4G06QD4DcMgV/vGS5G2E98En+5SmJ4hEciNsW9gVb4xg14kj4No9UHqoF5g/ pstdltg/du5BkUW8F1X98xk1JbP+p7RdTZhdJRqZcu3w0k0NY+R6Xsl1tdYUGbOt WOC7B0U8SfBoPoLpIFp6rMxKx5QPm88CVYw9Z90nqgKKvllfbdcFIMDcZ+gRD3co 1E3IIQK69NApsWX1i/Wgju2rlF7xbDz2kGw0a1g0S8bZxMqK6hmdPIy6UMt3NrZl gJGMQu2ES6LDswXHL5Lq07WA5agMt6OcW4m5Mj1ZIEPDBeKnTmnijHziJLGb023E H6uLi13IrhtuYhExgM1IJxTcqPWq5SMdMq03WiDZed9/lMMHMY/9tb46/gba6be+ kQEob2ZVBdhZ+ppmytTY =U3iG -END PGP SIGNATURE-
Bug#821541: pgfouine: PHP 7.0 Transition
Package: pgfouine Version: 1.2-3 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The pgfouine package currently depends on php5 php5-cli php5-gd . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: pgfouine -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqJXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHOaEQAIvCA9fgl8/7umF79vbZW20l b+cZN0hk0XqDkUxy1AM3ax0uKsecimT+Bz0fotNyulzyo8IuaybQLTfRszTK9fUf D9tz7L8Cbd6qfqMqUN9aJ1onqZgZXgnnEPCyhcJKo5+uTbIWdaY9k+j23WO/ggOA LpQ3LR1+6S7rccBfkYOAGAqMdoeCbmYnxQ+pNeSvQk7mcm6kB0Dj0Cji2amZF3Tt PBqBKI7q39uim8ue3sLmmIWYkB1ZDwaYv8rQuFoaXpgLGHgRm02BL3YiQop9cNLL eksQBc3XdT01INfObZD+WLxNwgLUu3DrxdaejG55u+21+UNRNjQv3lU2XHCiDeKp QwElfMp5OMGi/EZY8x0MKjhGB8GImq07GVCKDzh/mm6uNUKAZpgPiP2TgIEDJ+sV QY4aXTFKnfSXuS3denrRM9Kg/rX84Dbml4nf2uYbJp3jl4DyD1VRLANAoctFfMNX p9xwGWVriTdZ6L8OCADNAYo3oJGN7Kmv2N5YpFRuiCRGfBggBqDLlGh4onofVd/b PvOFiMy1WENA5wCNdQeLhhv8eWFgaFVvGnBYXdTnDtD/Ld2HQu6bTN756Q3VbWD0 lZgG0oqVkvOnFchwfFZ4mAbadXYv8o2Y4ERNvFlSf4vi1ZoKFjKL/Y2okG1u2oMS JkGHLtBpqB3q9lXzAw0Y =TsKH -END PGP SIGNATURE-
Bug#821544: phamm: PHP 7.0 Transition
Package: phamm Version: 0.6.2-1.2 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The phamm package currently depends on php5 php5-ldap . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: phamm -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqLXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH+MUP/1knW40y3xIDaJVRcgYrJDqX adziFyQiSII/osl5nkZnQ1BnvwmXEfrWveyVGeaqZ+Jr3gv4dlVMaSwSQNTOyhjQ 3mRSDRt2cPZDICbuDIOmdUGCP2CK8kPFge1IM3oWtjEI3cQK5A8LwL1ND9C6QYLP 7iTSr16L5nGLDD6Khn3dgr08+EPFSdDIW2lI9uAFzDkUg64ISDpL0PeKfP6EGbOs uJdX/rbzJAsgjnMGro3ON+2XdOfoC3Wcnm5SU5KqacdSIs1vHtL28Bz1PD7NUbOj DyeZ9RdNwCb0rPfZmagSAhescCEUEimsV74UEOFyyoWNl92zBH+uUwrWFIJ2KBvv tdnspg5CASjgrFKjsuxMBnpzqTzNPXedoHLLcX7uLZS7cZx6PbcpELPYpZ4wHf8D H3UMP9Q1eK/7Px+PfC9Yyi4VjMXQbdNfQ/DA6PpsVQJts5CL9OcXANLvKxNXaAEI bDZfdhF3t7YiBAIyff3gB1KtVxK/YjgRmAO1umsaITyebr6U0qx2UiVsnGkjWVgk pGrmCHz7V+ioXDUTO2sPWyvNkTgY29gPfwERHFmDQRofYMh89yFSQ2xpzvQNbN1u rgoXIVmRmEJgpbdHYwOS4ouvur+IoQkAnaBvmBgZV3fFYX3R3jXhqqV70FdkB1qw f5nn74JtFw0F76Bf92dt =yxLw -END PGP SIGNATURE-
Bug#821533: mlmmj-php-web-admin: PHP 7.0 Transition
Package: mlmmj-php-web-admin Version: 1.2.18.1-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The mlmmj-php-web-admin package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: mlmmj-php-web-admin -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqDXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHsZoP/1YrAC/4GL64QwjhvnW/F+rU vF+cp9gOOO/Gy34+mXULaS8h1fJ8fxUU2rfpvt+fxUJdKZov4ZQusAJMafcJHMMt p3g+6Yq85dhkpwPTgL7NngL/cGEmqkRF6HlsE6m390FgnI56pSUboGJaA6hvpkdG jkt9eVXDCKOECkfxzwnHSDJxm3FOWyuh2c1ZAAM+MzA+wpuVa7MISHzkhBwvaXi/ mfmjJmZZuKGkuDWw/p3BqWLU6Zd1fk0mvG6tttYR0YrQePlGekDnfBSbo5KGjthp Jruv31NYhTjVln+k+0kGcWpmKT6Ax/Ji955qcNhoM4oSqPGT2Oy8MO8GXubdvevJ kWitSYceVu7jhsKaMbAXRYQxW0bA+0jJbgEOQxnAqQ19saHNLRmv+MrhnMV3ULLH Xrdard35DC4BYGXv6HjQF69vy6W0z+ClgMRLrSHY6chFkb4BzCyPCCelPw15UQD+ nNngY2Kotxqso2wh4F1F4sbdKeQlws1YtxRypm+qq4+UZvqLl7Yp6615kres6ozO qB9qv9eR0OCS5FL+q8HA/A9+lfs+b0aAXri8zlTJYXdN7BBWAqZ0Z9HDMzWMhiwz C2IQt5dxpHI+VSOa7tv0y9WFDU0MYLCCyqp/6smL1VZVsLK/erB0OIRJlQKb7mY0 gGoVpVdrkwEYikmBWVON =Iqhp -END PGP SIGNATURE-
Bug#821539: ocsinventory-reports: PHP 7.0 Transition
Package: ocsinventory-reports Version: 2.1.2-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The ocsinventory-reports package currently depends on libapache2-mod-php5 php5 php5-gd php5-ldap php5-mysql . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: ocsinventory-reports -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqIXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHAPAP/0LeLmk23nsz7RwqM4ymkq2d KG0sik4aWAjN8QamfT0KkySlpqlrbHdtwxB2ZcztWL7tkj0cw8yscyrjowsIKbmo awNAresYFNIszjgkc8zDEYkBF22XhdYbnSPSL312IkRTd2bP8DykMEpSv20LlbQ+ b/XEjrfo9Vrkpb8Ay+QJe9op8L0A3xWsK20Lbo+dN/nGTpf1T6VuHStX3bTOahm4 3yG1u7xx1l3nqFt178fcVGBgYmpyA30vcxx/aVDtDRLrwVSPnG9vrScFevBeh+/3 8BfWEzxwoqQv1UWsvq6Dko+w/6y8vrtlZpwy5gVNNU927ZBJoweKbapAKJ/2p40W XLybm7bFnehaH51aXxcGzs42tfDQuR6FhvR6B0PoceiltaoC6oaexmhYxRJ8TjPl uKFI82EsnLruiDXkMl5yxYpl/PPKslY1hOAyEuZ5BEx1R/Y4vXEeE4m3zXYY/fAS Ws0BjKkbrSReldEU7PaBZF6y48/J120d0dGmmb7tZdOffqK8fSFn4K+kX7nb8dIQ 0/G65yqxvVLrNdgB/NuylBLZVVQAaO9vNGGDynBZqFzJXWJ4Iu+stCxwQhjHoGwf 4sCet2KdjNkxLBRgueQJC2qH7JsBiRu0QuG76V5sxW7l+g3/pmIWCQk2lZYDO9I9 kr4S+k8F8Irp91iJi+gi =HSzx -END PGP SIGNATURE-
Bug#821536: nagvis: PHP 7.0 Transition
Package: nagvis Version: 1:1.7.10+dfsg1-3 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The nagvis package currently depends on php5 php5-common php5-gd php5-sqlite . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: nagvis -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqGXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHPpgQAIhSAzJxZWIK8pvKt6WxM/8X EZtzshUzpXOKzcYn+jrn08sgEhlLnFbN7g2po3x6UbrqOaprTDt0epyRbjk1v80v VODDWkYACCJlxxqefSW6FdcbSWj7XiYVCZQedn3Ro6HUS3txC346OUjeIVERKhRK j83gcR7EfQmb/RlpCUXL9m9/xEaEiDxlboLxW4YBXjFrymgVirRxGci/hfMUh7V1 J0y/ltBHAKeF2keFFlR84xMz8oQkXsYfiMpr/33PzUnhIBVausBU9agfvSopIYK+ bIjbKNnV0C+oDf0eZ2LQawzcGE2gMwlnnwh/u5lD3BN+LdBf5cmWILp4Vqz5dQjV EvJsJFaRVLVb08SZ6uZ9P8U3Ckpmcwp5fTrIcNM0nvR6Yg4rIFdZ8HvAaIMfMpMF bVFXsReUEP485Xq6p1Ckiln99fWDWzVNNIEM0tcjjMX+4ZnFGeR8kIuiLEyA7u6m N2rzFLMszekjJ/eBzt4gcJd+TY7++9MlYMa+Y0onJbiaRjR+1Dfr4FaHSqH8tGXS fwdeL7xiYI4bBYQGqSh9RCwoFUyqApvVTBiDGd/2qu5OoROGNoDi82k9z3z0UC8Q uiGLo1I4rbrvlWZsSz9LWxG282YiGXn8ZDgZHsqmm0HXfCALAuff2JdnKnHbBnUW GWOxuuOBRZT0mkgasECo =9BKJ -END PGP SIGNATURE-
Bug#821525: libphp-jabber: PHP 7.0 Transition
Package: libphp-jabber Version: 0.4.3-4 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The libphp-jabber package currently depends on php5 php5-cli . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: libphp-jabber -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUp9XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHP24P/239oJhZN8SsUc506X6+0jbC /PLQjDFBZq4ooQgQYPXsxryVDMvD8WFn0mboVPGmfl9Cf1FM8wV2CUnyPKdao4Rm A6IZWvp7uarFeen4yUSR6qheHaGFQDYwE8cDED4trAtivZnEwcJquivXMPYzPbBX 1GrLFXhZXBMWS6y5TNQfvH35GanjimHjOHEpEOgp9X5VWd2ziLL0jnJIWbFaSdnz gZHUutyW10s1zC8xd6A4/Amoh3N2mmd9fR7Z9pfL0yh1Lg7Epb8IJ9uCYYM/Gsgm Mrx9uwap4Xcr5V3D/IO0huZIM3+x4EgY2068LHkiydehXro4MpgdqSWH8a0YCV3v q5IL4Rv1aCTtmjOgA4fOzwY66UThssRTFnnLW1KV4AqUpVPiKhpjCGAEGxmv/tys FSS7fp2RBDHlDZT5dIj1SE5/h8MCE4wTqZDWo6ojdxPQwfeDKFoxiOkI2rZf8krl TRJuAvmP7fpIV8+YQu/efOzOeHT96gWnsO2vvJliZTmGBpB3sNgQR/2iAC99CRDD jrhn4vKZHTzfkheZzRkA65ShBVaS/Mrk9EF4OG8A+M/3X1zyYEr6r3zMhvWGYsWt P02p6jTU+xWi7EQtbp7BhqEDyuc9OFa8GUa7JsQuevNUM82Qm5cQKmpVTmLDZSmY +GcNJ9XlPQE9EatutCGP =aKcR -END PGP SIGNATURE-
Bug#821524: libphp5-embed: PHP 7.0 Transition
Package: libphp5-embed Version: 5.6.20+dfsg-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The libphp5-embed package currently depends on php5 php5-common . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: libphp5-embed -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUp9XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHyBgP/2ajYGusq3q1r4IpemJWy6tt Vk3APlRFokSqhrNZrE8EQRizy+QLSUaR8NfUZxC1G5ar/btUFHwC/V+sS/sieLlr 53JSCZ5QTHoJ9kM2ydZflXidpcsuk2NAuq7cHahNxEBhMFB4XE9ngrJt8bjGouKs MW7kYGcg4DT+F8v0dA/GR5wYmNfMVT4srrQoLFltuTMv2rB5QcbDhsuWFuAEMwF6 0INmNhUoAKUqnmcnyE8bGHGsY7ar3fLZlMWlp9E2qnzLSCtEgM6PIljiTGj1zsop GFx3C5GKlx/cGogyBtWvcPsBYnFFFJXp9dJUabljQ9rPdhmETG0RsTaL2fQG1kYI DXt3mATOOxxHU0iDHqh3Zc6QPxBxjAsHzepvxApmS5DB2x77u/uFWln6laU4h17x iwZx6ILSrT+V00hfONsyOw4Y6M2+MkkeCc0X4HGO/505kgHC8VTTScXngEjhmoeP GAFH3Pwt6W7RnGBc0SnfmIrBIhH5WAO1rSMlW64tSc+HCimjIbSgA4GR4saw8puO JEl0yj15w+oEBGs2gnzh9DOakHZTwra0sF+x3RZk8EGlTDgkGDILlkOmNtthlMd0 /AwLx2YCuqwrW67kK65q+5aeBo37338/vhCsy62+jB0s0eR2h9gNxQrdV8HS8PX2 HVG5MnXps/HRcxHW7WSZ =sDVo -END PGP SIGNATURE-
Bug#821523: libownet-php: PHP 7.0 Transition
Package: libownet-php Version: 3.1p1-3 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The libownet-php package currently depends on php5 php5-cli . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: libownet-php -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUp8XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH6a4P/RQe6m9VhoTc5c5S+1Eq6E8V eDXlVDRQz43/DFhH5likypVA73S6qR7ocKWDE1Q+m+87OxqIwl/FRZ9pTLUWpjrz zWp9X82vJHkvllDSUzXdxcHsopGwkekGHTmoELRaxmaXxg8jSFzXkL4NDf3qhnXd 28boj3LMUdJpmA8zmIw4L+mnnh4W6xCAtyyUOlX1mJYiprFNRtucpyVpmSijuKtR jw+7u8HcHW/mANAmfdcsaZpf4m6KBzoWF+FNg3v1wibl3IsmemyPlEkHy1Mp7OTb aXed+vovYXWbZylhmhPiu6wjG8QUanFrNF3CNPDPtQGrrTYjIr59sGeTxBHum6bk J2OZpRGnOO9e0EOR2m6vS0EGNf2C9raDIc0en7S/h/gbK/QNq0YEz1hJivELkWqy dL5j2pv3UgB7Fbid/ToVq2IurtzPsWYvbT/RZK7mcvwynxNTSa7OWX2DslwsLz8m TDZbQ359f2tzfrsiwKtnuQkbTiY6k4iFd0F653Mic6mTHr5hx3+luV+2N4KZV6A/ 4yQPCRYWi+9rc5F1+bIi4poW/vZ9ZjzoJ/IE8HvVm/M9pqYTbbMzC3MuvPxeB24r Fh9TVXLQMy7vt6Cc6/4ZuBqtqpsMgUGI7Q0zKghJu7Q71dDBhrSzryJvAnisGnLp 32k5QogVOtTvPUpADJ/R =X5Kk -END PGP SIGNATURE-
Bug#821530: libsparkline-php: PHP 7.0 Transition
Package: libsparkline-php Version: 0.2-5 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The libsparkline-php package currently depends on php5 php5-gd . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: libsparkline-php -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqBXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH1sgQANFZYMiq6xkgI+2ByZkE0OaO iPj1O5wvgOQ0Z+zy6mC4oUnKjPT03DWBnUjTEzQA5JVpyTnAL1bE3wabYUn0qbUv Fq20lmLjUkP0aWxF+j4jDEZSqIsY/RRnAp0SfF03CNMKuSX/6Fc12NRCEyIvtuNH 9DgIXcrUqZ6OmjPnNiUphg1U6t/fphLKjZ7ZASf52VXCntHcQ5YCqHWu7P4U56h7 NMVzqsQx3XHxsEUMfzbuzHot3hU3cJonogbS9xB2CyN6vuTmJhpuNIN7BRq9z9yl jDyh6tu6VfUWq11gGl9fatk7DdSgi/uNSNbJ50Omi7zFHqy5OyJRuHk7nhgUBxkv 4gwn6gyBZZbznsUhpvrmoetmnHkZqxAu923IdW+LXTmwUV5LiNwX4Dbnx9Ps7BBx +dovgWXPdzPMcQx+Y3gAd3d+ys3vEBsrB1J8x7QpY9bXUxJ8uuHunsTNlIctFicp v/Zq1NqUsSn1KQWcc1zYz4GD2YfGknka4dL63jfzA0b085yk0ADnSkoULiVUHC33 2HUpdG2OBnIwUBRygwF4kQuVitGGUM0qICiBu8OEh+D6LuiRc2luf4aDbOdmx9uK 6WiwJ5RBFI6+Gd0BuES4eHU5aLDNNlwnuMG+XsziCbCA2Nr5hp7VzTRNI9ntUlq6 XkNFv1KhD+yjXbSMd3g2 =iHw/ -END PGP SIGNATURE-
Bug#821531: loganalyzer: PHP 7.0 Transition
Package: loganalyzer Version: 3.6.6+dfsg-2 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The loganalyzer package currently depends on libapache2-mod-php5 php5 php5-cgi . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: loganalyzer -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqCXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHb4sP/1BN8x//oAipV9tY7cFy+Oka jfGcOcsNvx9oL5GtWeCkUs7FEAEz6a/BWP0Db+24oOeaiXIzhlvhKSgnCB3zOLR8 r2564EvCaGqL3bib4ytXhEuMY9fKXi2RYWte3VNC9n0ndUycrR+0NIw2ydevzhwO 9X1xLeKqHvTwRuEsWhbCc5PP2ScHxdCsgjTr6IUtKqf026Qrmv8nX6XnBGP4HWkF BVNa5Mr9oQGPJ8Y9GWeGkzMGUHxnf8obv8Mv3dp9xOuxWejIil2W8Ga2h66cmJ+X AjFErI94ZfEWBQnfdzAtlbRAs6KcL3lYzsouNAr44xCk7PCy8YCCx/tz1TV69Wao 0oue3QWIMq1cQURstba2auc6tY+/WmugNsvm8csGxFAsni26d8a/zFAlAIW+hZsn Ha0nalidDLbgA2LyH+/bY0Hnu6dK1DI/FX/WghgxxXNfDz4UK/atIT0ThqBYrqdr Q+JHqwZgn5ClN26C4deO44N60nirdlZclTB/iEi/fD7uDITNl0VJ5TeDlPXKdtlO dErCDZsGo+gh/nOt2LWnI/i98xadeMpAZ1+tXr48OGqLp8pqFlmbjATVYPG33doU zBPZ9YPDePgRrVSS/ksOEnKTnMZLpB6tazvij+Yx2PhPyZjkJqWOwKPSaQTEblWH qGgKzrzI60pxgNLA2L0y =1Xar -END PGP SIGNATURE-
Bug#821529: libphp-snoopy: PHP 7.0 Transition
Package: libphp-snoopy Version: 2.0.0-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The libphp-snoopy package currently depends on php5 php5-cli . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: libphp-snoopy -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqAXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHCGYP/1cLWbRwEP5nW+2ySkpP2arR l/doBzOj7NhpL0/acGzgAPsu/NaE8O7jm0KLYinbABxcJNHkNHY+SsZpd6iFZ1of R7wHxJS8zdmYJsNpo6kBcyYSrMAoc6fH5ozx3egR0nRx7ifwt2urVe2ZZMXYvP2v B6ajUBhYsM5F0oXjL7Z9HlTE/vCBEHhVZiJsXGN1q9ZL/pD8vNqcrsfHLaSSlC0u SQ57KoycQbIrYYYad2R8hxmC/xh38cuP2LuSJNyEvNgeIeTTA1K5E7OYZdebkrVw SieCXVlCrMZncYggv36ziPTNYz13GwuC1mMwPyf8PNP0Nn6Z9obaXjNQWhpdJOqT ZgqdTOX0Q004yImO2LnD8f+PVD+gUgX9ZwYkSGJlgNxsAo038rUOL6aBbTq2qfsg 7lth1o07MVVilpjzvgqxDgdeZgpOT8lvs/pHWlrX2LoftCKL1FYcJfGRrfVsnqLv WzOcLBqYz83o+64UvCilLhE/lB4ncCOyGIdEkKkkFn45FZRccOUauwfvPOCxZois DqLvUlNRvjyk/EEcf1A4jppFTefl2LZo0gEz+Q3KeRY5TNUGN/dV8rps8dFQ+ihk xPQfpLtcg1oxa8jxUVOZDStkRElj1pOxkne/gHhuWmFvSswgFG1eCQhzNqLPNUKv JJ0Ywg0d7utvApgqX6K+ =E+3x -END PGP SIGNATURE-
Bug#821526: libphp-jpgraph: PHP 7.0 Transition
Package: libphp-jpgraph Version: 1.5.2-12.1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The libphp-jpgraph package currently depends on libapache2-mod-php5 php5 php5-cgi php5-gd . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: libphp-jpgraph -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUp+XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHa5wQAMUAObVlOfqzRdP/GMZ5Cicy ICIW4d9eozs267ee9j/SpF2Wtb9luh3EO5HrhLusY/rHnxPVUSQvroMOlPNyEEWR JjX3IsAXtFJ81t56bbfQQ1eDI+Rb/j0qAwI5ok9PiUZsL+TdX76I/Pk5HItBl4PC ouEbd5WCspr4sGX7eiZyohxt7oN4dKz/TgfBHMEPGmAbGj4jdcjBcBmR+LqYbPFL 07dWM73wArbq5aoJZVOEGzGoBhAL3d323/H4qhpMbCzU9rssL8BRFBUzodYyRWea rS4crHgfsFGR2QsLkKDow49zecVkV3ynz27f0IWTFsJ02soQU47ttdbNsZ6zYkGo LXFXNfstgX47gjBq4KCshq5cIoYhaG15AViG4Qd8i8sEiRQIanARgB5ZZQjOKhF1 E7bBlCyHcFy4iARAJsgHZdimBr5S3oDQa+3e4yt8sb55xSuOnjLTod9uhGwpdLfa Vi2ZJCILj+gD9jt8wTF2bn/771EIrgE4T4gK25ABNfzhgTtXqNNIyEcfqc2g/kkE o+wHO1EjVrVvnREh832XX4AvHkjpfwvjS0/FlmkyuA65KNmjmwvxWk6PwQq60ecF RslFANHK1ah6XnBhjI1PxuLeh+CCaOi6xG9cHJHuAUUaHKuz+/5MXzUw/cVKbBSb x9kQZgXUpwlQJJPoEmkQ =nqej -END PGP SIGNATURE-
Bug#821532: mlmmj-php-web: PHP 7.0 Transition
Package: mlmmj-php-web Version: 1.2.18.1-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The mlmmj-php-web package currently depends on php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: mlmmj-php-web -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUqDXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHCNYP/0NXHuP8cHF9KImKJf0KTKeG L7Ci8/HGbWbxvP+iHvcBRsyP3d7U9iPDxQMJEanqhn9jpxdpAT3fY3Fa2VilRywA OQ5ds2oGk3i+Gyf0NxXy+M5IqyTq9xBCqk8NgqCSCYSh492191AoQCYFQJ0/aGot H3ewpW+P0uuwGMSoMwr4MB0kg3wlBfQcXR+Z6Oog1CmNt3eUnmdGCKOoKAcA9BUn H881xtGXKFCCmRwmvBGGoZLTrhpaF2FO1VQgXaWyy+seuwnIn2GJyVrNZBk4Fcx4 ywcteJsLZW/lfsfLJ61v6a23WSL0ykX/Nx/HGkIt6BKNNsA18O+lfRd4tmO65znD yIsGiAPA+R7233g1YExr3Mh5A930izP1SCpxZKCIjC0XgdRLP/G/NkpdYi7MrJat Hu/hZajXFfLloxE1QwxpjLTFQBgP3ZNTzHxIoF+U3gCbIJEmrLgMEBzxM4BL5Ham 61H9gPQQVF4o84JHkOZZypQGiCMTeHMIb8+85vyvDhcxo7wFFWr9yPsQNl+GHTAK Ef2/77htFWJDWZkVlpP7AVVz7sz6JXKKAgyFVBZ0Ebl0DV7BZYcAQVPGOEEU9pcx aMwWeFQc/UsSynLI5Z0cssfQ4bYjdNTAPNdBJNhruRgXKOqeLYeIXk+MFKfJnoBG nqEdt0MHb3MqRiyoqdhY =9VQJ -END PGP SIGNATURE-
Bug#821522: libmarkdown-php: PHP 7.0 Transition
Package: libmarkdown-php Version: 1.0.2-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The libmarkdown-php package currently depends on php5 php5-cli . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: libmarkdown-php -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUp7XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHFJsQALri8baRQSKpGEbfZM083kUZ gjzHxScj6SslgpORO6jqTy3SdjNijmWfX01uDjDW+lVWUTkdEL2QfnzuYruX+L1o eVFyN1KbIRXigTlXzGJ03CwBw4F2QHd8RqJyTEhNb4lqFGaLwpx7YwrsDZQgKgFe A0h6yiEFKjBaviQ9Ltc1iy88GtVSqnAs22o4h2Py5jhlDD371+G+l+VR4iDo6J1+ upO3KAF7oD9py2IGrf0CpEeFPE020hVxNxoWC9tcfmT/8vJ/E8M+e4U5qafBQcj/ t+iORdKT/dlDMNSU6pYYNAks6jWYr6lEpPWnqaWBMCI3ah+++nLUqOPMiC+abXGA dwTDnix/swBik7mnjq+DTZF7JQpysafMlFktaAk7e6n6vJ037opwnEjorlLmknaS ufb30c5n7pG4SL4QYhiLZullKKiqNUYF5l40goSPjveVxng76aSmx5DmHCTGJLNP KIl2UwSkUrmII5XEa5GmLme9vmZqZ+3Z+8SIoscUlHIJeQ5qOaugxKPPCfJv1O4X MbVV7WOG3RI9fuGZGKpdBuc7DKePhARTmsNiG2IJ1itxvwc93uBV67foqyHpNwcG +6xZ60y1ZA2+QsV1BUTg5RIbMUwRz6qgu2AGvr8ntA7PApeDBT7FSiNOWl/Vt3L/ aBCxzNA2AeB3YZAK0lCN =UHaw -END PGP SIGNATURE-
Bug#821527: libphp-magpierss: PHP 7.0 Transition
Package: libphp-magpierss Version: 0.72-10 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The libphp-magpierss package currently depends on php5 php5-cli . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: libphp-magpierss -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUp/XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHpikP/0tvtQP8WjPUNeDTjmhfN569 0wUOco3vavfJRC3Z4D/uKuljXinDKErYh86L7uBgBYQ58bNtpJnDIKksQG4zRddo 2ByJnWFQfr2bJlXDI/6f6nTacacNO2fkDMDIRPrC0THEEMVTJN32CT4K+WZQqTnX 3pGOsf8PcPB41fDAu6vqmgZnFjlBBENCmtepoyB7I02BwL1wMgr9b7XT1bmIKGa5 UkAv0RbGRTQ1k6rz9KMEVK0b4H1EW82phd1/pJBwy1B94MHf4XOXTsn3ZB7IcgFR pgnlbjQjDJykJACOLCisIOzNNRCc4frWXul2EcSuMXjBqZwdko3ja4GSjtDyX0Sk UnxtY5KN9qWQmA+JGHqDhEtvQM577E7DJNJFCtTtf8SRClBkHquhBd2U2C/6V4WR mYhsJoh8BQyeHjPF1TEjl3AfIET+L1b7tPzZSlgW+kP3CEcK24kNWCfe86/an/SS q/sm0XXppqbrXBrZrqSugoSeSv41xctriyQc/r0HB8n2M8qqBxFNfwdtJHbYip1x JKBOdCJOXOUHxO3rzdWSwE/uYvMD1bF0MqI3bbirRr6TxJRgk7Th019aArT1g2zc xSFTeTadNKa+KpKOlW8zJjZFEqSb20aOVlihNsWiODwwU3Xei6zPkCQyXYzhu5Su CTtWBUo0Xe4lot3YWndS =iIVj -END PGP SIGNATURE-
Bug#821521: libkohana3.2-core-php: PHP 7.0 Transition
Package: libkohana3.2-core-php Version: 3.2.2-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The libkohana3.2-core-php package currently depends on libapache2-mod-php5 libapache2-mod-php5filter php5 php5-cgi php5-cli php5-fpm . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: libkohana3.2-core-php -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUp6XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHPiMQAMaOwTYh+NOQpGKaJlbhn/uw LQy8Mge2etr5xyZz+EIkeBd7Wcha7SF+bEtVaqYpL/W9suN5cOwJfUQmRwqIsEbs uUN1p5WQELZx7C9zL/73+0m4tpmWLnggSf04HtMcMn4ld1kbHmc+xKi0YWY8sCXd vL7IiJP6bGa+hFCFQwu7WnOJlGY5yfeN+53ovQfdloHfRuOFvTvruXphL8NfemhN BT+PW7TLQ6GxSz6XgB4vUmxtAJZ3KHpHP5YRf3PvIr9+dZrSuWo85dv0c94/C9Zb hqdpV8TW2GoaxXvqKRMpPZ1ZkUzn2NH6tGjP5fPBSWAtUvZtufoQNFJY//w03yzb WE7etFjL7044ifeD1fOvzVZRcASStKcipOPLorVPlbE5GzvLF66SHj0A2D4faPg9 XA+x7wTa0vYXlYui0F2B4sk+Qatdavrv3aZ237KJQy+BGD0pkbwojFrgZZ8hQW1z //SHPnyGB9CR//9v27sSsGhz97YnQAnJ2BAtsMDBjMGjiimNrCagF+1evtw7LNnX 1S+79UUxBpkccMk/jSrpSn9fg1/O65UuabWztAtrbPL+KUg5R4cCO7tdoGLRhJ7R fdGdJB5GMXcARQAaB/+5ps2ZUR7vIX5xcm5eGTzIyF4EJaDhzuazo1yKmfX3ZklE flgjIm54q2+hMCCi5h4D =Pp/F -END PGP SIGNATURE-
Bug#821518: libkohana2-modules-php: PHP 7.0 Transition
Package: libkohana2-modules-php Version: 2.3.4-2 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The libkohana2-modules-php package currently depends on php5 php5-cli . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: libkohana2-modules-php -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUp4XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHhoQP/1ycYMhZ4+Jy2bVQkVFm1yjm Q8HbGLJhVV89Pg+ipNPs6JxSUBDEZxhy4kqvZKPAHertpJEgjQwX66G268igAPrY aIIQ1NIrC3SoGnjmNaofKshAkTd1Pj2yJjCgt3PVKLwkcML5CZXmb8ufP4wWV+Bt Ye2H8f/DtiX0mE+SrzhkhCMSrl/KNgi9BApSW1UMaVnoNYEEvaIaAbBwCGhYZRdB 8/iTRYn/gnR8FHMd/ea5gRCiMbGW1uQcOn6i3Od62tsyCjtWrWG8rfr/XGaMouHi 3ko5qfQt+G2M/CJcM4ZVEcKQvqojmDdGuAdDNnYZPu3YCI7/967woGK7nj/Y5QnP bMwoBBn+fdRgFwv2+A+u4lawbbzw4yS4DX3O2Vo58IahzolEBQGKrUYnoRd5r8Vp WfAoGt75Ry4JHYQYTtDmjuUp2WvoVMmvjLP7WeXjC1EjC5nN1qK663TNEjOBSfjn Kb1phKP0rexPAb2sd1RZ1jeKtUvTLMsIAY1eIyIOkcdSkjAnKlRxuPILSvnpRF6y ynTJoROtrm9KAlIKVDFubVJOnnPytMOxiFUqYTcq9MBgf629i2TxXfJWYDe0X6EW Jk1DDj53WGfWf9CrKwivbkP0C6qGM7EBGOuON5b1FfUbLOMJ55N1gw49Gro8G9Jq LgS2x8g9DO7lG36BFq1j =DAd8 -END PGP SIGNATURE-
Bug#821507: icinga-web-config-icinga2-ido-pgsql: PHP 7.0 Transition
Package: icinga-web-config-icinga2-ido-pgsql Version: 1.13.1-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The icinga-web-config-icinga2-ido-pgsql package currently depends on php5 php5-pgsql . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: icinga-web-config-icinga2-ido-pgsql -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUpwXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHymwP/Rh/u7PGSxcqSPOier90a2yl PwfG0MsvT7GWsjLA6pn5iidzzVrsBceGQp4kry+XT2bEQUxp4+w24fId2dIl/VOS Zsql/iEBslaYs0aOnQbeuUO9BZhYcQVso+B99Ujv9a+qtiXK/ZtjbujPfbmi+ZzM av1gxUUhzRk7SS4BCrItKefqYF4JEjC3JNvMmDW3fXmqrqFuAfCIU+JQSeaHZNCH ZnOx3/yNnZK0BdAIF/AcXwrFlqrqa2zDRHnUbXoz+rSGyGJL7L7L2CmryMfIiWi3 tdSlxCCliULl29TKq98odaGZmFIlfOBZCPhIjpsmPzePrR0YgyqsGgoQN/hh1rkD kDHQk/sBGo4eEHaPQdTkshdYEKECX+fcrUl5mwFEI3QjSjB4isey4dHHWEtqi+51 jMw4XYOi6J72TXxnWszr91z4/f/AjSaD9E7MqV0sJOcNAlaNmNbqwt5/DtxkwkiT WO1vh7oF4Kbzxk903F2saNXamdzDZTr7WBH691PYMJyx2+oR4rMla6SHTMG7GWJ8 tt9OYAcpj1YGRLyxG9UleoK2Q5rNNd5NTNHBzvgOsiu3Minq4KsfdCbVIJ+TMsFL Jvo4VnsObErPsjay0znEPFm0mg0mF0h0MK+cAsxYTsgLKm5usmk10QcsEmHJfYjQ UYwXpqIGyaG4s37W3603 =mDvH -END PGP SIGNATURE-
Bug#821508: ilohamail: PHP 7.0 Transition
Package: ilohamail Version: 0.8.14-0rc3sid6.2 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The ilohamail package currently depends on libapache2-mod-php5 php5 . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: ilohamail -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUpxXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHA3cQAOXQtNiSB9Bk0+HajVOGL8jG 6KIxatXeAJ1mJX63hBqc5/fpm1m2eC4ufjkF7n5FnA5ESBU8OyAHDs85mPiTwrya aTsPKKGmVNHk94o51p8meQCiuxeUewn5gJQMCXKZ8tzxHNDlmdEvBVmQo/tpcC51 azRIhdTYgANOoyAeEzScYvbLuspTknuTA8PlKnflN4Y5+MV5Zy/0Lw0mnQTEq2nc yrIS8fUlJQPJfDYcLiNMtk1H7wJgkAg4AApnU3XYiQ/qKARSRwI2q0sayDWAtnhT Yj6RHmTuMCgOZftvGguOwM5gx5IrS3wa6sL+rcVDBGNYhMFNLtd2IlcqJdOFfnXD E4Xy8p4nLU8kB3VO+39nIq2gGKo2UtdQO6yJEVwZUCfho6Z8AwJdA38J+YJnNfX2 7PP7aFvtzbwO23Z5OaxdE40dNzt71rfg3D9Pec+bBW94nUJi2g5qc374EUgqYjz3 keCr5bjQ+7jriP5GjdXywodgw8gq7Z6Mrb4ogerpO+6O80L4prLdse6yPhDgKA7W QmJRns79Xrawdbtv4vCUl0DF6WNuFoGAcDUGulLP2d3zt93Hl6yAE2H6k53RXXAF RX5JS1vDVgIZfquGojTY7eQli402Ag55WilK+nbMV7u+CGWi0BUaIPR1wi5NDpyj RR2JH3VY3/3IkSw5pmkf =zSjr -END PGP SIGNATURE-
Bug#821520: libkohana3.1-core-php: PHP 7.0 Transition
Package: libkohana3.1-core-php Version: 3.1.5-1.1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The libkohana3.1-core-php package currently depends on libapache2-mod-php5 libapache2-mod-php5filter php5 php5-cgi php5-cli php5-fpm . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: libkohana3.1-core-php -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUp6XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHfeEP/1slN45R5r7Dhx2qyg71GxZs qYZ9Iwi4e3WVvNDPavNQXCjnFog1I4n9tohbq5lfb5W7WTctQWz0LHNSy8xGx2Oj AtCHQY9v8TaOAxOZ9dt3g6KMaCk8XkWrVKqZxSP05WJIiQY4A9dnRq3O10NfUgOR Y+uD0Pv+cgRO7OjKyOVdlVCOYXkNIQoV2pITD3x1zt88Y2i3ctTce8MuQUFYz+wR DfNU9LfHbwfIN9LwZdevt3fD5HE4Oszp+Kim5nuW9594N8OxM3KtOVLTqQ7wll7Y imZuc6r4Br5OOrRIHwnkh3clLSdJ1Pdfp3/JSQkbwsTpy9h0xlvbHc1lBjxubBXH VyeL9/c6MXDV6lfzqUlDZMSiZQA3+5edN7wNaXTxxFepE7rIZ6/SXGjNaqoYl7tt LsMTfSfw4Dw/kpVFa2aX4sz7RksXXej5RJs0Bc3z/Us77xUz75TLpd1tQ3n84mli 55+iRi5Qk3IqNxXN9ra4Ge0bmunV75X3hKdmJxumabuHL/P+vgUJ+CO0V6Sg6Kpv NWRVV5Io7vAd6n1XCu5WUN9wZLy4GIpqz+OmnXSfMkpIaSRjEVyY4gUTj3DP4aW/ OvuMPYAqCCQdYd2qS3G253OUhdisV9N54EysmoNbnJ+/C15Q//qT/JBihDd8bHL+ jE51aHZBoE6olvCukHE6 =1gDG -END PGP SIGNATURE-
Bug#821519: libkohana2-php: PHP 7.0 Transition
Package: libkohana2-php Version: 2.3.4-2 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The libkohana2-php package currently depends on php5 php5-cli . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: libkohana2-php -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUp5XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHeK8P/1ney1v3Drf0UW3d5hxbco5V To1Kxl90ARHv4HGkLcco0uRTGmhqIYI9rUdtH9TsBILnAaOzS+xOY4cQRW2qpcHc ndhP4EMYJHC7pZ3Rvr0nmfVIKyIVGoNUZopPUsZmYCpp/5io8ZPNTs0LsQp9mxG3 keBaBmDn641IFZBfEqrVT7Pg6wuxrIGk/S6swpfGJo2QVAFNjcVPSApM0DOfUmvm iertu0ocln7rccU7g/EnqVSiRRwAxwUNvruQiedaFCYvZRU6UuxTGTRqz52eUhAC QBlRyIGxVmi1Fl8K91Md+7FtbnwXSgUhAWb7O5kpsoo1XQjuuYpmxDUhutao1yg2 YuKM/iT7zVOdpp/+vni0D1qQV490ly2sl5R3/AiCORxy2gmWBWpnN4wwlAXltXoP lmM9aTg11AwhY6WDehsCP/X+BfR/QhngHLIBCltc+4P9TlIdIW81wzlZqSinypg7 +DaQj8m0EkgyHIpN2+4jfALEQwbJoJCdGFh3QRMtR0fmT/zQR41KZCcFVGtIDsoY q8KJ9B5s7/giUwnk7c4tAvrTGhAFvc6qRsD3l75pc6720vsm2z26Qhw2JxUBvUlq uEzybDevpYvzVl11M3CqUuQL+Yy6Kht6g7wQB9VF1Nyyu3LJelSF9U+AGDspVniU 0riEKcXGmRsnDxhjzdz0 =TbhR -END PGP SIGNATURE-
Bug#821510: ldap-account-manager: PHP 7.0 Transition
Package: ldap-account-manager Version: 5.3-1 Severity: important User: pkg-php-ma...@lists.alioth.debian.org Usertags: php7.0-transition -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), this bug is a part of ongoing php7.0 transition. It is filled as important, but the severity will be bumped to serious within quite short (~month) timeframe as the transition was announced almost 3 months ago. The ldap-account-manager package currently depends on php5 php5-gd php5-ldap . PHP 7.0 has landed in unstable with substantial changes to the packaging: 1. Every package built from src:phpMAJOR.MINOR now include phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm. 2. Accompanying src:php-defaults builds 1:1 mapping to a default MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you specify a dependency, please use the generic name, unless you absolutely know that won't work for you. 3. Every path in the system has been changed to a versioned, e.g. /etc/php5/cli is now /etc/php/7.0/cli 4. dh_php5 is now dh_php 5. php-pear is not built from independent source package. 6. master-7.0 branches of several extensions (php-apcu, xdebug, php-apcu-bc) can be used as a template how to change the PHP extension packaging. It's mostly cut since the d/rules tries to figure-out most of the variables from debian/ directory. 7. pkg-php-tools package now supports PHP 7.0 packaging and if your package uses pkg-php-tools a simple binNMU is all it might need 8. PHP 7.0 has changed extension API, so most-if-not-all extensions need work from upstream to be compatible with PHP 7.0. 9. We expect to ship next Debian release (stretch) only with PHP 7.0, that means that all packages needs to be made compatible with PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly maintained software. However some extensions has been deprecated (f.e. mysql) and thus old unmaintained software will stop working and it will have to be either patched or removed from stable Debian. So what you need to do: Replace every occurence of php5 with just php, e.g. if you depend on 'php5' then you just need to depend on 'php'. Also if you package a web application and depend on specific SAPI, I would recommend depending just on 'php' package and let the user decide whether he will install php-fpm, libapache2-mod-php or php-cgi. The script that was used to get the list of packages for MBF was not a particular smart one (so it doesn't detect alternatives, etc.), so if there's a false positive, please excuse me and just close the bug with short explanation. The other options that might be used with packages that don't and won't support PHP 7.0 is to remove the software from Debian by changing the title of this bugreport to: RM: ldap-account-manager -- ROM; doesn't support PHP 7.0 reassigning it to ftp.debian.org pseudo-package and changing severity to 'normal'. Also feel free to contact the maintainers at one of the lists: pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages pkg-php-p...@lists.alioth.debian.org -- for PHP extensions pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all Cheers, Ondrej - -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJXFUpyXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH2NcP/1cqKqKtqRDfJuAhsEABoHCv VuL4rreP7PgZdcFd2w1WBsb5CFAAFrf8oDb+wj/XDaueggc9pfdESq0LNNWkuDMP 5SQfBkIXrhapP5UyE0di63Ixtu9iuA7+K8mWiS6zfRZ7RSmVCxhaWTfD65+Ooq9p zqGkdT9qy/+milOBdcqnESM4A+MqGIApKpWGsJtXGQW67lRfU4JgNHC/R1FBAyAG cCS45Wn/LMXsbkJ1XAreV4RZD7Q56XjwBJZaNEki/+V1fDC2vNqzubSEnQSI03JL UHNJI5mSQ7icQtbxxEByExVWLa/6o2nXvhWpeayVopFwBM3PZzm0xvudTO6MmeYI hEWySs2IMjbGsQtta98YX7ZoZyUDMCMpiBQbl1bliF+Qlepk7/yHFVqM0kvK4CWG qOM6i9QXrjk5qFNssfmoHjPD4L1P1gV/JRfVNwAepQwipCx9xDQ90wmT5h3KVK3y EwZox44JOnxrTanciW+NG8YUsPrR3n4Ieff+crxGySEMTjQgYICkWxC9tBOB0y13 bstC6x/XBMXGKz/gDYsurKynRHnPFdOPkGG1DETqkRKPXMvVnIG/v7ss1DRBivkS LHB112pE1zxvpIq6EjXIrDErPjbKGV3hwY/bIBW9ow87SkjuBktiQZE7wPz7BnFB kTWKJb6PwHJ7msymE3VO =gx/c -END PGP SIGNATURE-
