Bug 105673 - ~ppc and ~amd64 keywording needed for dev-lang/php and related ebuilds
|
Bug#:
105673
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P1
|
|
Resolution: FIXED
|
Assigned To: php-bugs@gentoo.org
|
Reported By: jakub@gentoo.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: ~ppc and ~amd64 keywording needed for dev-lang/php and related ebuilds
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2005-09-12 04:30 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:
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
Marked ~ppc except for firebird, that doesn't build on ppc.
Sorry, forgot to remove ppc@
dev-php/PECL-Fileinfo-1.0 builds/runs fine on my ppc. (macmini)
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.
After checking, these all appear to be marked ~amd64. I don't know why the bug
was not updated.
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.