Issue
When trying to upgrade MAMP pear the following error is raised:
Notice: unserialize(): Error at offset 276 of 1133 bytes in Config.php on line 1050
ERROR: The default config file is not a valid config file or is corrupted.
Some suggestions how to fix this?
Steps to reproduce:
- Installed MAMP (version 2.0.5)
- cd /Applications/MAMP/bin/php/php5.3.6/bin
- sudo ./pear upgrade pear
- above mentioned error is thrown
Update (1):
Based on answer 8375349/420953 I tried 2 possibilities to fix this
- A: delete pear.conf
- rm /Applications/MAMP/bin/php/php5.3.6/conf/pear.conf
- B: edit pear.conf
- change "php_dir";s:44 to "php_dir";s:43
both resulted in error:
Could not get contents of package "/Applications/MAMP/bin/php/php5.3.6/bin/pear". Invalid tgz file.
upgrade failed
Update (2):
running
- which pear
results in output
- /usr/local/bin/pear
With this, I noticed that I was using the "local" version of PEAR.
I removed it with
- sudo pear uninstall pear
and then tried to upgrade the MAMP version of PEAR with
- /Applications/MAMP/bin/php/php5.3.6/bin/pear upgrade pear
this results in error
Cannot install, php_dir for channel "pear.php.net" is not writeable by the current user
upgrading with
- sudo /Applications/MAMP/bin/php/php5.3.6/bin/pear upgrade pear
installs it locally (again).
running
- which pear
outputs
- /usr/local/bin/pear
this brings me back to the starting point of Update (2). Seems that I am not able to upgrade PEAR under a MAMP directory.
Update (3):
I posted question
because my assumption is that the root of this issue is related to MAMP PEAR config.
Update (4):
I did not install a local PEAR version and this was causing quite some issues. After also installing a local version (and not only the MAMP) version, upgarding the MAMP version worked perfectly.
Solution
People with the your exact problem seem to has solved it in this MAMP forum thread.
You can either delete /Applications/MAMP/bin/php/php5.3.6/conf/pear.conf
, or change a line in that file from "php_dir";s:44
to "php_dir";s:43
.
Answered By - Alex
0 Comments:
Post a Comment
Note: Only a member of this blog may post a comment.