On Dec 8, 2015, at 6:48 AM, Robert Chalmers wrote: > Decided to install amaves-new and watched as it happily installed everything > to do with p5.16xxx and considering I am running p5.22 already I watched as > it happily installed just about everything in the port tree as a dependency > of amaves-new but in p5.16 … not p5.22, > I already running spam assassin, and it’s running nicely - under p5.22 > > however on getting to this bit - the install of amazes-new barfed all > together. > > ---> Activating p5.16-mail-spf @2.9.0_0 > Error: org.macports.activate for port p5.16-mail-spf returned: Image error: > /opt/local/sbin/spfd is being used by the active p5.22-mail-spf port. Please > deactivate this port first, or use 'port -f activate p5.16-mail-spf' to force > the activation. > Error: Failed to install p5.16-mail-spf > Please see the log file for port p5.16-mail-spf for details: > > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-mail-spf/p5.16-mail-spf/main.log > Error: The following dependencies were not installed: p5.16-mail-spamassassin > p5.16-mail-spf p5.16-net-cidr-lite p5.16-net-patricia p5.16-time-hires > p5.16-net-server p5.16-unix-syslog > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port amavisd-new failed > > … sigh….:-(
Looks like the subports of the p5-mail-spf port conflict with one another on this one file. This is a bug. You should file a bug report in our issue tracker. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users