Re: Upgrading from 3.0.6 to 4.0.4

[Albert Chin <rpm-list thewrittenword com>]

On Wed, May 15, 2002 at 03:33:56PM -0400, Jeff Johnson wrote:
> On Wed, May 15, 2002 at 02:14:16PM -0500, Albert Chin wrote:
> > 
> > Is --rebuilddb suppose to create Triggername? Odd that it creates the
> > other files fine.
> > 
> 
> What does
> 	rpm --eval '%{_dbi_tags}'
> say? If Triggername is present in %_dbi_tags but not in /var/tmp/db, then
> you have yet to install a package with a trigger scriptlet.

$ rpm --eval '%{_dbi_tags}'
Packages:Name:Basenames:Group:Requirename:Providename:Conflictname:Triggername:Dirnames:Requireversion:Provideversion:Installtid:Sigmd5:Sha1header:Filemd5s:Depends

If the two packages I installed with 3.0.6 before the upgrade didn't
have a trigger, why does removing one of them after the upgrade to
4.0.4 require Triggername? As far as I know, we don't use triggers in
any RPM spec we build (just checked with -qp --triggers and nothing
was listed).

BTW, it looks like if I do:
  $ rpm30/bin/rpm --dbpath /var/tmp/db --initdb
  $ rpm30/bin/rpm -Uvh [rpm v3 package]
  $ rpm30/bin/rpm -Uvh [rpm v3 package]
  ...
  $ rpm40/bin/rpm --dbpath /var/tmp/db --define "_dbapi 1" --rebuilddb
  $ rpm40/bin/rpm -Uvh [rpm v4 package]

then /var/tmp/db/Triggername is created and the error I saw before is
gone. So, I need to install at least one v4 package after the
--rebuilddb and all appears to work ok.

-- 
albert chin (china@thewrittenword.com)