pinning = pin the right versions of the packages :) In buildout you can pin the versions by adding a section [versions].
You have an example into https://github.com/plumi/plumi.app/blob/master/buildout.cfg#L86 so, add those versions pinnings to your buildout and re- do bootstrap. You can do bootstrap as many times you want. If you are using buildout 1.x you should use http://downloads.buildout.org/1/bootstrap.py that should be the same version of the plumi buildout. By specifing --version=XXX you force the bootstrap to you use that version of zc.buildout. Note: before bootstrap it's better to remove zc.buildout egg from eggs/ folder, just to keep it clean if you downloaded other versions. HTH, S. On Fri, Mar 6, 2015 at 1:48 PM, Graabein <[email protected]> wrote: > Hello Simone > > Thanks for trying to help, very much appreciated. > > However, and unfortunately, I dont understand what you are talking about. > > What is "pinning"? > > and by re-do bootstrap, you mean I can just do the command over again but > this time force it to use a special version of bootstrap.py? > > So I just do: > python bootstrap.py --version=1.7.1 ? > > Do I have several versions of bootstrap.py in the same file, or do I need > to download a special version? If so, how do I do that, and from where? > > Graabein > > > > Den 06. mars 2015 13:22, skrev Simone Orsi: > > Hi, > > try pinning these: > > [versions] > zc.buildout = 1.7.1 > distribute = 0.6.35 > > and re-do bootstrap by forcing buildout version: > ../bin/python bootstrap.py --version=1.7.1 > > whereas ../bin/python is from your virtualenv (or your current python). > > HTH, > S. > > > > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.plumi.org/listinfo/discuss > >
_______________________________________________ Discuss mailing list [email protected] http://lists.plumi.org/listinfo/discuss
