Your message dated Sun, 24 Apr 2016 09:54:00 +0000
with message-id <[email protected]>
and subject line Bug#821563: fixed in php-apigen-theme-default 1.0.2+dfsg-2
has caused the Debian Bug report #821563,
regarding php-apigen-theme-default: 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.)


-- 
821563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821563
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: php-apigen-theme-default
Version: 1.0.2+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 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&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-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:

[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

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

--- End Message ---
--- Begin Message ---
Source: php-apigen-theme-default
Source-Version: 1.0.2+dfsg-2

We believe that the bug you reported is fixed in the latest version of
php-apigen-theme-default, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Florian Schlichting <[email protected]> (supplier of updated 
php-apigen-theme-default package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 22 Apr 2016 23:38:41 +0200
Source: php-apigen-theme-default
Binary: php-apigen-theme-default
Architecture: source all
Version: 1.0.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers <[email protected]>
Changed-By: Florian Schlichting <[email protected]>
Description:
 php-apigen-theme-default - ${phpcomposer:description}
Closes: 816795 821563
Changes:
 php-apigen-theme-default (1.0.2+dfsg-2) unstable; urgency=medium
 .
   * Rebuild against PHP 7 (Closes: #821563)
   * Update VCS fields to use secure URI
   * Add myself to Uploaders and remove David as requested (Closes: #816795)
   * Declare compliance with Debian Policy 3.9.8
Checksums-Sha1:
 e4afb32326005fb663671d27d2ebaf4484184d6e 2135 
php-apigen-theme-default_1.0.2+dfsg-2.dsc
 903398a527383308ff7b8e59811b9c52583f5eb5 3992 
php-apigen-theme-default_1.0.2+dfsg-2.debian.tar.xz
 50eecc7b8391f1008e2a25de18bdae463a5a0e2e 31864 
php-apigen-theme-default_1.0.2+dfsg-2_all.deb
Checksums-Sha256:
 a0a31c7b600ba1a711c2354162e8946effa905c3ff87d4b43bc2b58002d3e194 2135 
php-apigen-theme-default_1.0.2+dfsg-2.dsc
 8e52e311c1073b492d8eb4739e7805a4b3821bc53ac4bddf110ed3d9b9a4c6b2 3992 
php-apigen-theme-default_1.0.2+dfsg-2.debian.tar.xz
 9079f66f764a3646be242d6e83da47f0d16a50ec7887e9b5123ab31843a85698 31864 
php-apigen-theme-default_1.0.2+dfsg-2_all.deb
Files:
 a44fb65bff77d1f916690be24bf911e3 2135 php optional 
php-apigen-theme-default_1.0.2+dfsg-2.dsc
 d0bac46a2c8b5dd3627ecaf7075ec31e 3992 php optional 
php-apigen-theme-default_1.0.2+dfsg-2.debian.tar.xz
 0d7c300858f8f2f60e81bc5d4ba431ef 31864 php optional 
php-apigen-theme-default_1.0.2+dfsg-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJXHILuAAoJEBKXO25y3Ae15lwP+weEvFj5PzLdn6Ho4rGlw5Xl
IknfjS+VILZd6aPVAiTKsyA4yTP87CZJhHFDCetfE6zQK7P2djkcVBsn2OqUOHSP
T1n7xLkI08Dou5cJK0JFoGjYY7mL5tzjG1GcSW/R1oY4S2Mv3YFPWMOSgopDG1Z+
Dit3llPyLMjH8q2lU37vsYhI1OUct45ffJDlhUMFBiwwWKB5nNtMdCHcMIWiiPmW
CAkFc/D2P6/nyQ55+kW9GBuXHFzg6CBdIhvZEUh4t35y4qMlfoZALL+qRi6ysC+y
RCRCvcNAyNa+vkTE5bjVQQfClebvT7Lm0aaotKSdHQL8pA9Ah6q0K2AAEJu0/jOp
GmPKeL4fE8f3nYZRGMf2QPvjIqtamRrbjq8TXoZBTue12F3RTWfwfPjwQg4n7L/i
POP4R+kYy197/XbVM2F4ghsktAkzYSbE8IkEn6JrZjAuVe9EJk3RFGH8GPdoErp9
zHA7MyuSrLG0+DKOe1xZYLJshsT9+aM1RQSZ9L7LH542f6sxj5ch3bm5dNM+pSZO
mbUQYJHoQ/XdsghNS+eI9jk7wYyAWoLwb701qM7xY55ocGuoEBj90RMzch6K6Ffz
oLAzBply3V5PjU/G0AfrSbOwJLj+fqypGMDJcYbOH3AlQknxWz/Kw2Qo71sF0/Yh
hAzHdwA6uznUl7DL/7Z6
=oRcQ
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to