Up2date tends to hang on me, particularly using a "demo" account, and has to be killed. Now it keeps telling me I need a package but then fails the dependence check telling me the package is already installed.

Anybody know how to fix this short of waiting for a new version of the package in question to appear?

Try rebuilding the rpm database:
rpm --rebuilddb

Give it some time to terminate automatically. If it doesn't, run:

killall -KILL rpm
rm -f /var/lib/rpm/__*
rpm --rebuilddb
up2date -p


Be patient. Don't interrupt RPM, especially not the 4.1 and 4.2 versions. A final fix for this is in the queue hopefully.

or re-register up2date --register but first delete old comp from web

another option may be to use apt. You can get it from www.sourceforge.net. After installing, use "apt-get update" to update your database, then installing other apps will be much easier, because it will let you know when an app is dependent upon other apps, as well as give you the option to install them also.

Thanks for all of the suggestions.

It's not a registration problem - I have updated a few other packages on this machine since. I had also rebooted and had given it a couple of days to clear up think that RH runs a cron job every day that rebuilds the rpm database but still had problems.

Just was getting ready to try misc's suggestion and noticed the machine was sluggish (no rpm running tho). The alert notification area also had an icon I have never seen before - looked sort of like the two arrows but with a red bar across them. Must have been some comm program since trying to connect. When I rebooted, damned if things didn't fix themselves.

Maybe I'll take a chance and re-register this machine on my subscription account instead of a demo account. Had two machines on another demo account and one $60 fee got both a basic subscription so maybe the third will be so lucky.

I upgraded from Red Hat 8 to Red Hat 9. After the update my RPM database was corrupt. I update all my RPM packages to 4.2.1. The database was repaired using rpm -vv --rebuilddb. But, why I run db_verify Packages, I get:
[root@localhost rpm]# db_verify Packages
db_verify: region error detected; run recovery.
db_verify: Old or incorrect DB version; extraneous errors may result
db_verify: DB->verify: Packages: DB_VERIFY_BAD: Database verification failed
[root@localhost rpm]#
Any ideas how to fix this?
Thanks

Why? What symptoms?
Don't run that.

So, does that mean db_verify is BAD, and untrustworthy?

No, I didn't write that. I wrote "Don't run that" because you posted about Red Hat Linux 9.

Original poster in this thread did not mention his version of RHL. Third posting from above contains the solution to the orginal problem with both RHL 8.0 and 9.