ryandesign at macports.org
Fri Aug 10 17:08:29 PDT 2012
On Aug 10, 2012, at 09:17, Alexandr Kobzarenko wrote:
> Ryan Schmidt wrote:
>> On Aug 10, 2012, at 00:56, Alexandr Kobzarenko wrote:
>>> ---> Updating database of binaries: 100.0%
>>> ---> Scanning binaries for linking errors: 5.2%
>>> Warning: Error parsing file /Applications/MacPorts/Python 2.7/Build Applet.app/Contents/MacOS/Python: Error opening or reading file
>>> ---> Scanning binaries for linking errors: 5.4%
>>> Warning: Error parsing file /Applications/MacPorts/Python 2.7/Python Launcher.app/Contents/MacOS/Python Launcher: Error opening or reading file
>>> ---> Scanning binaries for linking errors: 100.0%
>>> ---> No broken files found.
>> Does /Applications/MacPorts/Python 2.7/Build Applet.app/Contents/MacOS/Python exist?
>> What about /Applications/MacPorts/Python 2.7/Python Launcher.app/Contents/MacOS/Python Launcher?
>> What does "port -v installed python27" say?
> I dont have path /Applications/MacPorts/Python 2.7/
> sh-3.2# port -v installed python27
> The following ports are currently installed:
> python27 @2.7.3_0 (active) platform='darwin 12' archs='x86_64'
Ok, so then presumably whatever method you used to remove Python also removed parts of MacPorts Python, which is now confusing the rev-upgrade portion of MacPorts which expects all of a port's files to actually exist.
To get those parts back, just deactivate and reactivate the port:
sudo port -f deactivate python27
sudo port activate python27
More information about the macports-users