Bad files on buildports-lion-x86_64

[David Evans]

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 apple.com <mailto:groen at apple.com>
> ☎ 415.971.3222

An alternative would be to just delete any of the following files if 
they exist:

   /opt/local/lib/perl5/vendor_perl/5.20/Spiffy.pm
   /opt/local/lib/perl5/vendor_perl/5.20/Spiffy.pod
   /opt/local/lib/perl5/vendor_perl/5.20/Spiffy/mixin.pm
/opt/local/lib/perl5/vendor_perl/5.20/darwin-thread-multi-2level/auto/Spiffy/.packlist
   /opt/local/share/perl5.20/man/man3/Spiffy.3pm

>
>> On May 1, 2015, at 8:46 PM, David Evans <devans at macports.org 
>> <mailto:devans at macports.org>> 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/Spiffy.pm 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: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20150502/661b5a8d/attachment.html>