On Saturday 12 February 2011 19:48:41 Jeff Johnson wrote:
> Yes the --import path likely leads to "corruption", particularly
> if --import is attempted automagically in a script. There's
> some deeply obscure code paths handling pubkeys, an rpmdb is actually
> opened twice to use pubkeys).
>
> You might try using %pubkey instead of doing --import in a script.
>
> The %pubkey is a file attribute like %attr et al.
>
> It can take a relative path (like %doc relative to the top of the build
> directory) or it can take an absolute path (like other attributes, within
> %buildroot, the absolute path will be installed on the file systes _AND_
> the pubkey content will be pulled into the header for indexing in an
> rpmdb).
Thanks for the hint, but does this work with 5.2.1 as well?
I've removed the current key in database:
rpm -e gpg-pubkey-87468781-4bb78410
Then added %pubkey in openmamba-release:
%pubkey %{_sysconfdir}/pki/rpm-gpg/RPM-GPG-KEY-Mambasoft
But after upgrading the package openmamba-release, the key does not appear:
$ rpm -q gpg-pubkey-87468781-4bb78410
package gpg-pubkey-87468781-4bb78410 is not installed
Probabily I just didn't understand how this should work or there is a
different way to retrieved the installd key...
Silvan
--
mambaSoft di Calarco Silvan
Web: http://www.mambasoft.it
mambaSoft Store @ http://www.mambastore.it
openmamba GNU/Linux development @ http://www.openmamba.org
______________________________________________________________________
RPM Package Manager http://rpm5.org
Developer Communication List [email protected]
