The package does depend on dev-python/pysqlite:2 but not on Python implementation USE=sqlite. The pysqlite package is no longer maintained and compatible with Python 2 only; while the builtin 'sqlite3' module is basically a maintained clone/fork of pysqlite. If the package actually imports pysqlite2 unconditionally, please check whether it wouldn't work with the builtin 'sqlite3' module as well. If it does, upstream should probably fix the package to import 'sqlite3' *at least* when 'pysqlite2' is not available. If it doesn't, please let us know and we will know that pysqlite needs to be kept in the tree. If the package simply supports 'sqlite3', please let us know or update the deps. However, the latter is unnecessary since the 'old' Python eclass doesn't provide a proper way to do this, and we may decide to drop pysqlite entirely after getting feedback for the packages depending on it.
In this one, we're applying a patch to support pysqlite fallback from built-in sqlite3.
(In reply to comment #1) > In this one, we're applying a patch to support pysqlite fallback from > built-in sqlite3. What do you mean by "we're applying..."? Is there a patch already or will there be one?
(In reply to comment #2) > (In reply to comment #1) > > In this one, we're applying a patch to support pysqlite fallback from > > built-in sqlite3. > > What do you mean by "we're applying..."? Is there a patch already or will > there be one? Yes, there's a patch in files/. If we decide to drop pysqlite2 completely, it would be enough to drop it.
I have future-fixed the deps. There is still the case of dropping the patch but I think that can be post-poned until pysqlite is removed completely.
pysqlite has now been removed completely.
+ 15 Oct 2013; Justin Lecher <jlec@gentoo.org> bibus-1.5.1.ebuild, + bibus-1.5.2.ebuild, -files/bibus-1.5.0-pysqlite.patch: + Drop obsolete patch, #452128 +