[pkg-php-pear] Bug#775633: php-crypt-gpg: FTBFS in jessie: exception 'InvalidArgumentException' with message 'Unknown PEAR dependency type 'os'' in /usr/share/php/pkgtools/phppear/source.php:225

[Lucas Nussbaum]

Source: php-crypt-gpg
Version: 1.3.2-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20150117 qa-ftbfs
Justification: FTBFS in jessie on amd64

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
>  fakeroot debian/rules binary
> dh binary --buildsystem=phppear --with phppear
>    dh_testroot -O--buildsystem=phppear
>    dh_prep -O--buildsystem=phppear
>    dh_auto_install -O--buildsystem=phppear
> install ok: channel://pear.php.net/Crypt_GPG-1.3.2
>    dh_installdocs -O--buildsystem=phppear
>    dh_installchangelogs -O--buildsystem=phppear
>    dh_perl -O--buildsystem=phppear
>    dh_phppear -O--buildsystem=phppear
> exception 'InvalidArgumentException' with message 'Unknown PEAR dependency type 'os'' in /usr/share/php/pkgtools/phppear/source.php:225
> Stack trace:
> #0 /usr/share/php/pkgtools/phppear/command.php(98): Pkgtools\Phppear\Source->getDependencies()
> #1 [internal function]: Pkgtools\Phppear\Command->runSubstvars()
> #2 /usr/share/php/pkgtools/base/command.php(181): call_user_func_array(Array, Array)
> #3 /usr/share/php/pkgtools/base/command.php(169): Pkgtools\Base\Command->parseArgs(Array)
> #4 /usr/bin/pkgtools(32): Pkgtools\Base\Command->parseArgs()
> #5 {main}
> dh_phppear: /usr/bin/pkgtools -v --sourcedirectory . phppear substvars returned exit code 1
> make: *** [binary] Error 29

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2015/01/17/php-crypt-gpg_1.3.2-1_jessie.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.