Roundup Tracker - Issues

Issue 1082801

classification
setup.py install of 0.8b1 fails
Type: Severity: normal
Components: Installation Versions:
process
Status: closed fixed
:
: richard : alain_tesio, radeex, richard
Priority: normal :

Created on 2004-12-10 10:21 by anonymous, last changed 2005-01-03 03:12 by richard.

Messages
msg1561 Author: [hidden] (anonymous) Date: 2004-12-10 10:21
Two different errors:

*** SOURCE ERROR: The MANIFEST file is missing!

and:

running build_py
error: build_py: supplying both 'packages' and
'py_modules' options is not allowed

Trying to --skip-build the installation to avoid this
problem didn't work either::

running install_lib
warning: install_lib: 'build/lib' does not exist -- no
Python modules to install
running install_scripts
error: cannot copy tree 'build/scripts-2.2': not a
directory


-- radix
msg1562 Author: [hidden] (alain_tesio) Date: 2004-12-12 22:02
Logged In: YES 
user_id=13893

This command rebuilds the file MANIFEST:

python setup.py sdist --manifest-only

But then build complains about missing files:

python setup.py build
running build

*** SOURCE ERROR: There are files missing (245/250 found)!
Missing: roundup-admin
Missing: roundup-demo
Missing: roundup-gettext
Missing: roundup-mailgw
Missing: roundup-server

I don't know why sdist put these lines, remove the 5 lines
starting with roundup- in the file MANIFEST and build works
msg1563 Author: [hidden] (richard) Date: 2004-12-12 22:16
Logged In: YES 
user_id=6405

The manifest messages are not fatal, so may be ignored. I don't 
know why the MANIFEST isn't being included - the MANIFEST.in 
file specifically has "include run_tests.py *.txt demo.py 
MANIFEST.in MANIFEST". The MANIFEST file contains a line 
"MANIFEST". I just re-bundled the code, and the MANIFEST file is 
in there - it's just not in the version on sf.net's download area. 
 
When building, I specifically perform separate steps: 
 
 python setup.py clean --all 
 python setup.py sdist --manifest-only 
 python setup.py sdist --quiet 
 
... so I really don't know WTF is going on :( 
 
BTW, the setup.py "build" command is not necessary. 
 
Having said all that, I've just tested both "build" and "install" 
using Python 2.3.4 and the tarball from the files section on 
https://sourceforge.net/project/showfiles.php?group_id=31577 
and it works fine for me. 
 
I guess I'll just be more alert next time I bundle a release, and 
check for the MANIFEST file in the release... 
 
msg1564 Author: [hidden] (radeex) Date: 2004-12-13 02:35
Logged In: YES 
user_id=493158

Richard,

The latter error about py_modules and packages only occurs
in python 2.2. Unfortunately, I can only use python 2.2 for
the Twisted roundup instance (well, unless I want to do a
bunch of extra work).

Is roundup still supporting Python 2.2?
msg1565 Author: [hidden] (richard) Date: 2004-12-13 03:02
Logged In: YES 
user_id=6405

Ah crap. Looks like we're hitting a distutils issue that was fixed in 
2.3. 
 
To fix the problem, change: 
 
--- setup.py.old        2004-12-13 14:02:12.030974713 +1100 
+++ setup.py    2004-12-13 14:02:18.032655025 +1100 
@@ -274,7 +274,7 @@ 
     installdatafiles = [ 
         ('share/roundup/cgi-bin', ['cgi-bin/roundup.cgi']), 
     ] 
-    py_modules = ['roundup.demo',] 
+    py_modules = [] 
 
     # install man pages on POSIX platforms 
     if os.name == 'posix': 
 
 
I'm not sure what a better solution is to make us work with 
<py2.3 ... 
 
msg1566 Author: [hidden] (richard) Date: 2005-01-03 03:12
Logged In: YES 
user_id=6405

I will mod the setup.py to remove that arg for <Python2.3. It just 
won't install the demo code (which is OK, since that's only 
needed for Windows binary installer users). 
 
History
Date User Action Args
2004-12-10 10:21:54anonymouscreate