php-igbinary no longer compatible with php5.6/7.0/7.1/7.2

[Frenck]

Since the last published version of the php-igbinary package, the package no longer provides for older/other PHP versions.

Before
=================
Package: php-igbinary
Version: 2.0.7-1+ubuntu16.04.1+deb.sury.org+1
Priority: optional
Section: php
Maintainer: Debian PHP PECL Maintainers <email address hidden>
Installed-Size: 656 kB
Provides: php5.6-igbinary, php7.0-igbinary, php7.1-igbinary, php7.2-igbinary, php7.3-igbinary
Depends: php-common (>= 1:7.0+33~), phpapi-20180731 | phpapi-20170718 | phpapi-20160303 | phpapi-20151012 | phpapi-20131226, libc6 (>= 2.14)
Download-Size: 101 kB
APT-Manual-Installed: no
APT-Sources: http://ppa.launchpad.net/ondrej/php/ubuntu xenial/main amd64 Packages
Description: igbinary PHP serializer
 Igbinary is a drop in replacement for the standard PHP serializer.
 Instead of time and space consuming textual representation, igbinary
 stores PHP data structures in a compact binary form. Savings are
 significant when using memcached or similar memory based storages for
 serialized data.

After
=================
Package: php-igbinary
Version: 2.0.7-1+ubuntu16.04.1+deb.sury.org+2
Priority: optional
Section: php
Maintainer: Debian PHP PECL Maintainers <email address hidden>
Installed-Size: 167 kB
Provides: php7.3-igbinary
Depends: php-common (>= 1:7.0+33~), phpapi-20180731, libc6 (>= 2.14)
Download-Size: 45.5 kB
APT-Sources: http://ppa.launchpad.net/ondrej/php/ubuntu xenial/main amd64 Packages
Description: igbinary PHP serializer
 Igbinary is a drop in replacement for the standard PHP serializer.
 Instead of time and space consuming textual representation, igbinary
 stores PHP data structures in a compact binary form. Savings are
 significant when using memcached or similar memory based storages for
 serialized data.

This renders the use of older PHP version useless for us (since we use packages that rely on this one).

[Frenck (frenck)]

Wrong location for this report. Please close.

[Hans Joachim Desserud (hjd)]

I'm closing this based on your comment. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.