[Python-bugs-list] [ python-Bugs-220993 ] Installation flaky with multiple installers, old versions

noreply@sourceforge.net noreply@sourceforge.net
Fri, 01 Feb 2002 02:26:37 -0800


Bugs item #220993, was opened at 2000-11-01 05:41
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=220993&group_id=5470

Category: Distutils
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Michael Hudson (mwh)
Summary: Installation flaky with multiple installers, old versions

Initial Comment:
Installation tends to have problems when there are old installations present, especially when a different user is doing the new installation.

In particular, it appears that the chmod() done in 'copy_file()' (as a result of the "install" command attempting to preserve the mode of files from the build tree) fails, because you can't chmod() a file owned by somebody else.

Paul Dubois suggests that simply unlinking the target file before doing the copy should work.  I think he's right, but need to think about it and test it a bit first.


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

>Comment By: Michael Hudson (mwh)
Date: 2002-02-01 02:26

Message:
Logged In: YES 
user_id=6656

Um, may be being dense, but os.unlink raises os.error if you
try to unlink a file that doesn't exist... so won't this
blow up in a first-time install for instance?

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

Comment By: A.M. Kuchling (akuchling)
Date: 2002-01-31 12:35

Message:
Logged In: YES 
user_id=11375

This bit David Binger today, so I finally dug in and fixed 
it.  Patch attached for a sanity-check.
(2.2 bugfix candidate)


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

Comment By: Michael Hudson (mwh)
Date: 2002-01-23 08:07

Message:
Logged In: YES 
user_id=6656

I'll have a look at this, as I've already assigned some
installation related bugs to myself.

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

Comment By: A.M. Kuchling (akuchling)
Date: 2001-09-20 11:41

Message:
Logged In: YES 
user_id=11375

I think unlinking first is the right thing to do, having 
just run into another problem that seems to be caused by 
this.  Installing *.so files to an NFS partition messed up 
other  people, I think because they had the *.so file 
loaded into memory and the kernel's VM got confused.  
(That's the theory, anyway.)

Bumping up the priority as a reminder to myself...



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

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