#39376: gnome-keyring @2.30.3_6 can not be installed ----------------------------+---------------------- Reporter: mk@… | Owner: devans@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: gnome-keyring | ----------------------------+---------------------- Changes (by devans@…): * status: new => assigned Comment: Here's the deal. The file is installed outside the MacPorts tree because it has to be to work properly. It is a PAM binary module and it needs to reside in the system PAM module directory for it properly interface with the system PAM implementation. There really is nothing wrong with this port. If you deactivate or uninstall the port using Mac Ports, the file is removed during the deactivate phase. If you reinstall it is installed in the activate phase. This works whether the file is in the MacPorts tree or not (try it). The problem is in step 2 above. By using the brute force remove, you don't remove the file in question (because you didn't use a brute force remove on it too) and you destroy the MacPorts registry so it "forgets" after the new install that it had previously been installed. If you really want to nuke the MacPorts installation and reinstall a new one, you really should uninstall the existing ports and then use the brute force remove. {{{ sudo port echo installed > ~/installed_ports (so you can remember what to reinstall) sudo port uninstall installed (remove all installed ports) rm -rf ${prefix) (now nuke what's left) }}} Do whatever you were going to do such as (upgrade to a newer major OS version) Reinstall MacPorts as usual (say the one that goes with the new OS version) then: {{{ sudo port install `cat ~/installed_ports` }}} If you have done it the way you describe, to recover, you just need to do what the error message says and remove the offending file or force the activation of the new version. The old file will be moved aside with distictive tag that can be removed later. {{{ sudo port -f activivate gnome-keyring }}} I hope this clarifies the situation. -- Ticket URL: <https://trac.macports.org/ticket/39376#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X