leif wrote: > John Cremona wrote: >> I have a similar problem, on a machine which has successfully built >> Sage in the past. Version 7.2 (literally commit f76401f). >> >> The last few commainds in history are >> >> make distclean >> ../configure >> make >> make >> >> but each of the last two make's ends with the following, also >> mentioning sage_setup.autogen.pari: >> >> >> make[3]: Entering directory `/home/lmfdb/sage/src' >> python -c "from sage_setup.autogen.pari import rebuild; rebuild()" >> sys:1: RuntimeWarning: not adding directory '' to sys.path since it's >> writable by an untrusted group. >> Untrusted users could put files in this directory which might then be >> imported by your Python code. As a general precaution from similar >> exploits, you should not execute Python code from this directory >> Traceback (most recent call last): >> File "<string>", line 1, in <module> >> ImportError: No module named sage_setup.autogen.pari >> make[3]: *** [sage/libs/pari/auto_gen.pxi] Error 1 >> make[3]: Leaving directory `/home/lmfdb/sage/src' > > Well, which group owns the folder, and does that group need write access? > > As a work-around, either change the group or chmod g-w ... > > > -leif
P.S.: W.r.t. what Volker(?) considers an "untrusted group", see build/pkgs/python2/patches/sys_path_security.patch -leif -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
