Trac 0.10 uses dev-python/pypgsql to access Postgres databases instead of dev-python/psycopg. The documentation on the Trac wiki seems to suggest that either will work, but in fact Apache logged a lot of errors when psycopg was the only package installed of the two.
Created attachment 98713 [details, diff] Obvious patch to trac-0.10.ebuild
Can you post or attach your Apache error log please?
Created attachment 98784 [details] Trimmed apache error log This is the Apache log, trimmed; it starts at Apache startup and continues through two Python backtraces, then Apache shuts down. The two backtraces are from two different reloads of the correct Trac URL. The first backtrace fails trying to import from pypgsql. After installing pypgsql, the second backtrace requested that I run trac-admin to update the old Trac repository; I did so, and everything worked after that.
Please, can you try with trac-0.10.1 or above ? I suspect the dev-python/psycopg dependency was wrong, and psycopg-2 should be used instead.
You're 100% right. psycopg-2 works as expected. I assume this was just a transitory ~x86 on the new psycopg when I reported the bug.
Then closing. I don't really see the benefit of offering the choice between psycopg-2 and pypgsql in the ebuild, via some kind of USE flag magic. I'll keep depending on psycopg-2.
