The ebuild for dev-python/django depends on pysqlite unconditionally. Python 2.5 includes sqlite functionality in the standard library and blocks pysqlite. If Python 2.5 is available, the package should not depend on pysqlite.
I believe this value for RDEPEND is correct. RDEPEND=">=dev-lang/python-2.3 sqlite? || ( >=dev-lang/python-2.5 >=dev-python/pysqlite-2.0.3 ) postgres? ( <dev-python/psycopg-1.99 ) mysql? ( dev-python/mysql-python ) dev-python/imaging"
The RDEPEND is just fine.
*** Bug 149961 has been marked as a duplicate of this bug. ***
How is it fine? My python-2.5 out-of-hard-mask system has conflicting blocking packages if the portage ebuild is used. dev-lang/python-2.5 blocks dev-python/pysqlite. dev-python/django (as is) requires dev-python/pysqlite. This is a blocker for 2.5 de-hard-mask-ing.
(In reply to comment #4) > How is it fine? My python-2.5 out-of-hard-mask system has conflicting blocking > packages if the portage ebuild is used. dev-lang/python-2.5 blocks > dev-python/pysqlite. dev-python/django (as is) requires dev-python/pysqlite. > This is a blocker for 2.5 de-hard-mask-ing. Learn to read the deps. sqlite? || ( >=dev-lang/python-2.5 >=dev-python/pysqlite-2.0.3 ) means _either_ >=dev-lang/python-2.5 _or_ >=dev-python/pysqlite-2.0.3. If you have >=dev-lang/python-2.5, it won't depend on >=dev-python/pysqlite-2.0.3.
Correct. That is the intention. If you have >=dev-lang/python-2.5, it won't depend on >=dev-python/pysqlite-2.0.3, because python-2.5 includes the functionality. The RDEPEND I posted is a proposed fix, not the current value of RDEPEND in portage. Sorry if that created any confusion.
> Sorry if that created any confusion. Eh, that was indeed confusing like hell... :P
hang on, are you sure about this? i am pretty sure the version of django in portage does not support python 2.5's sqlite3 module. in fact that was only added a week ago: http://code.djangoproject.com/changeset/3818 so the current dep is correct, it will only work with pysqlite2 even if python2.5 is installed. python2.5 presents pysqlite as sqlite3.
Ah, OK then. I hadn't tested release 0.95 against Python 2.5 (since it wouldn't install). Invalid is OK, as long as the next release does have correct dependencies.