I already submitted a bug report on this topic, for RPMs available for
download under Red Hat 6.0 errata; however, I forgot to mention that I
believe the netscape-communicator RPM also gives this error.

The simplest way to be certain, if you don't mind me making a suggestion,
would be to check all of the packages in the download directory.  This
would be useful to everyone.

This kind of monitoring job could be run at least daily against all
packages placed in the download directories, as well as before the RPMs are
copied to these directories.  If the script finds packages that aren't OK,
then the script or job could send an email message to the people
responsible for placing the RPMs in these directories.

I don't know your setup; therefore, this script idea is just a suggestion
about setting up some kind of control watcher job.  This morning I reported
a total of 22 RPMs in the 5.2 and 6.0 errata download directories which
have this error, and some RPMs take considerable time to download.

If the same RPMs are placed on update CDROMs, then many more people would
also get these problem packages.

Or, is there something wrong with my configuration?  I have both rpm 2.5.3
and 3.0.2 installed; although, 3.0.2 is the active version.  Nonetheless,
there are two rpm directories under /usr/lib, namely /usr/lib/rpm and
/usr/lib/rpm2.5.3.  I assume the one named simply rpm is for 3.0.2, however
there's nothing clearly indicating this.  /usr/lib/rpmrc is linked to
/usr/lib/rpm, though.

This should not cause such problems, however I'll provide this additional
information in case this could be a problem.