On Mon, Dec 20, 2004 at 07:41:39AM -0600, Marcelo E. Magallon wrote: > On Mon, Dec 20, 2004 at 11:54:46PM +1300, Nick Phillips wrote: > > > Seems that DBD::SQLite has now migrated to sqlite3, but that > > libdbd-sqlite-perl has stayed at sqlite2 by actually packaging > > DBD::SQLite2 rather than DBD::SQLite. > > Uhm... from README.Debian: > > Package name changes from DBD::SQLite to DBD::SQLite2. > > meaning the Perl package name, not the Debian package name. > > Upstream package DBD::SQLite >= 1.00 uses sqlite3. For compatibility > reasons Debian use DBD-SQLite2 as foundation. Please, change in your > programs connect param from "dbi:SQLite" to "dbi:SQLite2". > > Sounds broken to me. Yes, I didn't like the fact that it suddenly broke various bits of code. I have lots of perl modules packaged which have 'use DBD::SQLite' in their test suites. This means that they all now break and need hand hacking to fix. This has effectively introduced RC bugs into some of my packages. > The changelog for 1.x doesn't actually mention something breaking, so > my guess is that the new DBD::SQLite is backwards compatible and that > there's a libdbd-sqlite3-perl stuck in incoming's queue. Checking the incoming list at http://developer.skolelinux.no/~pere/debian-NEW.html I can see no sign of libdbd-sqlite3-perl, it seems to me this is something that needs to be resolved quickly. The current situation is a bit of a mess. Thankfully it hasn't reached sarge yet due to dependencies on the perl package. Stephen
Attachment:
signature.asc
Description: Digital signature