On Mon, 14 Mar 2005 10:41:46 -0500, Jeff Spaleta <jspaleta@xxxxxxxxx> wrote: > Naively this makes me think that > something significant changed inside the sqlite package when it was > renamed to sqlite from sqlite3. A little more evidence to indicate something inside libsqlite3.so.0.8.6 is different between sqlite and sqlite3 packages. I replace just the libsqlite3.so.0.8.6 file from sqlite package with the version from sqlite3 package and yum works again. The is something different about the libsqlite3.so.0.8.6 file between package versions. Here's my procedure: Force the installation of sqlite3-3.0.8-3.i386.rpm using yum-2.3.1-2 python-sqlite-1.1.6-1 rpm-4.4.1-7 make sure rpm -V sqlite3 returns clean make sure yum will operate yum check-update is enough to check cp /usr/lib/libsqlite3.so.0.8.6 somewhere safe update to sqlite-3.1.2-1 make sure rpm -V sqlite returns clean yum check-update will blow up mv saved copy of libsqlite3.so.0.8.6 back to /usr/lib/ rpm -V sqlite returns S.5....T. /usr/lib/libsqlite3.so.0.8.6 yum check-update works again. Was there ever a published sqlite3 package for version 3.1.2? The problem could be associated with internal sqlite library change between 3.1.2 and 3.0.8. -jef
