On Mar 24, 2008, at 20:37, Alejandro Aragon wrote:
On Mar 24, 2008, at 8:30 PM, Ryan Schmidt wrote:
On Mar 24, 2008, at 20:23, Alejandro Aragon wrote:
On Mar 24, 2008, at 6:40 PM, skip@pobox.com wrote:
Alejandro> garyw:~ aaragon$ sudo port install aquaterm ---> Activating aquaterm 1.0.1_0 Alejandro> Error: Target org.macports.activate returned: Image error: /Library/ Alejandro> Frameworks/AquaTerm.framework/AquaTerm already exists and does not Alejandro> belong to a registered port. Unable to activate port aquaterm. Alejandro> Error: Status 1 encountered during processing.
Alejandro> What does it mean?
To me it means try this:
sudo rm -r /Library/Frameworks/AquaTerm.framework/Aquaterm sudo port install aquaterm
:-)
I cannot do that, can I? Probably that framework is used by the system.
Nope, that's part of AquaTerm, which is not made by Apple.
More probably, you installed AquaTerm either manually, or with MacPorts before, then removed MacPorts without first uninstalling AquaTerm, then reinstalled MacPorts, so that it now has no idea that it previously installed these files.
That's exactly what I did! How do I fix it? The AquaTerm framework is dated March 19th, and the most recent gnuplot installation March 20th. I was having some issues with macports when compiling the boost library so I uninstalled thinking that the problem may be a bad installation. Should I remove completely that directory and try the AquaTerm installation again?
Yes, just like Skip said: sudo rm -r /Library/Frameworks/AquaTerm.framework/Aquaterm sudo port install aquaterm You could also just tell MacPorts to force the installation: sudo port -f install aquaterm For any file that MacPorts wants to install that already exists, it will first rename the existing file, and tell you about it. You can then manually remove those renamed files later if you want.
It's working now, you guys are the best! On Mar 24, 2008, at 9:56 PM, Ryan Schmidt wrote:
On Mar 24, 2008, at 20:37, Alejandro Aragon wrote:
On Mar 24, 2008, at 8:30 PM, Ryan Schmidt wrote:
On Mar 24, 2008, at 20:23, Alejandro Aragon wrote:
On Mar 24, 2008, at 6:40 PM, skip@pobox.com wrote:
Alejandro> garyw:~ aaragon$ sudo port install aquaterm ---> Activating aquaterm 1.0.1_0 Alejandro> Error: Target org.macports.activate returned: Image error: /Library/ Alejandro> Frameworks/AquaTerm.framework/AquaTerm already exists and does not Alejandro> belong to a registered port. Unable to activate port aquaterm. Alejandro> Error: Status 1 encountered during processing.
Alejandro> What does it mean?
To me it means try this:
sudo rm -r /Library/Frameworks/AquaTerm.framework/Aquaterm sudo port install aquaterm
:-)
I cannot do that, can I? Probably that framework is used by the system.
Nope, that's part of AquaTerm, which is not made by Apple.
More probably, you installed AquaTerm either manually, or with MacPorts before, then removed MacPorts without first uninstalling AquaTerm, then reinstalled MacPorts, so that it now has no idea that it previously installed these files.
That's exactly what I did! How do I fix it? The AquaTerm framework is dated March 19th, and the most recent gnuplot installation March 20th. I was having some issues with macports when compiling the boost library so I uninstalled thinking that the problem may be a bad installation. Should I remove completely that directory and try the AquaTerm installation again?
Yes, just like Skip said:
sudo rm -r /Library/Frameworks/AquaTerm.framework/Aquaterm sudo port install aquaterm
You could also just tell MacPorts to force the installation:
sudo port -f install aquaterm
For any file that MacPorts wants to install that already exists, it will first rename the existing file, and tell you about it. You can then manually remove those renamed files later if you want.
Ryan> Yes, just like Skip said: Ryan> sudo rm -r /Library/Frameworks/AquaTerm.framework/Aquaterm Ryan> sudo port install aquaterm BTW, I ran into precisely these problems when migrating from my old PowerBook to my shiny new MacBook Pro. I naively assumed MacPorts was wholly contained in /opt/local so I just rm -r'd it and started over. I only learned later that it sprinkles some files outside of that tree. I have several times needed to simply zap something MacPorts complained about. Skip
participants (3)
-
Alejandro Aragon
-
Ryan Schmidt
-
skip＠pobox.com