Ralf S.Engelschall
2004-05-18 17:28:11 UTC
when installing a new OpenPKG instance using
openpkg-20020208-20020208.src.sh the RPM DB does not exists
# /cw/bin/rpm -qa
error: cannot open Packages index using db3 - No such file or directory (2)
The openpkg-20020208-20020208.src.sh script has a bug which makes it
"forget" initializing the RPM DB.
This is not a problem when upgrading, it appears only when installing a
new instance from scratch. The
solution below shows how to initialize the RPM DB and upgrade to itself,
which fixes the problem.
# /cw/bin/rpm --initdb
# /cw/bin/rpm -qa
(the error is gone but the database is empty)
# /cw/bin/rpm -Uvh openpkg-20020208-20020208.*-*.rpm
(ignore warnings)
Verify the solution
# /cw/bin/rpm -qa
openpkg-20020208-20020208
This was already fixed a few weeks ago. The openpkg.boot was broken.openpkg-20020208-20020208.src.sh the RPM DB does not exists
# /cw/bin/rpm -qa
error: cannot open Packages index using db3 - No such file or directory (2)
The openpkg-20020208-20020208.src.sh script has a bug which makes it
"forget" initializing the RPM DB.
This is not a problem when upgrading, it appears only when installing a
new instance from scratch. The
solution below shows how to initialize the RPM DB and upgrade to itself,
which fixes the problem.
# /cw/bin/rpm --initdb
# /cw/bin/rpm -qa
(the error is gone but the database is empty)
# /cw/bin/rpm -Uvh openpkg-20020208-20020208.*-*.rpm
(ignore warnings)
Verify the solution
# /cw/bin/rpm -qa
openpkg-20020208-20020208
Ralf S. Engelschall
***@engelschall.com
www.engelschall.com