Hello Jim, What about writing out the upgraded buildout script as a temp script, like "/tmp/buildout-<random>.py" and restarting with that?
Upgrading with easy_install is a catch 22, one app needs zc.buildout-1.1.1 the other zc.buildout-1.4.3 nailed via versions. Friday, March 26, 2010, 1:35:15 PM, you wrote: JF> On Wed, Mar 24, 2010 at 6:38 AM, Adam GROSZER <agros...@gmail.com> wrote: >> Hello, >> >> Having problems here with the above. >> >> The thing is that there should be two projects installed on the same >> server, but the one is a zope KGS 3.4 the other is a >> ztk/bluebream-ish. >> The two have different version requirements for setuptools and >> zc.buildout. >> The buildout.cfg comes from the web like this: >> buildout -t 2 -c http://mypypi.org/++projects++/proj/proj-stage-0.0.4.cfg >> (On top of that this is driven by keas.build, but that should not >> matter) >> Buildout (1.4.1) is installed via easy_install and setuptools (0.6c9). >> Therefore the message "Not upgrading because not running a local >> buildout command". The message is reasonable, but still makes problems >> in the way of making the one of the projects non-installable. >> >> Would not it be easy to create a bin/buildout script and restart with >> that? JF> The auto-upgrade feature of buildout only works if the buildout script JF> being run is in the buildout's bin directory. This is a safety feature JF> to avoid unintentional upgrades of other buildouts. JF> If you installed buildout with easy_install and want to upgrade it, I JF> suggest upgrading it with easy_install. JF> Jim -- Best regards, Adam GROSZER mailto:agros...@gmail.com -- Quote of the day: Not only is there no God, but try getting a plumber on the weekend. - Woody Allan _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
