After using --repackage, I get DSA signature: BAD

[Panu Matilainen]

On 08/21/2014 12:07 AM, Kai Lanz wrote:
> I used --repackage to rebuild an  rpm; this worked fine:
>
> # rpm -ev --repackage kernel-smp-2.6.9-103.EL
> Wrote: /var/spool/repackage/kernel-smp-2.6.9-103.EL.x86_64.rpm
>
> Unfortunately, the resulting rpm can't be used. If I copy it to another
> machine and try to install it, I get:
>
> # rpm -ivh kernel-smp-2.6.9-103.EL.x86_64.rpm
> error: kernel-smp-2.6.9-103.EL.x86_64.rpm: V3 DSA signature: BAD, key ID db42a60e
>
> On the machine where I created the rpm, I see:
>
> $ rpm --checksig kernel-smp-2.6.9-103.EL.x86_64.rpm
> kernel-smp-2.6.9-103.EL.x86_64.rpm: (sha1) dsa sha1 MD5 GPG NOT OK
>
> and
>
> $ rpm -qip kernel-smp-2.6.9-103.EL.x86_64.rpm
> error: kernel-smp-2.6.9-103.EL.x86_64.rpm: V3 DSA signature: BAD, key ID db42a60e
>
> How do I fix this? Will signing the rpm do the trick? (Creating a GPG key
> and then resigning the rpm...)

The fix is to use the original package, not a repackaged one.
Repackaged rpms are not for distribution, they're only intended to be 
used on the same host where they were repackaged, and even there only 
with --rollback, not manual -U/-i.

	- Panu -