upgrade broken on Gentoo due to sandbox violations

[GoogleCodeExporter]

We build packages inside a sandboxed environment that traps any attempt to
modify the filesystem outside the build directory.  Recent upgrades of
editra have been failing due to attempts to unlink files in
/usr/lib/python2.6/site-packages/Editra/ (the installation directory).  

It looks like the culprit is 
http://svn.wxwidgets.org/viewvc/wx?view=revision&revision=62827

I'm not really sure how to go about fixing this.  I tried making it
conditional on write permission but because checking perms doesn't modify
the file, the sandbox doesn't kick in and it appears to be writable.

https://bugs.gentoo.org/298752

Original issue reported on code.google.com by dirtyepic.sk on 18 Feb 2010 at 5:14

[GoogleCodeExporter]

Open for ideas on what todo about this one. I had to add that change a while 
back
because there was starting to be issues with old files from previous installs 
that
were conflicting with new installs.

For example awhile back there was a file called 'xml.py' this was renamed to
'_xml.py' to avoid a naming conflict with the module in pythons standard lib. 
The
problem was that new installs where not removing 'xml.py' so it caused 
conflicts and
runtime failures when any code tried to access the xml module in pythons stdlib.

I suppose I could make the check more specific to check for if these renamed 
files
exist or perhaps add a command line arg to disable the delete part. Thinking the
latter may be better.

Any opinion?

Cody

Original comment by CodyPrec...@gmail.com on 18 Feb 2010 at 2:07

• Changed state: Started
• Added labels: Component-Scripts

[GoogleCodeExporter]

an option to disable deletion should work.  in our case the package manager will
ensure that any old files are removed.

Original comment by dirtyepic.sk on 18 Feb 2010 at 7:21

[GoogleCodeExporter]

Added '--no-clean' option to the setup command

python setup.py install --no-clean

can now be used to do the install and skip the cleanup of old files.

A work around for current releases is to make sure that any existing 
installation is
removed prior to running the the setup script as the remove step will be 
skipped if
the files are not found.

Original comment by CodyPrec...@gmail.com on 18 Feb 2010 at 7:36

• Changed state: Fixed

[GoogleCodeExporter]

thanks!

Original comment by dirtyepic.sk on 19 Feb 2010 at 12:02