yum/python/sqlite b0rkage in Rawhide

[seth vidal]

> Well, it started as sqlite3, with good reason. Look:
> 
> -rwxr-xr-x root  root     29844 /usr/bin/sqlite3
> lrwxrwxrwx root  root        19 /usr/lib/libsqlite3.so.0
> -rwxr-xr-x root  root    316204 /usr/lib/libsqlite3.so.0.8.6
> -rw-r--r-- root  root     52690 /usr/include/sqlite3.h
> -rw-r--r-- root  root    403624 /usr/lib/libsqlite3.a
> -rwxr-xr-x root  root       819 /usr/lib/libsqlite3.la
> lrwxrwxrwx root  root        19 /usr/lib/libsqlite3.so
> -rw-r--r-- root  root       231 /usr/lib/pkgconfig/sqlite3.pc
> 
> Sure, the v2 sqlite package could be rename to sqlite0 or sqlite2 if it
> will still be needed. But that's not the point.

I asked for it to be changed from sqlite3 to sqlite b/c it made little
sense to me that the package should be named sqlite3 when we weren't
providing sqlite(any number) in the rest of the distro.

add to that the the upstream package name is sqlite, not sqlite3 and I
didn't see a compelling reason to have an odd ball virtual provide  (and
dep) for the package.

-sv