Problem with port upgrade

Philip Neukom neukomp at profitanalytics.com
Thu Sep 16 11:30:45 PDT 2010


On 16.09.2010 14:08, Ryan Schmidt wrote:
> On Sep 16, 2010, at 12:52, Philip Neukom wrote:
> 
>> I ran "sudo port -v upgrade outdated" today before I was going to
>> install a new package.
>>
>> It gave out with the following error:
>>
>> "Waiting for lock on
>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_orc/work/.macports.orc.state
> 
> This means you were trying to run two "port" commands affecting the orc port simultaneously, from different terminal windows. This can cause things to break (though I'm not sure if this was the problem here today).
> 
> In the next version of MacPorts, this message will be changed to read:
> 
> Waiting for lock on /opt/local/var/macports/registry/.registry.lock
> 
> And MacPorts will ensure it does not work on multiple tasks simultaneously.
> 
> 
>> Error: Unable to upgrade port: can't create directory
>> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_readline":
>> file already exists
> 
> First, try cleaning the affected port and running the command again. So:
> 
> sudo port clean readline
> sudo port upgrade readline
> 
> Does that work?
> 
> If not and you get the same message, then does that directory exist? If so, try removing it, then trying again as above.

Thanks Ryan.

I tried "sudo port clean readline" and then re-ran "sudo port -v upgrade
outdated".  It looks to be proceeding as expected.

I'm going to have to look why I even have readline installed.  It must
be a requirement for something else that I have installed.(?)

Again, thanks for the quick reply.


More information about the macports-users mailing list