I have been running MAMP Pro 3.05 successfully in Yosemite up to DP4 on a partition that was a clean install of Yosemite.
I now have run the installer for DP5 over m
This works also for Mamp Pro 2.1.1 on Yosemite.
MAMP Folks just posted the workaround
Workaround for the 10.10 Preview 5 bug: Rename the file “envvars” located in /Applications/MAMP/Library/bin into “_envvars”
Test Update: It works!
Just found workaround from MAMP on Twitter
Workaround for the 10.10 Preview 5 bug: Rename the file “envvars” located in into “_envvars”
I tried that solution and others over and over and did not work until I realised I should be restarting completely MAMP, after doing so, this simple change from envvars to _envvars worked like a charm.
You can completely restart MAMP checking if there's any process going on, open the terminal:
ps -cvx | grep "mysql"
That will output a list of the processes that involves mysql at the time, with a PDI associated, so you only have to take that number and:
kill PDI
Where PDI is the number associated to the process, after that, if you write again the command ps -cvx | grep "mysql"
the pointer should be empty.
Once done, only execute MAMP.
Try this::
Rename the file “envvars” located in /Applications/MAMP/Library/bin into “_envvars” only for OS X Yosemite.
MAMP Folks just posted the workaround
Workaround for the 10.10 Preview 5 bug: Rename the file “envvars” located in /Applications/MAMP/Library/bin into “_envvars”
Test Update: It works!
Works for Yosemite release too!
Apparently the MAMP folks are working on a work-around:
https://twitter.com/mamp_en/status/496655943506350081
Follow their account for updates.