[Yum] Yum and RH AS 2.1

Chris Chabot chabotc at 4-ice.com
Thu Oct 30 18:29:34 UTC 2003


Try installing the rpm ? Looks like that creates the missing db's

----- Original Message ----- 
From: "Miguel Armas" <kuko at maarmas.com>
To: "Yellowdog Updater, Modified" <yum at lists.dulug.duke.edu>
Sent: Thursday, October 30, 2003 19:11
Subject: Re: [Yum] Yum and RH AS 2.1


> On Thursday 30 October 2003 16:41, Chris Chabot wrote:
> > Did you do a
> >
> >     # rpm --root=/home/kk --initdb
> >
> > before all of this?
> >
> > Sounds like you do have a Packages database (created since u installed
> > packages), but never did a --initdb (which creates the Packages db, plus
> > all those others)
>
> Yes, I did. But it only created the Packages database (not the others):
> [root at gate root]# rm -rf /home/kk/*
> [root at gate root]# ls -l /home/kk/
> total 0
> [root at gate root]# rpm --root=/home/kk/ --initdb
> [root at gate root]# ls -l /home/kk/var/lib/rpm/
> total 280
> -rw-r--r--    1 root     root         8192 Oct 30 17:06 __db.001
> -rw-r--r--    1 root     root      1310720 Oct 30 17:06 __db.002
> -rw-r--r--    1 root     root       360448 Oct 30 17:06 __db.003
> -rw-r--r--    1 root     root        12288 Oct 30 17:06 Packages
>
> Then I install something:
> [root at gate root]# yum --installroot=/home/kk install setup
> Calculating available disk space - this could take a bit
> error: cannot open Basenames index using db3 - No such file or directory
(2)
> setup 100 % done
> error: cannot open Group index using db3 - No such file or directory (2)
> error: cannot open Requirename index using db3 - No such file or directory
(2)
> error: cannot open Providename index using db3 - No such file or directory
(2)
> error: cannot open Conflictname index using db3 - No such file or
directory
> (2)
> error: cannot open Dirnames index using db3 - No such file or directory
(2)
> error: cannot open Requireversion index using db3 - No such file or
directory
> (2)
> error: cannot open Provideversion index using db3 - No such file or
directory
> (2)
> error: cannot open Installtid index using db3 - No such file or directory
(2)
> error: cannot open Sigmd5 index using db3 - No such file or directory (2)
> error: cannot open Sha1header index using db3 - No such file or directory
(2)
> error: cannot open Filemd5s index using db3 - No such file or directory
(2)
> error: cannot open Triggername index using db3 - No such file or directory
(2)
> Installed:  setup.noarch
> Transaction(s) Complete
>
> And I get some more rpm databases:
> [root at gate root]# ls /home/kk/var/lib/rpm/
> Conflictname  __db.002  Name      Providename
> __db.001      __db.003  Packages  Pubkeys
>
> If I install another package:
> [root at gate root]# yum --installroot=/home/kk install filesystem
> Calculating available disk space - this could take a bit
> error: cannot open Basenames index using db3 - No such file or directory
(2)
> filesystem 100 % done
> error: cannot open Group index using db3 - No such file or directory (2)
> error: cannot open Requirename index using db3 - No such file or directory
(2)
> error: cannot open Providename index using db3 - No such file or directory
(2)
> error: cannot open Dirnames index using db3 - No such file or directory
(2)
> error: cannot open Requireversion index using db3 - No such file or
directory
> (2)
> error: cannot open Provideversion index using db3 - No such file or
directory
> (2)
> error: cannot open Installtid index using db3 - No such file or directory
(2)
> error: cannot open Sigmd5 index using db3 - No such file or directory (2)
> error: cannot open Sha1header index using db3 - No such file or directory
(2)
> error: cannot open Filemd5s index using db3 - No such file or directory
(2)
> error: cannot open Triggername index using db3 - No such file or directory
(2)
> Installed:  filesystem.noarch
> Transaction(s) Complete
> [root at gate root]# ls /home/kk/var/lib/rpm/
> Conflictname  Name  Packages  Providename  Pubkeys
>
> Could it be that it's just a warning because that database didn't exist,
but
> the databases are created automagically by installing packages that uses
> them? So if I keep installing packages it should work?...
> Hmm, I'll try...
>
> How can I FORCE the creation of all the rpm databases?
>
> Salu2!
> -- 
> --------------------------------------
> Miguel Armas <kuko at maarmas.com>
> Consultor de Sistemas y Comunicaciones
> Ing. Tec. de Telecomunicaciones
> --------------------------------------
>
> _______________________________________________
> Yum mailing list
> Yum at lists.dulug.duke.edu
> https://lists.dulug.duke.edu/mailman/listinfo/yum
>




More information about the Yum mailing list