Public key not installed error when installing from Dag RPM Repository

Posted February 26th, 2008 in Linux/Unix/BSD (Updated June 29th, 2009)

The Dag RPM Repository contains a collection of RPM packages for Red Hat Enterprise Linux, CentOS, Fedora and others which are not included in the base installation/libraries for those Linux distributions. If you get an error message similar to the one shown below when attempting to install an RPM package from the Dag RPM Repository, then you need to install the Dag GPG keys:

warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 6b8d79e6
Public key for jigdo-0.7.3-1.el4.rf.i386.rpm is not installed

Update June 29th 2009: I received an email today from someone having issues following the instructions below because the URL in the example is no longer valid. I've updated the URL and made it a little clearer it's an example.

One thing I've noticed from re-reading this post and the Dag RPM Repoistory page, is that the instructions here are for adding the Dag RPM Repository and not just the GPG key. I'm not sure if something's changed since I wrote this post originally but in any case following the instructions here will both add the repository and add the GPG keys, so if you are experiencing the above error it should fix it.

Update ends.

Installation of the GPG keys is simple. Go to the Dag RPM Repository FAQ page and look at the section titled "How to configure to use RPMforge". This contains a list of the GPG keys by Linux distribution, version and platform, and the commands you need to run to install them.

To install, running the command

rpm -Uhv [appropriate file goes here]

For example, if you had a CentOS 5 x86_64 or Red Hat Enterprise Linux 5 x86_64 install that you wanted to install the GPG keys to, you would use the Red Hat Enterprise Linux 5 / x86_64 GPG key like so:

rpm -Uhv http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS//rpmforge-release-0.3.6-1.el5.rf.x86_64.rpm

And that's all there is to it. You will now be able to install from the Dag RPM Repository, and will no longer receive the error message at the top of this post.