Your message dated Tue, 19 Apr 2016 20:58:26 +0000
with message-id
<caly8cw7lsocxn+ulvzqteq+-v1vy6tox9spppvqhwgyjqxm...@mail.gmail.com>
and subject line Re: Bug#821667: wordpress: PHP 7.0 Transition
has caused the Debian Bug report #821667,
regarding wordpress: PHP 7.0 Transition
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
821667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821667
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wordpress
Version: 4.5+dfsg-1
Severity: important
User: [email protected]
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 wordpress package currently depends on libapache2-mod-php5 php5
php5-gd 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&paste 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: wordpress -- 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:
[email protected] -- for PEAR related packages
[email protected] -- for PHP extensions
[email protected] -- 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
iQJ8BAEBCgBmBQJXFUrnXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHtboQAJSu8KR+Rv2JeSw5TWWeDnPr
3HTCrpKGqOIelf0wFximEYg1OHnnYj+FOuwNNFICoDE7eyV7fJN6vQ00L9AyROIn
47pZK7kiAAT37yro1xrkjnK5/hbkVzqo3667DkUaMpvCtJBuIqkl473nhug4eeFK
QIp7HeziEUqBsL7nn8g8/k4b5IknZ6pTnICGR5J1e790CB0gHAdS3aNDkKPN2kgf
QR1XWDu9LtiBqEUUrWFymgDr/KjygoD5Oe5njewkG5NKrswoNr+zT1lens8t12EF
YQ5wKdXHkP6soHACTD4LtzjgAdKFGV1KbASRtCPtpu8y1hoYCd0D8UFv99Hzjb12
ii7w5pBuXxNJKUjB+8yXty2vNngaQIx/K3xnCRuQEfaAzxOcnGaqMuphrhYEaOxx
oRsjwqexfo1JO5VGWqZzNjbURz8/9O1a4bFNVvK5OL2fYHOOqC6sDdXAuQe4cYJD
oYwFVCyrjdQV+1GnCHOs+wxfj4P6RHr20q2ceonuu0Vdh2mQFrCjCbXRIWsx+mj6
5/OvCPw+nbub+dgOqg4uxgC7x9DGXCq4TMTcGK50tl3Iq5IkNCLRAglZ4kQz1tIX
6YaXULFNR9FcNSq/qsbC1UwYkpxvzDkvyVDSEQPwiyb8m6ldnV/mxxsnoFCk6G7i
C6Qq6G0H/ccR4fymh6RV
=esfr
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Tue, Apr 19, 2016 at 7:15 AM Ondřej Surý <[email protected]> wrote:
> 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.
>
It sure doesn't pick up alternatives, which is what wordpress uses.
Depends: apache2 | httpd,
libapache2-mod-php | libapache2-mod-php5 | php | php5,
ca-certificates,
mysql-client | mariadb-client,
php-gd | php5-gd,
php-mysql | php5-mysql | php-mysqlnd | php5-mysqlnd,
${misc:Depends}
Closing bug.
- Craig
--
Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au
Debian GNU/Linux http://www.debian.org/ csmall at : debian.org
GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5
--- End Message ---
