Opened 17 years ago

Closed 16 years ago

Last modified 16 years ago

#2125 closed defect (fixed)

BUG: problem deactivating adium port

Reported by: reilles@… Owned by: tobypeterson
Priority: Normal Milestone:
Component: ports Version: 1.0
Keywords: Cc: rshaw@…


the adium port leaves files behind it when it is deactivated.

I deactivated the 0.62 version of adium port, in order to install the new one.

The build and install phases are fine, but i get ---> Activating adium 0.63_0 Error: Target returned: Image error: /Applications/DarwinPorts/ Contents/PlugIns/Gaim.AdiumPlugin/Contents/Frameworks/Libgaim.framework/Libgaim already exists and does not belong to a registered port. Unable to activate port adium.

Indeed, these files are left by the deactivate target. Workaround is to manually remove the /Applications/Darwinports/ directory (activate -f should work too) This problem happens only with different versions of the adium port. port deactivate adiium && port activate adium works

Change History (6)

comment:1 Changed 16 years ago by olegb@…

Owner: changed from darwinports-bugs@… to toby@…

assigning to maintainer

comment:2 Changed 16 years ago by rshaw@…

Cc: rshaw@… added

There are two problems at work here.

comment:3 Changed 16 years ago by rshaw@…

This actually looks like a combination of two problems:

One is a bug in the base/ code where the uninstall code is not properly removing symbolic links that point to non-existant files. I will look at this and fix it.

The second is the port itself since the installed port is apparently creating symbolic links to things using an absolute path:

`-- PlugIns

`-- Gaim.AdiumPlugin

`-- Contents

`-- Frameworks

`-- Libgaim.framework

Headers -> /opt/darwinports/dports/aqua/adium/work/adium/Plugins/Gaim Service/Libgaim.framework/Versions/Current/Headers

This would of course not run once you clean your port build area since the files are pointing off to the build space instead of the location. Toby will need to fix this one.


comment:4 Changed 16 years ago by rshaw@…

Ok, the problem with symlinks not being removed during deactivate has been fixed in the base/ code.


comment:5 Changed 16 years ago by rshaw@…

The Adium port should now properly deactivate with the latest base/ code fixes. However, existing installations will not deactivate properly since the problem came from the contents file map being incorrect (missing symlinks). Once you reinstall using the new base/ code, the deactivate should work correctly.


comment:6 Changed 16 years ago by toby@…

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.