Ahh you just reminded me of a bug.  I'm not sure how to fix this using
the dynamic values..  But basically, "Depends" can't be in the _dbi_tags
if you are using sqlite.  If you notice in the fragment below, on db3
it's setup as a "temporary private" database used for single-run
optimization.  On the sqlite side, it becomes a "permanent" cache..  The
problem with that is that it only holds partial dependency data.. so you
suddenly start to get failures.

Could we make the _dbi_tags variable depending on the configuration?
And we need ot be sure that Depends never gets used on sqlite.

>   -# "Depends" is a per-transaction cache of known dependency resolutions.
>   -%_dbi_config_Depends		%{_dbi_btconfig} temporary private
>   +# database tags
>   +%_dbi_tags      Packages:Name:Basenames:Group:Requirename:Providename:Conflictname:Triggername:Dirnames:Requireversion:Provideversion:Installtid:Sigmd5:Sha1header:Filemd5s:Depends:Pubkeys:Packagecolor
>    
>   -# The default database configuration to use
>   -%_dbi_config    %{_dbi_btconfig}
>   +# database configuration: Berkeley-DB [dbapi 3 hooks]
>   +%_dbi_config_3_Depends          %{_dbi_btconfig} temporary private
>   +
>   +# database configuration: SQLite [dbapi 4 hooks]
>   +%_dbi_config_4_Depends          %{_dbi_sqlconfig}
>   +
>   +# database configuration [code entry hooks]
>   +%_dbi_config_Depends            %{expand:%%{_dbi_config_%{_dbapi_used}_Depends}}

--Mark