New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong access rights of pcmdi_metrics-v1.1.1-py2.7.egg-info in 2.8.0! #496
Comments
@jypeter thanks for this feedback, when the conda packages are being built we might have to add in a perm wash to ensure that similar issues don't occur in the future.. It's the first time that we've received such a specific use case issue, some other folks using the PMP are doing so in a shared install env |
Can you check what access rights you have for this file (and the others), ideally in a 2.8.0 version? Also, the date of the pcmdi_metrics-v1.1.1-py2.7.egg-info file is 21 juil. 2016, which seems kind of old to me, but I don't know what it should be. Could it be that I got a wrong and outdated version? |
@jypeter when I install for users here I always do some sort of rechmod to make sure users can read files. I don't think it's due to pmp. |
Not due to PMP? Why is it that I have this access rights problem only with PMP (see my find command above), on 2 separate servers? I have installed PMP the same way I have installed other packages. Look for "PMP" in my 2.8.0 installation notes Can one of you guys check the access rights of the mentionned PMP file(s) in one of your installation (where you have not done a chmod -R a+rX cdat) |
@doutriaux1 @durack1 Nightlies are done on Travis. I didn't build the conda packages for v1.1.1, but I usually use aims4, however I never worked on a shared env. |
@doutriaux1 @zshaheen The problem seems to have been solved in My initial problem was with How did you solve this in the end? |
This issue was solved in 1.1.2 so closing |
@doutriaux1 and @durack1 with my usual luck, I have found an unusual problem...
I have installed PMP in 2.8.0, just in case, with
conda install -n cdatm14 -c conda-forge -c pcmdi pcmdi_metrics
I have not used PMP, so I assume it is OK, but it has the following weird side effect: if another person uses my shared CDAT installation, AND wants to use ipython, then there is a huge traceback due to the fact that pcmdi_metrics-v1.1.1-py2.7.egg-info can be read only by the owner (the person who installed cdat, i.e me)
I have checked the content of envs/cdatm14/lib/python2.7/site-packages/ on 2 different servers where I have installed 2.8.0 and pcmdi_metrics-v1.1.1-py2.7.egg-info is the only file that is not readable by group+other.
I guess that ipython scans the content of site-packages when it starts (maybe that's one of the reasons it is so much slower to start than the regular python interpreter, and why I don't use ipython) and breaks when it can't access one of the files. This almost sounds like an ipython bug to me, but I won't take care of reporting it
Just to be sure, I have checked if some other files were having the same problem in 2.8.0, but it seems only files in PMP have this problem (you may want to check if I used the correct value for -perm below
The text was updated successfully, but these errors were encountered: