| Summary: | dev-php/PEAR-PEAR-1.3.5-r1 seems broken | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jakub Moc (RETIRED) <jakub> |
| Component: | New packages | Assignee: | PHP Bugs <php-bugs> |
| Status: | RESOLVED INVALID | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Jakub Moc (RETIRED)
2005-06-30 06:15:49 UTC
Cannot reproduce. Besides, the PHP 5 ebuilds are package.masked. (In reply to comment #1) > Cannot reproduce. OK, still broken w/ PEAR-XML_RPC-1.3.2 and dev-php/mod_php-5.1.0_beta-r1. I can reproduce this on two boxes. It's really easy - just setting safe_mode = On and open_basedir= "/some/path" in /etc/php/apache2-php5/php.ini is enough for this ebuild to fail. > Besides, the PHP 5 ebuilds are package.masked. Hmm, I thought that they are package.masked to fix bugs before unmasking them. OK, seems like PEAR-PEAR is pretty much broken... $ pear list WARNING: running in safe mode requires that all files created be the same uid as the current script. PHP reports this script is uid: 0, and current user is: root Warning: mkdir(): open_basedir restriction in effect. File(/usr) is not within the allowed path(s): (/usr/share/php:/var/www:/tmp) in System.php on line 249 Warning: mkdir(): open_basedir restriction in effect. File(/usr/lib) is not within the allowed path(s): (/usr/share/php:/var/www:/tmp) in System.php on line 249 Warning: mkdir(): open_basedir restriction in effect. File(/usr/lib/php) is not within the allowed path(s): (/usr/share/php:/var/www:/tmp) in System.php on line 249 Warning: mkdir(): open_basedir restriction in effect. File(/usr/lib/php/pear) is not within the allowed path(s): (/usr/share/php:/var/www:/tmp) in System.php on line 249 Warning: mkdir(): open_basedir restriction in effect. File(/usr/lib/php/pear/.registry) is not within the allowed path(s): (/usr/share/php:/var/www:/tmp) in System.php on line 249 could not create directory '/usr/lib/php/pear/.registry' Hmm... So what about unmerge and reinstall PEAR-PEAR: >>> Install PEAR-PEAR-1.3.5-r1 into /var/tmp/portage/PEAR-PEAR-1.3.5-r1/image/ category dev-php >>> dobin: making pear executable... Warning: main(PEAR.php): failed to open stream: Operation not permitted in pearcmd.php on line 42 PHP Fatal error: main(): Failed opening required 'PEAR.php' (include_path='.:/var/tmp/portage/PEAR-PEAR-1.3.5-r1/image//usr/share/php') in /var/tmp/portage/PEAR-PEAR-1.3.5-r1/image/usr/share/php/pearcmd.php on line 42 Fatal error: main(): Failed opening required 'PEAR.php' (include_path='.:/var/tmp/portage/PEAR-PEAR-1.3.5-r1/image//usr/share/php') in /var/tmp/portage/PEAR-PEAR-1.3.5-r1/image/usr/share/php/pearcmd.php on line 42 !!! ERROR: dev-php/PEAR-PEAR-1.3.5-r1 failed. !!! Function install_pear_after_bootstrap, Line 87, Exitcode 255 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message. Hmmm? Closing, I will open a new bug to make it consistent. |