Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Ticket #908 (closed defect: invalid)

Opened 11 years ago

Last modified 10 years ago

tg-admin fails if setuptools is too old and/or an old version of TG is installed

Reported by: Aaron Digulla Owned by: anonymous
Priority: normal Milestone:
Component: Installation Version: 0.9a5
Severity: major Keywords:
Cc: digulla@…

Description

I ran the setup as described on the download (not the upgrade page)

Everything seemed to be fine but my version of easy_install was too old to install all packages, so during the install process, RuleDispatch? wasn't installed but the script also didn't abort with an error.

Later, when I tried to run tg-admin as described on the Wiki 20 page, it failed:

Running /usr/bin/python setup.py egg_info
Error (exit code: 1)
Traceback (most recent call last):
  File "setup.py", line 2, in ?
    from turbogears.finddata import find_package_data
  File "/usr/lib/python2.4/site-packages/TurboGears-0.9a6-py2.4.egg/turbogears/__init__.py", line 6, in ?
    from turbogears.controllers import expose, flash, validate, redirect, \
  File "/usr/lib/python2.4/site-packages/TurboGears-0.9a6-py2.4.egg/turbogears/controllers.py", line 10, in ?
    from dispatch import generic, strategy, functions
ImportError: No module named dispatch

It took me a while to figure out that some packages were in fact missing.

My suggestion is a) to abort if a package can't be installed and b) print a better error message when an import fails ("Package ... is not installed/too old").

Change History

comment:1 Changed 11 years ago by jorge.vargas

you should be aware that setuptools its alpha software.

are you sure your not behind a setuptools breaking point instead if a TG problem?

comment:2 Changed 11 years ago by elvelind

  • Status changed from new to closed
  • Resolution set to invalid

it looks like most probably a setuptools issue. If somebody gets the problem again, please reopen

Note: See TracTickets for help on using tickets.