Bug 96941 – can't install PEAR, because PEAR is needed?

• Status: RESOLVED DUPLICATE of bug 95931
• Product: Gentoo Linux

[Description Ian P. Christian 2005-06-24 05:51:14 UTC]

I recently upgraded from 5.04 to 5.1 of PHP, and PEAR has gone missing. I 
understand PEAR-PEAR is now needed, but I can't install that, because I don't 
have PEAR 
 
# emerge PEAR-PEAR -av 
 
These are the packages that I would merge, in order: 
 
Calculating dependencies ...done! 
[ebuild  N    ] dev-php/PEAR-XML_RPC-1.1.0  0 kB 
[ebuild  N    ] dev-php/PEAR-Archive_Tar-1.3.1  14 kB 
[ebuild  N    ] dev-php/PEAR-Console_Getopt-1.2  3 kB 
[ebuild  N    ] dev-php/PEAR-PEAR-1.3.5  105 kB 
 
Total size of downloads: 123 kB 
 
Do you want me to merge these packages? [Yes/No] 
>>> emerge (1 of 4) dev-php/PEAR-XML_RPC-1.1.0 to / 
>>> md5 files   ;-) ChangeLog 
>>> md5 files   ;-) metadata.xml 
>>> md5 files   ;-) PEAR-XML_RPC-1.1.0.ebuild 
>>> md5 files   ;-) PEAR-XML_RPC-1.2.2.ebuild 
>>> md5 files   ;-) files/digest-PEAR-XML_RPC-1.1.0 
>>> md5 files   ;-) files/digest-PEAR-XML_RPC-1.2.2 
>>> md5 src_uri ;-) XML_RPC-1.1.0.tgz 
>>> Unpacking source... 
>>> Unpacking XML_RPC-1.1.0.tgz to /var/tmp/portage/PEAR-XML_RPC-1.1.0/work 
tar: A lone zero block at 102 
>>> Source unpacked. 
>>> Test phase [not enabled]: dev-php/PEAR-XML_RPC-1.1.0 
 
>>> Install PEAR-XML_RPC-1.1.0 into /var/tmp/portage/PEAR-XML_RPC-1.1.0/image/ 
category dev-php 
/usr/portage/eclass/php-pear.eclass: line 49: pear: command not found 
 
!!! ERROR: dev-php/PEAR-XML_RPC-1.1.0 failed. 
!!! Function php-pear_src_install, Line 49, Exitcode 127 
!!! (no error message) 
!!! If you need support, post the topmost build error, NOT this status 
message. 
 

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 Ian P. Christian 2005-06-24 05:52:09 UTC]

for some reason, http://bugs.gentoo.org/show_bug.cgi?id=95931 was marked 
invalid, despite being this exact issue. 

[Comment 2 Paweł Hajdan, Jr. (RETIRED) 2005-06-24 06:04:52 UTC]

So why do you report the same bug? Please close it as a duplicate of bug 95931.

[Comment 3 Ian P. Christian 2005-06-24 06:07:34 UTC]

because the other one has been closed, and I don't have permissions to reopen 
it. Am I misunderstanding something? 

[Comment 4 Jakub Moc (RETIRED) 2005-06-24 06:34:59 UTC]

Reopening the original bug.

*** This bug has been marked as a duplicate of 95931 ***