bad file on lion buildbot

[Joshua Root]

Hmm, that's unfortunate. Shree, could you clean up any stray ncurses
port contents please?

I don't think there's any easy way to maintain consistency between the
registry and the filesystem in the face of rebooting at just the wrong time.

- Josh

On 2015-1-19 08:41 , Jeremy Huddleston Sequoia wrote:
> Yeah, it looks like the slave died during activation of the port, leaving it in a bad state:
> 
> https://build.macports.org/builders/buildports-lion-x86_64/builds/26408
> 
> 
>> On Jan 18, 2015, at 09:45, Daniel J. Luke <dluke at geeklair.net> wrote:
>>
>> trac build failed on lion because -
>>
>> Error: org.macports.activate for port ncurses returned: Image error: /opt/local/bin/captoinfo already exists and does not belong to a registered port.  Unable to activate port ncurses. Use 'port -f activate ncurses' to force the activation.
>>
>>
>> on my local box /opt/local/bin/captoinfo is a symlink provided by ncurses.
>>
>>> Begin forwarded message:
>>>
>>> Date: January 18, 2015 at 12:40:04 PM EST
>>> Subject: buildbot failure in MacPorts on buildports-lion-x86_64
>>> From: noreply at macports.org
>>> To: dluke at geeklair.net, dluke at macports.org
>>>
>>> The Buildbot has detected a failed build on builder buildports-lion-x86_64 while building MacPorts.
>>> Full details are available at:
>>> http://build.macports.org/builders/buildports-lion-x86_64/builds/26412
>>>
>>> Buildbot URL: http://build.macports.org/
>>>
>>> Buildslave for this Build: apple-lion-x86_64-ports
>>>
>>> Build Reason: scheduler
>>> Build Source Stamp: [branch trunk] 131786
>>> Blamelist: dluke at macports.org
>>>
>>> BUILD FAILED: failed status
>>>
>>> sincerely,
>>> -The Buildbot
>>
>> --
>> Daniel J. Luke