Package: sqlite3
Version: 3.3.17-1
Severity: critical
Justification: causes serious data loss
see
http://www.sqlite.org/cvstrac/wiki?p=DatabaseCorruption
http://www.hwaci.com/sw/sqlite/
* There is a VACUUM bug that could lead to obsolete caches
on a second connection. Introduced in 3.3.14 (says
http://www.hwaci.com/sw/sqlite/), fixed in 3.4.1.
* SQLITE_BUSY error in a transaction without rollback can corrupt
the database file! Introduced in 3.3.0, fixed in 3.4.0. Update
strongly recommended (says http://www.hwaci.com/sw/sqlite/).
* Auto-vacuum or incremental-vacuum + large UPDATE + CREATE TABLE
or CREATE INDEX + UPDATE with malloc-failure causing a rollback
=> database corruption. Introduced in 3.1.0, fixed in 3.4.0,
not seen in the wild.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages sqlite3 depends on:
ii libc6 2.6-5 GNU C Library: Shared libraries
ii libreadline5 5.2-3 GNU readline and history libraries
ii libsqlite3-0 3.3.17-1 SQLite 3 shared library
sqlite3 recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
