Buildbot failures after migrating from Distribute to Setuptools

Peter Danecek Peter.Danecek at bo.ingv.it
Thu Jun 13 10:36:27 PDT 2013


Hi developers, 

I just realised, that I have these deactivated py2x-distribute @0.6.45_0 port laying a around and I guess this basically the issue of this thread.

What I am wondering now: If the dependency can be deactivated, why it is a dependency in the registry in the first place?
Is py-distribure non JUST a build dependency? Or why now I would be save to make a forced uninstall?
I am just asking to understand!

Thanks for clarification!
~petr


--- snip ---

radegast:~ petr$ sudo port uninstall  py27-distribute @0.6.45_0
--->  Unable to uninstall py27-distribute @0.6.45_0, the following ports depend on it:
--->  	py27-nose @1.2.1_1
--->  	py27-ipython @0.13.2_0+notebook+parallel+scientific
--->  	py27-dateutil @1.5_1
--->  	py27-altgraph @0.10.2_0
--->  	py27-pyobjc @2.5.1_0
--->  	py27-dap @2.2.6.7_0
--->  	py27-pep8 @1.4.5_0
--->  	py27-rope @0.9.2_0
--->  	py27-roman @2.0.0_0
--->  	py27-jinja2 @2.7_0
--->  	py27-pygments @1.6_0
--->  	py27-numexpr @2.1_0
--->  	py27-bottleneck @0.6.0_0
--->  	py27-pandas @0.11.0_0
--->  	py27-pyro @4.17_0
--->  	py27-virtualenvwrapper @4.0_0
--->  	py27-pyproj @1.9.3_2
--->  	py27-virtualenv @1.9.1_0
Error: org.macports.uninstall for port py27-distribute returned: Please uninstall the ports that depend on py27-distribute first.
Please see the log file for port py27-distribute for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_py27-distribute_0.6.45_0/py27-distribute/main.log
Warning: Failed to execute portfile from registry for py27-distribute @0.6.45_0
--->  Unable to uninstall py27-distribute @0.6.45_0, the following ports depend on it:
--->  	py27-nose @1.2.1_1
--->  	py27-ipython @0.13.2_0+notebook+parallel+scientific
--->  	py27-dateutil @1.5_1
--->  	py27-altgraph @0.10.2_0
--->  	py27-pyobjc @2.5.1_0
--->  	py27-dap @2.2.6.7_0
--->  	py27-pep8 @1.4.5_0
--->  	py27-rope @0.9.2_0
--->  	py27-roman @2.0.0_0
--->  	py27-jinja2 @2.7_0
--->  	py27-pygments @1.6_0
--->  	py27-numexpr @2.1_0
--->  	py27-bottleneck @0.6.0_0
--->  	py27-pandas @0.11.0_0
--->  	py27-pyro @4.17_0
--->  	py27-virtualenvwrapper @4.0_0
--->  	py27-pyproj @1.9.3_2
--->  	py27-virtualenv @1.9.1_0
Error: port uninstall failed: Please uninstall the ports that depend on py27-distribute first.
radegast:~ petr$ 

--- snip ---

radegast:~ petr$ sudo port activate  py27-distribute @0.6.45_0
--->  Computing dependencies for py27-distribute
--->  Activating py27-distribute @0.6.45_0
Error: org.macports.activate for port py27-distribute returned: Image error: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/easy_install is being used by the active py27-setuptools port.  Please deactivate this port first, or use 'port -f activate py27-distribute' to force the activation.
Please see the log file for port py27-distribute for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_py27-distribute_0.6.45_0/py27-distribute/main.log
Warning: Failed to execute portfile from registry for py27-distribute @0.6.45_0
--->  Activating py27-distribute @0.6.45_0
Error: port activate failed: Image error: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/easy_install is being used by the active py27-setuptools port.  Please deactivate this port first, or use 'port -f activate py27-distribute' to force the activation.
radegast:~ petr$ 

--- snap ---



On Jun 12, 2013, at 11:55 , Joshua Root <jmr at macports.org> wrote:

> On 2013-6-12 09:30 , Blair Zajac wrote:
>> How about, if there's no update to a port in the commit you made, we
>> bump the rev?
> 
> If we do that, let's review them to make sure the dependency type is
> correct at the same time. I suspect some of them don't actually need
> setuptools at runtime.
> 
> - Josh
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev



More information about the macports-dev mailing list