Debian ships (currently):
php-pear | 5.6.19+dfsg-0+deb8u1 | stable | all php-pear | 1:1.10.1+submodules+notgz-6 | testing | source, all php-pear | 1:1.10.1+submodules+notgz-6 | unstable | source, all
Ubuntu ships:
php-pear | 5.5.9+dfsg-1ubuntu4 | trusty | all php-pear | 5.5.9+dfsg-1ubuntu4.14 | trusty-security | all php-pear | 5.5.9+dfsg-1ubuntu4.14 | trusty-updates | all php-pear | 5.6.4+dfsg-4ubuntu6 | vivid | all php-pear | 5.6.4+dfsg-4ubuntu6.4 | vivid-security | all php-pear | 5.6.4+dfsg-4ubuntu6.4 | vivid-updates | all php-pear | 5.6.11+dfsg-1ubuntu3 | wily | all php-pear | 5.6.11+dfsg-1ubuntu3.1 | wily-security | all php-pear | 5.6.11+dfsg-1ubuntu3.1 | wily-updates | all php-pear | 1:1.10.1+submodules+notgz-6 | xenial | source, all
None of those are 5.6.16+dfsg-2. Would it be possible to confirm if this still occurs in Xenial or unstable?
Debian ships (currently):
php-pear | 5.6.19+ dfsg-0+ deb8u1 | stable | all 1+submodules+ notgz-6 | testing | source, all 1+submodules+ notgz-6 | unstable | source, all
php-pear | 1:1.10.
php-pear | 1:1.10.
Ubuntu ships:
php-pear | 5.5.9+dfsg-1ubuntu4 | trusty | all 1ubuntu4. 14 | trusty-security | all 1ubuntu4. 14 | trusty-updates | all 4ubuntu6. 4 | vivid-security | all 4ubuntu6. 4 | vivid-updates | all dfsg-1ubuntu3 | wily | all dfsg-1ubuntu3. 1 | wily-security | all dfsg-1ubuntu3. 1 | wily-updates | all 1+submodules+ notgz-6 | xenial | source, all
php-pear | 5.5.9+dfsg-
php-pear | 5.5.9+dfsg-
php-pear | 5.6.4+dfsg-4ubuntu6 | vivid | all
php-pear | 5.6.4+dfsg-
php-pear | 5.6.4+dfsg-
php-pear | 5.6.11+
php-pear | 5.6.11+
php-pear | 5.6.11+
php-pear | 1:1.10.
None of those are 5.6.16+dfsg-2. Would it be possible to confirm if this still occurs in Xenial or unstable?