Issues Upgrading Outdated Under 1.700
Rainer Müller
raimue at macports.org
Fri Dec 19 09:12:20 PST 2008
Tim Visher wrote:
> [...]
> Unfortunately, now I'm failing with the
> following message (and _no_ lock file):
>
> Waiting for lock on
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/.macports.boost.state
>
> I've done `find /opt -name '*.lock' -print` a bunch of times and
> nothing shows up, so I don't _think_ it's a lock file issue this time,
> but I've got no idea.
In fact, this is a lock file, it is locking a specific port. The port
tool is thinking there is another port instance running to build boost
currently. Look for running tclsh processes.
Rainer
More information about the macports-users
mailing list