[pkg-php-pear] Bug#821605: php-pdfparser: PHP 7.0 Transition

[Ondřej Surý]

Package: php-pdfparser
Version: 0.9.25+dfsg-1
Severity: important
User: pkg-php-maint at 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&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: 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-pear at lists.alioth.debian.org -- for PEAR related packages
pkg-php-pecl at lists.alioth.debian.org -- for PHP extensions
pkg-php-maint at 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

iQJ8BAEBCgBmBQJXFUq5XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
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-----