maemo.org Bugzilla – Bug 4530
Re-enable support for SQLite3 in PyMaemo/build static libraries for sqlite3
Last modified: 2009-05-22 22:48:29 UTC
You need to log in before you can comment on or make changes to this bug.
I'm using version 2.5.2-15maemo2 of the "python2.5" package in the Fremantle SDK. This bug did not happen with previous versions. STEPS TO REPRODUCE THE PROBLEM: [sbox-FREMANTLE_X86: ~] > python2.5 Python 2.5.2 (r252:60911, May 9 2009, 05:04:04) [GCC 4.2.1] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import sqlite3 EXPECTED OUTCOME: (no error while importing the sqlite3 module - the sqlite3 module is usable as on a normal Python 2.5 installation with sqlite3 enabled) ACTUAL OUTCOME: Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.5/sqlite3/__init__.py", line 24, in <module> from dbapi2 import * File "/usr/lib/python2.5/sqlite3/dbapi2.py", line 27, in <module> from _sqlite3 import * ImportError: No module named _sqlite3 REPRODUCIBILITY: always OTHER COMMENTS: sqlite3 support in Python is required for some Python applications on Maemo, including gPodder. Bruno Araujo writes via e-mail: > The reason for the removal of sqlite3 support in the current version of > python2.5 is that the libsqlite3-dev package available in Fremantle beta > includes only the shared library files, lacking the static library ones > that are needed for proper sqlite3 support inside python. So, in order > to provide a functional python2.5 package in our latest release, we had > to disable sqlite3 support (or else python2.5 simply wouldn't compile). I have verified this: [sbox-FREMANTLE_X86: ~] > dpkg -L libsqlite3-dev /. /usr /usr/include /usr/include/sqlite3.h /usr/include/sqlite3ext.h /usr/lib /usr/lib/pkgconfig /usr/lib/pkgconfig/sqlite3.pc /usr/share /usr/share/doc /usr/share/doc/libsqlite3-dev /usr/share/doc/libsqlite3-dev/copyright /usr/share/doc/libsqlite3-dev/README /usr/share/doc/libsqlite3-dev/changelog.Debian.gz /usr/lib/libsqlite3.so Only the shared library is installed there. The relevant Debian ChangeLog entry is this: sqlite3 (3.6.10-0maemo0) stable; urgency=low * Upgraded to upstream 3.6.10 * Using tarball instead of uncompressed sources * Removed static libraries * F i x e s : N B # 93828 sqlite3 command line tool doesn't work in scratchbox -- Ivan Frade (frade) <ivan.frade@nokia.com> Thu, 21 Jan 2009 14:56:03 +0300 ("Removed static libraries" is the relevant part here)
This bug does not happen in python2.5 version 2.5.2-11.1maemo3+0m5.
According to Ivan Frade, the new sqlite3 package will include the static libraries in the -dev package: > I plan to integrate a new version of sqlite3 soon (this week), and it > will include the static libraries in the -dev package. After that, I think python2.5 can be re-built with SQLite3 support, or is there still something left to do?
Nothing else left, we are just waiting for the updated sqlite package, after which we will revert the patch and upload a new python2.5 package.
sqlite3 version 3.6.14-1maemo1+0m5 uploaded to Fremantle beta repository.
That version should include the static libraries.
Ok, the update is now out. After a rebuild of Python with SQLite support, and upload to the repos, this ticket can be closed :)
I've fixed python2.5 and sent it to the autobuilder, hopefully it'll be on extras-devel soon :-) The version uploaded was 2.5.2-15maemo3.