Hi..
Or maybe the package is corrupt.
You can test with
rpm -i --test package.rpm
If you receive the same message about the key, mean that's is corrupt.
nosp wrote:
On Tue, 2003-12-02 at 21:49, Kevin Hanser wrote:
I've noticed that some other people mentioned that they couldn't install the new kernel thru up2date... I'm also experiencing this problem. If I try to use up2date, it tells me that it has an invalid GPG signature, and the file was corrupted. I've also tried downloading the rpm manually, and using the rpm commandline to install it. When I try that, it complains: error: kernel-2.4.22-1.2129.nptl.i686.rpm: V3 DSA signature: BAD, key ID 4f2a6fd2 error: kernel-2.4.22-1.2129.nptl.i686.rpm cannot be installed
The "BAD, key ID xxx" is a hint that the problem is that RPM doesn't recognize the GPG key that signed the rpm as one it should trust, not that the file is corrupted. It has a GPG key, but RPM doesn't like it.
Do this:
1) Verify you do not have this GPG key; here's what I see when I DO have the key:
# rpm -q gpg-pubkey | grep 4f2 gpg-pubkey-4f2a6fd2-3f9d9d3b # rpm -qi gpg-pubkey-4f2a6fd2-3f9d9d3b Name : gpg-pubkey Relocations: (not relocateable) Version : 4f2a6fd2 Vendor: (none) Release : 3f9d9d3b Build Date: Thu 06 Nov 2003 06:08:47 PM GMT Install Date: Thu 06 Nov 2003 06:08:47 PM GMT Build Host: localhost Group : Public Keys Source RPM: (none) Size : 0 License: pubkey Signature : (none) Summary : gpg(Fedora Project <fedora@xxxxxxxxxx>) Description : -----BEGIN PGP PUBLIC KEY BLOCK----- Version: rpm-4.2.1 (beecrypt-3.0.0)
mQGiBD+dnTsRBACwnlz4AhctOLlVBAsq+RaU82nb5P3bD1YJJpsAce1Ckd2sBUOJD11NUCqH 8c7EctOquOZ5zTcWxHiWWbLyKQwUw2SUvnWa5SSbi8kI8q9MTPsPvhwtgMrQMLenMO+nsrxr SaG6XcD+ssfJNxC7NQVCQAj3pvvg9rKi3ygsM7CXHwCghgsqX6TOr55HE90DbEsoq3b/jjsD /i8aIZ6urUgrpAkQslcakXdJLKgSdwjRUgVZgvYZb7kAx1iPq0t/AhB3NJw3zW4AAKJohGg3 xj5K4V8PJEZrSIpoRYlF43Kqlfu2p5ghWT89SP4YAlWPeTqf0+dTYUYz3b144k2ZFOdRuXIR xunoYNAUr9oMrxBXbJ/eY+0UQX3pBACYzKizyY4JJgd0zFJmNkcdK9nzcm+btYFnYQo33w5G SE686UNr+9yiXt9tmPRvNEbj3u+xoAX8B/5k3aZ5NbUhV64/VcKlUdRIxNlFCG7I9KgxeHWA Ywi7yqOGXM3T/v6o7GLdQEB0ChFqS7kUlqmwLV+C3QhlrFe/Cuk26i+Q6rQiRmVkb3JhIFBy b2plY3QgPGZlZG9yYUByZWRoYXQuY29tPohbBBMRAgAbBQI/nZ07BgsJCAcDAgMVAgMDFgIB Ah4BAheAAAoJELRCadBPKm/S2PAAnRTlhorITphab+oxAHtbxZF9BVyDAJ9WOVaZUG53IWWI AXOGv3j/cmr3lohGBBMRAgAGBQI/nZ22AAoJECGRgM3bQqYOR5QAoIp1G+omVktq/snxpmz5 UeHjlSYjAKCRr/ea/L7S7ZTxB18cf1TYfad1x4hGBBARAgAGBQI/ntjgAAoJECnVuiSN9W0F USUAoJnrone4J0o1HMkRz+6g9KVuO2FyAJ0XyebOzVmI9U5OyOfnNmYV0wnQcrkBDQQ/nZ08 EAQAugOfLWJbKwMA9vg2mJU594TZU0HRJkx/fqYhx0YxWWRpzplrEyvcDXuYcWi1Hwh0tD86 T4fR5GV6joWiWClzD+Hwhhb6gcSdeSGlGLlZAvWYtFSHWiv+3LaI9w8Vtczl99Bh2WiMDNDD Gw0RQg6ZaftldLSe4j1pffpFGQ8SuisAAwUEAKVxqLT7fC5xQ6oclcZ+PhoDlePQ1BiTS7tu GM07bFF4nNvY91LL7S31pooz3XbGSWP8jxzSv1Fw35YhSmWGOBOEXluqMbVQGJJ5m8fqJOjC 0imbfeWgr/T7zLrJeiljDxvX+6TyawyWQngF6v1Hq6FRV0O0bOp9Npt5zqCbDGs/iEYEGBEC AAYFAj+dnTwACgkQtEJp0E8qb9L//gCcDVYnDegNCOxDn1sedDwxw+0h8OcAn1CZHof15Qqx nTwEnvwF2QeOI5dn =mJAx -----END PGP PUBLIC KEY BLOCK-----
2) Import the Fedora key to your rpm keyring (it's strange that you don't have this already -- you should also check that you have the "fedora-release-1-3" rpm installed):
# rpm --import /usr/share/doc/fedora-release-1/RPM-GPG-KEY-fedora
3) Try installing the RPM again.
You could tell RPM to not perform its digital signature checks (check the rpm man page), but that's just avoiding the problem.
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
