What seems to be happening is that you don't have any of the supported PostgreSQL drivers available in Python anymore. The reason why trac- admin talks about the other driver is because it's the last one it tries before failing.
Try this from a Python console: >>> import psycopg2 as psycopg If this fails, psycopg2 is somehow missing. Fix this first and then see what Trac does. HTH, Sergey. On Jun 23, 8:23 am, Michal Paluchowski <[EMAIL PROTECTED]> wrote: > Hi, > > a similar problem's been touched here before but no solutions seem to > have emerged. I'm running Trac on a FreeBSD system with PostgreSQL and > psycopg2 - that's the standard out-of-the-ports setup, which worked > fine. > > Now I'm doing port upgrades once in a while and one of these must have > broken something. Now running Trac from my server through Apache works > just fine: > > http://trac.nethut.pl/hubbub/ > > but the trac-admin script stopped working. What I get is: > > /usr/local/trac # trac-admin hubbub/ permission list > Command failed: No module named pyPgSQL > > Now obviously I don't have pyPgSQL and never did. The web interface of > Trac does just fine without it, so why does trac-admin now so > desperately want to have it? Obviously I can't do any administrational > tasks this way. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
