[CentOS] public Key Problems after Centos 4 -> 5 update.

Robert Slade centos at likley.co.uk
Sat Oct 27 06:19:32 UTC 2007

On Fri, 2007-10-26 at 03:11 -0500, Johnny Hughes wrote:
> Robert Slade wrote:
> > On Thu, 2007-10-25 at 19:06 +0100, Robert Slade wrote:
> >> Hi,
> >>
> >> I have just updated my system from Centos 4 to 5 using the DVD. When I
> >> try to update using Yum, it gets so far then I get:
> >>
> >> "Public key for tomcat5-jsp-2.0-api-5.5.23-0jpp.3.0.2.el5.i386.rpm is
> >> not installed"
> >>
> >> How do I get the key and install it?
> >>
> > To reply to my own post, the answer was obvious when I thought about it.
> > It was looking for the GPG key downloaded and imported it and Bob's your
> > uncle. Slightly puzzled that yum didn't automatically do it as per the
> > documents though.
> Maybe the CentOS-Base.repo file in your /etc/yum.repos.d/ is the one for
> CentOS-4 and not CentOS-5.
> The only difference between the CentOS-4 and CentOS-5 repo files is the
> key ... we have different keys for CentOS-4 and CentOS-5.
> By default, there are many CONFIG files that are not replaced if they
> have been updated when you do normal upgrades.  In most cases, you will
> instead get a file that is a replacement called <config-file-name>.rpmnew
> On an upgrade from CentOS-4 to CentOS-5, you will have MANY files named
> .rpmnew that you will need to look at and you will need to modify the
> appropriate config files that are currently in place (and designed for
> CentOS-4) to work with CentOS-5.

Thanks for the pointer, I did have a CentOS-Base.repo.rmpnew file. 

I am still unsure what is happening with yum. I am getting this now:

Loading "protectbase" plugin
Loading "installonlyn" plugin
/usr/lib/python2.4/site-packages/yum/plugins.py:380: DeprecationWarning:
registerOpt() will go away in a future version of Yum.
Please manipulate config.YumConf and config.RepoConf directly.

Unfortunately, the documenation on the web site for yum does not cover


More information about the CentOS mailing list