Edit report at http://pear.php.net/bugs/bug.php?id=18388&edit=1
ID: 18388
Updated by: [email protected]
Reported By: edomat at gmail dot com
-Summary: Parenteses error in REST.php line 232
+Summary: Parentheses error in REST.php line 232
Status: Closed
Type: Bug
Package: PEAR
Operating System: Debian GNU/Linux
Package Version: SVN
PHP Version: 5.3.6
Assigned To: dufuz
Roadmap Versions:
New Comment:
-Summary: Parenteses error in REST.php line 232
+Summary: Parentheses error in REST.php line 232
Previous Comments:
------------------------------------------------------------------------
[2011-03-23 13:31:57] dufuz
Thanks for the catch
------------------------------------------------------------------------
[2011-03-23 13:29:52] dufuz
-Summary: Parenteses error en REST.php line 232
+Summary: Parenteses error in REST.php line 232
-Status: Open
+Status: Closed
-Assigned To:
+Assigned To: dufuz
This bug has been fixed in SVN.
If this was a documentation problem, the fix will appear on pear.php.net
by the end of next Sunday (CET).
If this was a problem with the pear.php.net website, the change should
be live shortly.
Otherwise, the fix will appear in the package's next release.
Thank you for the report and for helping us make PEAR better.
------------------------------------------------------------------------
[2011-03-22 22:47:49] edomato
Added #patch bug:18388;patch:rest-parenteses-fix;revision:1300834069;.
------------------------------------------------------------------------
[2011-03-22 22:43:55] edomato
Description:
------------
On line 232 of PEAR/REST.php script it reads:
if (System::mkdir(array('-p', $cache_dir) === false)) {
when it should be:
if (System::mkdir(array('-p', $cache_dir)) === false) {
making the pear command unusable when the cache directory is not present
------------------------------------------------------------------------
--
Edit this bug report at http://pear.php.net/bugs/bug.php?id=18388&edit=1
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.