I could probably do something like described in this thread:
http://lists.plumi.org/pipermail/discuss/2014-September/006252.html
2) create a directory (ex: /opt/plumi.app/tmp/python-eggs)
give that directory full rights chmod 777 /opt/plumi.app/tmp/python-eggs
But how to I tell python to use this directory in the PYTHON_EGG_CACHE
variable? Where do I edit/change this variable?
Graabein
Den 06. mars 2015 18:05, skrev Graabein:
Thank you Simone, this helped me a bit further.
As you suggested I modified the buildout.cfg and added
[versions]
zc.buildout = 1.7.1
distribute = 0.6.35
Now the compiler did some more work, but then new errors occured
I got huge numbers of "PYTHON EGG CACHE, access denied error" as
described here:
https://www.google.no/search?client=ubuntu&channel=fs&q=PYTHON_EGG_CACHE&ie=utf-8&oe=utf-8&gfe_rd=cr&ei=udn5VO6UNM-o8wfZxoAQ
Based on the myriad of different answers to how to solve it, I think
it is best to ask you in here what best to do regarding the Plumi setup.
I am confused, I must admit, as I dont understand if this python egg
cache need to be accessed ALWAYS, or just during the Plumi compiling,
or what? So I don't know what I should do to fix it. What do you
suggest?
BTW, I also got some other error messages, but maybe these are related
to this cache problem?
I am compiling Plumi as root user, is this a problem? Should I do all
of this as another ordinary sudo user?
Graabein
Den 06. mars 2015 16:22, skrev Simone Orsi:
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]
<mailto:[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] <mailto:[email protected]>
http://lists.plumi.org/listinfo/discuss
_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss
_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss
_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss
