#39376: gnome-keyring @2.30.3_6 can not be installed ----------------------------+---------------------- Reporter: mk@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: gnome-keyring | ----------------------------+---------------------- Comment (by david@…): This is a bit odd, since the error is thrown about a system file (/usr/lib outside macports /opt) so what to do... This command outputs what I'd expect... David-Favor-iMac# port provides /usr/lib/pam/pam_gnome_keyring.so /usr/lib/pam/pam_gnome_keyring.so is not provided by a MacPorts port. Ah... that's right, PAM has to have files placed where it expects to ensure no exploit/malware is attempting a machine hijack... so... this is set... destroot.violate_mtree yes Searching for all occurrences of pam_gnome_keyring shows only one Portfile. David-Favor-iMac# ack -i -r -l pam_gnome_keyring /opt/local/var/macports /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/gnome /gnome-keyring/Portfile So the problem must be in the Portfile... Ah... now I get it. Here's the problem. 1) Install MacPorts + some port that requires gnome-keyring 2) Completely remove MacPorts via brute force rm -rf ... (per the MacPorts Guide) 3) Reinstall MacPorts + some port that requires gnome-keyring At this point the install done in #1 has left /usr/lib/pam/pam_gnome_keyring.so as residue (wasn't removed in #2) So a simple fix might be something like... {{{ pre-destroot { file delete -force ${destroot}/usr/lib/pam/pam_gnome_keyring.la } }}} This way a -force delete is done (which should do a rm -f and ignore errors) prior to install. Thus if the residue of a previous install exists, it's just quietly removed. I'll try this + if it works provide a patch file. Whew... this was driving me crazy... -- Ticket URL: <https://trac.macports.org/ticket/39376#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X