For a quick solution you can try to disable the signature check:

# yum --help | grep gpg
  --nogpgcheck          disable gpg signature checking

The correct way to address the problem is adding the new gpg key
(if it's actually required). You could try to get some help from
the fedora community (check the wiki, irc, mailing lists, etc...).

-- 
Federico

----- Original Message -----
> From: "ShaoHe Feng" <shao...@linux.vnet.ibm.com>
> To: "Federico Simoncelli" <fsimo...@redhat.com>
> Cc: "Shu Ming" <shum...@linux.vnet.ibm.com>, "VDSM Project Development" 
> <vdsm-devel@lists.fedorahosted.org>
> Sent: Monday, April 23, 2012 4:35:09 PM
> Subject: Re: [vdsm] Installation dependency for VDSM-4.9.6-0.109 package on 
> FC16
> 
> error, when I apply these updates on my laptop.
> 
> here is the err:
> 
> Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64
> 
> The GPG keys listed for the "Fedora 17 - x86_64" repository are
> already
> installed but they are not correct for this package.
> Check that the correct key URLs are configured for this repository.
> 
> 
> the libvirt is still 0.9.6
> virsh # version --daemon
> Compiled against library: libvir 0.9.6
> Using library: libvir 0.9.6
> Using API: QEMU 0.9.6
> Running hypervisor: QEMU 0.15.1
> Running against daemon: 0.9.6
> 
> the sanlock version is still 1.9
> $ sanlock version
> sanlock 1.9 (built Feb 20 2012 19:52:57)
> 
> 
> On 04/23/2012 08:04 PM, Federico Simoncelli wrote:
> > Hi Shu,
> >   you can get sanlock and libvirt from fedora 17:
> >
> > # yum --releasever=17 update libvirt
> > # yum --releasever=17 install sanlock
> >
> > And lvm2 from my repository:
> >
> > http://fsimonce.fedorapeople.org/lvm2/fedora-16/x86_64/
> >
_______________________________________________
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

Reply via email to