Bad files on buildports-lion-x86_64

David Evans devans at
Fri May 1 21:45:14 PDT 2015

On 5/1/15 9:03 PM, Henry Groen wrote:
> I just tried that and it gives me a  port: command not found, is there 
> something else I need to do first?
> henry
> *Henry Groen*
> *Core OS*
> ☎ 408.862.5234 | ✉ groen at <mailto:groen at>
> ☎ 415.971.3222
probably need to specify the full path to port, it may not be in the 
superuser's path.
does "which port" give you something useful?  On my machine it is 

>> On May 1, 2015, at 8:46 PM, David Evans <devans at 
>> <mailto:devans at>> wrote:
>> Dear admins,
>> Currently a number of perl ports are failing to build on 
>> buildports-lion-x86_64 due to the following activation error 
>> regarding port p5.20-spiffy.
>>> Error: org.macports.activate for port p5.20-spiffy returned: Image 
>>> error: /opt/local/lib/perl5/vendor_perl/5.20/ already 
>>> exists and does not belong to a registered port.  Unable to activate 
>>> port p5.20-spiffy. Use 'port -f activate p5.20-spiffy' to force the 
>>> activation.
>> As the error message says the offending files can be removed using 
>> the following commands (preferably during a period when the buildbot 
>> is idle):
>> sudo port -f activate p5.20-spiffy
>> sudo port deactivate p5.20-spiffy
>> The offending files will be moved aside with a unique suffix and can 
>> be deleted after the successful completion of these commands.
>> Thanks in advance for your help

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the macports-dev mailing list