According to Kristian Klette, this error has been fixed in the non-test version of the 3.4.0 release (to be called 3.4.1) You can bypass this error by removing the following line in the "/usr/local/nav/lib/python/nav/models/manage.py" file:
community_suffix = models.CharField(max_length=-1)
This should fix that particular error, yes.
Although when I remove this line, I get another error saying "column vendor.enterpriseid does not exist".
This seems to be the same kind of error, only on a different model
Remove the line "enterprise_id = models.IntegerField(db_column='enterpriseid')" from /usr/local/nav/lib/python/nav/models/manage.py. Its on line 461 (or around there somewhere ;-) )
To recap whats causing these errors; The current django-models where created by introspecting (and some manual labour) our in-house development database, so it accidently got some experimental fields with it. Django applications using the select_related()-command on querysets fails because it cant find every field in the model in the actual database. So; if you encouter more of these errors, just delete the corresponing line from the manage.py file, and send us an email or report it on sourceforge (email is probably faster than that old behemoth though ;-)
And for people getting and error about a missing 500.html template, please enable django-debugging by making sure DEBUG is set to True in /usr/local/nav/lib/python/nav/django/settings.py
- Kristian Klette