700: setup.py install' is broken at django-evolution; configure.ac is also broken

akimb*****@gmai***** (Google Code) (Is this you? Claim this profile.)
Nov. 25, 2008 
I tried to install Reviewboard by running 'sudo python setup.py install'

This fails when it gets to django-evolution: 

[ lots of copying... lines elided ]
Installed /usr/lib/python2.5/site-packages/ReviewBoard-0.9.dev-py2.5.egg
Processing dependencies for ReviewBoard==0.9.dev
Searching for django-evolution
Reading http://www.review-board.org/downloads/mirror/
Reading http://www.review-board.org/downloads/nightlies/
Reading http://www.review-board.org/downloads/bleeding/
Best match: django-evolution 0.0.0
Downloading
http://www.review-board.org/downloads/mirror/django_evolution-0.0.0.tar.gz
Processing django_evolution-0.0.0.tar.gz
Running django_evolution-0.0.0/setup.py -q bdist_egg --dist-dir
/tmp/easy_install-nKmMrt/django_evolution-0.0.0/egg-dist-tmp-blRvBZ
zip_safe flag not set; analyzing archive contents...
django_evolution.evolve: module references __file__
No eggs found in
/tmp/easy_install-nKmMrt/django_evolution-0.0.0/egg-dist-tmp-blRvBZ (setup
script problem?)
error: Could not find required distribution django-evolution

(it looks like a broken package on your site?) 

I installed Django 1.0, python-module-MysqlDB, and memcached, and then ran
the reviewboard installation script. I'm trying to get this to work in
Apache on Fedora Core 8 (x86_64). Python is 2.5.1.  

Before attempting setup.py, Apache complains in ssl_error_log:
[Tue Oct 21 06:00:22 2008] [error] [client 216.231.36.48] ImportError:
Could not import settings 'reviewboard.settings' (Is it on sys.path? Does
it have syntax errors?): No module named reviewboard.settings

After the aborted attempt, it now claims: 
[Tue Oct 21 03:01:33 2008] [error] [client 216.231.36.48]
ImproperlyConfigured: Error importing middleware
reviewboard.admin.middleware: "No module named django_evolution"

I also tried running 'autoconf configure.ac' to try to install this way.
When generating the configure script, it complains:

configure.ac:8: error: possibly undefined macro: AM_INIT_AUTOMAKE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:10: error: possibly undefined macro: AM_MAINTAINER_MODE
configure.ac:12: error: possibly undefined macro: AM_PATH_PYTHON
configure.ac:13: error: possibly undefined macro: AM_PATH_DJANGO

Running the configure script anyway gives:
./configure: line 1629: syntax error near unexpected token `1.9'
./configure: line 1629: `AM_INIT_AUTOMAKE(1.9 dist-bzip2)'

This is with autoconf-2.61-9.fc8.noarch and automake 1.10
#1 akimb*****@gmai***** (Google Code) (Is this you? Claim this profile.) 
Updated... I got this working by manually installing django_evolution from their svn,
and removing all dependencies from install_requires and all addresses from
dependency_links in the call to setup()
chipx86
#2 chipx86 
Should be fixed now. We've officially deployed the new setup install, and removed the
old autoconf/automake system.
  • +Fixed
  • -Priority-Medium
    +Priority-Critical
    +Milestone-Release1.0
    +Component-Deployment