"sudo python setup.py install" makes requires.txt unreadable except root #1403

New Issue

tahoe-lafs · 2011-05-12T05:42:44Z

socrates1024 commented

2011-05-12 05:42:44 +00:00

Right after python setup.py build and sudo python setup.py install, running $ tahoe gives this error:
https://gist.github.com/967983

I checked, and the file is in fact unreadable

-rw------- 1 root staff 208 2011-05-12 01:22 /usr/local/lib/python2.6/dist-packages/allmydata_tahoe-1.8.1-py2.6.egg-info/requires.txt

Running standalone, with bin/tahoe works just fine

Right after python setup.py build and sudo python setup.py install, running $ tahoe gives this error: <https://gist.github.com/967983> I checked, and the file is in fact unreadable -rw------- 1 root staff 208 2011-05-12 01:22 /usr/local/lib/python2.6/dist-packages/allmydata_tahoe-1.8.1-py2.6.egg-info/requires.txt Running standalone, with bin/tahoe works just fine

tahoe-lafs added the

labels 2011-05-12 05:42:44 +00:00

tahoe-lafs added this to the undecided milestone 2011-05-12 05:42:44 +00:00

davidsarah commented

2011-05-12 12:30:09 +00:00

Please do 'sudo echo foo >testfile; ls -l testfile', to get root's umask.

Please do '`sudo echo foo >testfile; ls -l testfile`', to get root's umask.

tahoe-lafs added

packaging

and removed

unknown

labels 2011-05-21 00:20:13 +00:00

warner commented

2016-03-26 21:37:02 +00:00

I think this was a problem with his root umask. Also, we no longer recommend installing as root to the system: our current virtualenv-based instructions won't require that.

Closing as INVALID. Please feel free to re-open if you disagree.

I think this was a problem with his root umask. Also, we no longer recommend installing as root to the system: our current virtualenv-based instructions won't require that. Closing as INVALID. Please feel free to re-open if you disagree.

warner added the

invalid

label 2016-03-26 21:37:02 +00:00

warner modified the milestone from undecided to 1.11.0

2016-03-26 21:37:02 +00:00

warner closed this issue

2016-03-26 21:37:02 +00:00

Sign in to join this conversation.