[pkg-php-pear] Bug#814809: Moving forward with the PHP 7.0 transition [Was: phing depends on php5-xdebug, which is not available anymore]

David Prévot taffit at debian.org
Tue Feb 16 02:12:53 UTC 2016

Control: clone -1 -2
Control: reassign -2 pkg-php-tools
Control: found -2 1.31
Control: retitle -2 Please, be ready for PHP 7.0 transition
Control: forwarded -2 https://lists.debian.org/debian-devel-announce/2016/01/msg00002.html
Control: block -1 by -2
Control: found -1 2.12.0-1

Hi Matthias, Mathieu, and all,

On Mon, Feb 15, 2016 at 05:09:51PM +0100, Matthias Klose wrote:
> Package: phing
> Version: 2.13.0-1
> Severity: serious
> Tags: sid stretch
> phing depends on php5-xdebug, which is not available anymore, it should
> depend on php-xdebug (not providing php5-xdebug)

As already pointed not so for away before (#810526#10 and #811431#10):
you may wish to not file such bugs currently [0]: the (soon to be)
ongoing transition of php will require a lot of rebuild (and NEW
processing). We already know that, but all the tools are not yet in

  0: https://lists.debian.org/debian-devel-announce/2016/01/msg00002.html

As a matter of fact, this php5-xdebug dependency is generated at build
time by pkg-php-tools, so pkg-php-tools needs to be ready for PHP 7.0
transition in order to move forward. pkg-php-tools also generates a
dependency on php5-common that is not what we want for Stretch, and
we’ll need to rebuild (no binNMU for arch:all…) every PHP class anyway
(removing the “5” from every “php5-*” (build-)dependency, recommends,
etc. in the process). Increasing the workload of handling all of that by
adding individual bug reports for every package is not going to make the
change happen sooner or on better terms IMHO.

[ pkg-php-tools ]

About the “root” issue, Mathieu, what are the current blockers holding
the still current “pkg-php-tools package is still WIP”? [0] Is there
anything we can help with in order to start making our PHP classes ready
for the ongoing transition?

Among the things I was wondering that might need handling in order to
make this transition possible without having to deal manually with every 
version of every (build-)dependency, recommendation, etc. of every

[ php-defaults ]

It seems like the packages currently built from the php-defaults source
(e.g., php, php-common, php-cli, etc.) are lacking a proper version
number (something like 7.0.3-* could have been useful to prepare
properly versionned reverse dependencies), is there a plan to use an
epoch in order to provide a useful version scheme (as e.g., java-common
0.56 source builds the default-jre 2:1.8-56 binary depending on
openjdk-8-jre –OK, the 8 in 2:1.8-56 is a bit hidden, but it seems to be
reliable for a while to point at the main version of the Java engine–)?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-php-pear/attachments/20160215/2b9da6f2/attachment-0001.sig>

More information about the pkg-php-pear mailing list