php-zeta-base unit tests fail due to png optimization in php-zeta-unit-test

[Nish Aravamudan]

I was investigating the build failure of php-zeta-base 1.9-2build1 (https://launchpadlibrarian.net/240582668/buildlog_ubuntu-xenial-amd64.php-zeta-base_1.9-2build1_BUILDING.txt.gz) and noticed that the PNG optimization has modified the php-zeta-unit-test PNG file /usr/share/php/data/UnitTest/design/class_diagram.png from:

-rw-r--r-- 1 root root 163K Feb 13 17:43 /usr/share/php/data/UnitTest/design/class_diagram.png
/usr/share/php/data/UnitTest/design/class_diagram.png: PNG image data, 1347 x 1032, 8-bit/color RGBA, non-interlaced

in Debian to:

-rw-r--r-- 1 root root 75K Feb 13 15:19 /usr/share/php/data/UnitTest/design/class_diagram.png
/usr/share/php/data/UnitTest/design/class_diagram.png: PNG image data, 1347 x 1032, 8-bit gray+alpha, non-interlaced

I'm assuming this is due to

pkgstripfiles: Running PNG optimization (using 4 cpus) for package php-zeta-unit-test

from the build of php-zeta-unit-test.

It seems like the PNG mangling should be disable for php-zeta-unit-tests, as it has some hard-coded meta data in dependent packages.

[Nish Aravamudan (nacc)]

php-zeta-unit-test (1.0.2-2ubuntu1) xenial; urgency=medium

  * Disable PNG mangling (LP: #1549046).

 -- Nishanth Aravamudan <email address hidden> Tue, 23 Feb 2016 16:18:37 -0800

[Nish Aravamudan (nacc)]

With php-zeta-unit-tests 1.0.2-2ubuntu1, php-zeta-base 1.9-2build1 successfully builds & tests.

[Launchpad Janitor (janitor)]

This bug was fixed in the package php-zeta-unit-test - 1.0.2-2ubuntu1

---------------
php-zeta-unit-test (1.0.2-2ubuntu1) xenial; urgency=medium

  * Disable PNG mangling (LP: #1549046).

 -- Nishanth Aravamudan <email address hidden> Tue, 23 Feb 2016 16:18:37 -0800

[Steve Langasek (vorlon)]

php-zeta-base now fails to build with the following error:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/«PKGBUILDDIR»'
phpunit
Class 'DOMDocument' not found
debian/rules:17: recipe for target 'override_dh_auto_test' failed

[Steve Langasek (vorlon)]

> Class 'DOMDocument' not found

This appears to be bug #1549552.