105673 2005-09-12 04:30 0000 ~ppc and ~amd64 keywording needed for dev-lang/php and related ebuilds 2005-09-21 09:24:30 0000 1 1 1 Unclassified Gentoo Linux Ebuilds unspecified All Linux RESOLVED FIXED P1 normal --- 60440 1 jakub@gentoo.org php-bugs@gentoo.org amd64@gentoo.org jakub@gentoo.org 2005-09-12 04:30:55 0000 ppc herd, please, test and keyword the following ~ppc, thanks... dev-lang/php-4.4.0 dev-lang/php-5.0.4 dev-php/PEAR-PEAR-1.3.6 dev-php/PEAR-Console_Getopt-1.2-r1 PEAR-Archive_Tar-1.3.1-r1 PEAR-XML_RPC-1.4.1 amd64 herd, please, test and keyword the following ~amd64: dev-lang/php-4.4.0 dev-lang/php-5.0.4 dev-php/PEAR-PEAR-1.3.6 dev-php/PEAR-Console_Getopt-1.2-r1 PEAR-Archive_Tar-1.3.1-r1 PEAR-XML_RPC-1.4.1 dev-php5/pecl-zip-1.0 dev-php5/pecl-pdo-0.9 dev-php5/pecl-yaz-1.0.4 dev-php5/php-java-bridge-2.0.7 Keywording of the above ebuilds (at minimum) is needed to fix the currently broken dependencies in portage. Please, don't flame me, I did not break it ;) - and TIA! Reproducible: Always Steps to Reproduce: jakub@gentoo.org 2005-09-12 05:07:51 0000 ppc - round 2 DEPEND.bad dev-php5/pecl-pdo-firebird-0.2 - either keyword dev-db/firebird or remove ~ppc dev-php{4,5}/pecl-ps-1.3.1 - either keyword dev-libs/pslib or remove ~ppc josejx@gentoo.org 2005-09-14 09:08:21 0000 Marked ~ppc except for firebird, that doesn't build on ppc. josejx@gentoo.org 2005-09-14 09:08:46 0000 Sorry, forgot to remove ppc@ lejban@gmail.com 2005-09-14 17:01:39 0000 dev-php/PECL-Fileinfo-1.0 builds/runs fine on my ppc. (macmini) jasper_roel@yahoo.com 2005-09-17 06:26:29 0000 dev-php/PEAR-PEAR-1.3.6 dev-php/PEAR-Console_Getopt PEAR-Archive_Tar-1.3.1-r1 PEAR-XML_RPC all of these run fine on my AMD64. dang@gentoo.org 2005-09-21 07:32:24 0000 After checking, these all appear to be marked ~amd64. I don't know why the bug was not updated. cryos@gentoo.org 2005-09-21 09:24:30 0000 I marked many of these ebuilds after trapni missed a few of the deps, and was working off the main bug for getting new style PHP marked in the tree. As such I didn't look for another different bug. See bug 102649 - really amd64 should have been referred back to the main bug I would have thought. Closing it now.