On Nov 22, 2013, at 15:38, david laxer wrote: > I did this: > > 701 sudo port -v selfupdate > 703 sudo port upgrade outdated > > Also, this: > > 733 port -qv installed > myports.txt > 734 sudo port -f uninstall installed > 735 sudo port clean all > > and this: > > sudo ./restore_ports.tcl myports.txt > > >> Why does > >> /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/numpy/core/_methods.py > >> already exist if it does not belong to a port? > I've done Ruby work in the past. Also, Boost installation. Could Brew > cause this?
/opt/local is MacPorts’ directory. Nobody else should be installing software there. This file is either on your system because you previously installed the py26-numpy port, then somehow cleared MacPorts’ database of what ports are installed without actually uninstalling the py26-numpy port, or because you installed a 3rd-party software package that was itself built using MacPorts and it installed files into the MacPorts directory. This situation is discussed (for a different port (expat), but it’s the same principle regardless what port it is) here: https://trac.macports.org/wiki/ProblemHotlist#xmlwf You can force the activation of py26-numpy, but if this one file exists and shouldn’t, it seems unlikely that it would be the only file, so you may run into this problem again later unless you fix it now. If you cannot explain why this file is there, the safest fix would be to uninstall MacPorts completely: http://guide.macports.org/chunked/installing.macports.uninstalling.html Then reinstall MacPorts and the ports you want (using the restore_ports.tcl script if you like). _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
