running yum with --nosignature
Edward M
edwardm1 at live.com
Sun Jun 3 06:36:17 UTC 2012
On 06/02/2012 11:15 PM, JD wrote:
> On 06/02/2012 11:05 PM, Ed Greshko wrote:
>> On 06/03/2012 01:51 PM, JD wrote:
>>> D: Expected size: 9392994 =
>>> lead(96)+sigs(348)+pad(4)+data(9392546)
>>> D: Actual size: 9392994
>>> warning: xfdr-2.0.1.src.rpm: Header V3 DSA/SHA1 Signature, key ID
>>> 2e1efa87: NOKEY
>>> xfdr-2.0.1.x86_64
>>> D: closed db index /var/lib/rpm/Name
>>> D: closed db index /var/lib/rpm/Packages
>>> D: closed db environment /var/lib/rpm
>> And in the "failing" environment?
>>
>>
>>
> $ rpm -qpvv xfdr-2.0.1.src.rpm
> D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/*.key
> D: couldn't find any keys in /var/lib/rpm/pubkeys/*.key
> D: loading keyring from rpmdb
> D: opening db environment /var/lib/rpm cdb:0x201
> D: opening db environment /var/lib/rpm cdb:private:0x201
> D: opening db index /var/lib/rpm/Packages 0x400 mode=0x0
> D: locked db index /var/lib/rpm/Packages
> D: opening db index /var/lib/rpm/Name 0x400 mode=0x0
> D: read h# 453 Header sanity check: OK
> D: added key gpg-pubkey-adf25d9c-4de0797b to keyring
> D: read h# 943 Header sanity check: OK
> D: added key gpg-pubkey-a82ba4b7-4e2df47d to keyring
> D: read h# 1726 Header sanity check: OK
> D: added key gpg-pubkey-66534c2b-4eff56c5 to keyring
> D: read h# 2162 Header sanity check: OK
> D: added key gpg-pubkey-f6777c67-45e5b1b9 to keyring
> D: read h# 2828 Header sanity check: OK
> D: added key gpg-pubkey-952f3af8-4de079ff to keyring
> D: read h# 4721 Header sanity check: OK
> D: added key gpg-pubkey-7fac5991-4615767f to keyring
> D: Using legacy gpg-pubkey(s) from rpmdb
> error:xfdr-2.0.1.src.rpm: rpmReadSignature failed: sigh load: BAD
> error:xfdr-2.0.1.src.rpm: not an rpm package (or package manifest)
> D: closed db index /var/lib/rpm/Name
> D: closed db index /var/lib/rpm/Packages
> D: closed db environment /var/lib/rpm
>
does rpm still has the option to resign, like rpm --resign, if it
does that may help?
However i still a think along the way a security update to rpm is
blocking for a reason or
the src package in question has problems and a fix is needed to the
package.
More information about the users
mailing list