The trac ebuild should be changed to reflect the fact that Python 2.5 includes pysqlite in it already. This can be done by simply changing the dependency from: >=dev-python/pysqlite-2.3 to || (>=dev-python/pysqlite-2.3 >=dev-lang/python-2.5) Thanks! Reproducible: Always
There's more to it than that, since >=dev-lang/python-2.5 now has a sqlite use flag. See https://bugs.gentoo.org/show_bug.cgi?id=179930 for a similar situation with net-im/gajim. It will also need a built_with_use check in pkg_setup.
Created attachment 120756 [details, diff] patch to trac-0.10.3.1 ebuild Suggested fix to check for sqlite in python 2.5 for trac 0.10.3.1
Created attachment 120758 [details, diff] patch to trac-0.10.4 ebuild Suggested fix to check for sqlite in python 2.5 for trac 0.10.4
These patches appear to have been ignored for 3 and a half weeks. Is there anything I can do to help this along further?
Any news?
Whatever the situation, the current 'stable' packages in portage have a bug related to this issue. As a user with no python experience, I had to go to #trac and ask around before my install worked. I was amazed that 'emerge trac' didn't solve dependencies. Why? I had to manually emerge dev-python/pysqlite before it would work. Anyway, this situation needs to change. (python 2.4.4-r4, sqlite 3.3.17 ... manually installed pysqlite 2.3.3)
@Walter: Did you emerge trac with the 'sqlite' use flag? If so, portage should've pulled in sqlite and pysqlite automatically. Can you reproduce the behaviour you described above? It appears that trac can use a mysql or a sqlite backend, so it shouldn't always pull in (py)sqlite. @Julien: Is there anything I can do to help this bug on its way?
Fixed for 0.10.* in CVS, sorry for the delay. Will remove 0.9.6 in a short time. Thanks
