[ python-Bugs-1076467 ] test_shutil fails on x86-64 // Suse 9.1

SourceForge.net noreply at sourceforge.net
Sat Dec 4 22:05:15 CET 2004


Bugs item #1076467, was opened at 2004-12-01 03:45
Message generated for change (Comment added) made by nijel
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1076467&group_id=5470

Category: Installation
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Ross G Baker Jr (rossgbaker2)
Assigned to: Nobody/Anonymous (nobody)
Summary: test_shutil fails on x86-64 // Suse 9.1

Initial Comment:
Here is the log of the single failing test: 
attached 
 
 

----------------------------------------------------------------------

Comment By: Michal Čihař (nijel)
Date: 2004-12-04 22:05

Message:
Logged In: YES 
user_id=192186

I meant, that as root you can do anything regardless actual
file permissions:

as root:

# mkdir test
# touch test/file
# chmod 400 test
# ll -d test
dr--------  2 root   root     4096 2004-12-04 22:00 test
# rm -rf test
#

as user:

$ mkdir test
$ touch test/file
$ chmod 400 test
$ ll -d test
dr--------  2 michal michal 4096 2004-12-04 22:05 test
$ rm -rf test
rm: cannot chdir from `.' to `test': Permission denied
$

----------------------------------------------------------------------

Comment By: Edward C. Jones (edcjones)
Date: 2004-12-04 18:47

Message:
Logged In: YES 
user_id=58796

I am having the same problem with Mandrake 10.1. I have an AMD chip with at least a i686 architecture. My Mandrake 10.1 is set at security level 3.

In the past (RedHat, Gentoo), I have installed programs from source as follows:
1. su to root.
2. Copy the tar ball (.tgz, .tar.gz, or .tar.bz2) into /usr/local/src.
3. Expand the tar ball.
4. cd to the top directory of the new source tree.
5. Follow the directions given there.

For Mandrake 10.1, this process failed when installing Python 2.4. The failure occured during "make test"  in test_shutil.py with the same error message as above in this thread. Nigel said above that "This failure happens only when testing as root, because then permissions don't have usual meaning". Have the meaning of the root permissions changed? What do the root permissions now mean? Is this documented somewhere?


----------------------------------------------------------------------

Comment By: Michal Čihař (nijel)
Date: 2004-12-02 12:57

Message:
Logged In: YES 
user_id=192186

This failure happens only when testing as root, because then
permissions don't have usual meaning, when testing as user,
it works fine.

----------------------------------------------------------------------

Comment By: Pierre (pierre42)
Date: 2004-12-01 22:35

Message:
Logged In: YES 
user_id=512388

Same here.


----------------------------------------------------------------------

Comment By: Michal Čihař (nijel)
Date: 2004-12-01 16:11

Message:
Logged In: YES 
user_id=192186

Same happends on i386

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1076467&group_id=5470


More information about the Python-bugs-list mailing list