RPM gives warnings for everything but doesn't accomplish anything

I'm running SuSe 9.3 on AMD64 here and I'm finding that RPM seems to insist
on being useless. Most recently, I attempted to install the Wine source
package (wine-20050830-SuSELinux93.src.rpm from www.winehq.org) and I keep
getting the message:

warning: wine-20050830-SuSELinux93.src.rpm: V3 DSA signature: NOKEY, key ID
0175623e

When I do an rpm -q on this package, it tells me that it has not been
installed. I get the same message for many other RPMs.

I read a response here about the database getting corrupted, so I ran rpm
--rebuilddb as root and it did not help. What is this key nonsense and is
there any way to force RPM to do its job in spite of this? I've gotten the
packages from trusted sources, so this "security" stuff is really just
getting in the way.

--
[Reverse the parts of the e-mail address to reply.]

Marty adjusted his/her tinfoil beanie to post:

> I'm running SuSe 9.3 on AMD64 here and I'm finding that RPM seems to
> insist
> on being useless. Most recently, I attempted to install the Wine
> source package (wine-20050830-SuSELinux93.src.rpm from www.winehq.org)
> and I keep getting the message:
>
> warning: wine-20050830-SuSELinux93.src.rpm: V3 DSA signature: NOKEY,
> key ID 0175623e
>
> When I do an rpm -q on this package, it tells me that it has not been
> installed. I get the same message for many other RPMs.
>
> I read a response here about the database getting corrupted, so I ran
> rpm
> --rebuilddb as root and it did not help. What is this key nonsense
> and is
> there any way to force RPM to do its job in spite of this? I've
> gotten the packages from trusted sources, so this "security" stuff is
> really just getting in the way.
>


rpm -Uvh <name-of-rpm>.rpm --nosignature

If that does not work then add a --force

That is if you trust the rpm, the security is there for a reason.

man rpm


HTH
--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

On Sat, 24 Sep 2005 21:22:03 +0000, Marty wrote:

> I'm running SuSe 9.3 on AMD64 here and I'm finding that RPM seems to insist
> on being useless. Most recently, I attempted to install the Wine source
> package (wine-20050830-SuSELinux93.src.rpm from www.winehq.org) and I keep
> getting the message:
>
> warning: wine-20050830-SuSELinux93.src.rpm: V3 DSA signature: NOKEY, key ID
> 0175623e
>
You are getting this warning because the rpm is signed with a key that is
not located in the pub keyring that rpm uses to verify signatures. This
means that you'll get a warning if you attempt to install any rpm that is
signed with this gpg key, but it will not prevent you from installing a
package. I think that YOU, on the other hand, will balk at installing
packages that haven't been signed with an official SuSE build/security
keys.

> When I do an rpm -q on this package, it tells me that it has not been
> installed. I get the same message for many other RPMs.

I don't believe that rpm creates an entry in the database when
installing *src.rpm packages, it just installs the source archive, patch
files, spec file, etc. under the relevant directories under
/usr/src/packages/.

>
> I read a response here about the database getting corrupted, so I ran rpm
> --rebuilddb as root and it did not help. What is this key nonsense and is
> there any way to force RPM to do its job in spite of this? I've gotten the
> packages from trusted sources, so this "security" stuff is really just
> getting in the way.

Even "trusted sources" can have their security comprimised.

--
sktsee

baskitcaise wrote:

> Marty adjusted his/her tinfoil beanie to post:
>
>> I'm running SuSe 9.3 on AMD64 here and I'm finding that RPM seems to
>> insist
>> on being useless. Most recently, I attempted to install the Wine
>> source package (wine-20050830-SuSELinux93.src.rpm from www.winehq.org)
>> and I keep getting the message:
>>
>> warning: wine-20050830-SuSELinux93.src.rpm: V3 DSA signature: NOKEY,
>> key ID 0175623e
>>
>> When I do an rpm -q on this package, it tells me that it has not been
>> installed. I get the same message for many other RPMs.
>>
>> I read a response here about the database getting corrupted, so I ran
>> rpm
>> --rebuilddb as root and it did not help. What is this key nonsense
>> and is
>> there any way to force RPM to do its job in spite of this? I've
>> gotten the packages from trusted sources, so this "security" stuff is
>> really just getting in the way.
>
> rpm -Uvh <name-of-rpm>.rpm --nosignature
>
> If that does not work then add a --force
>
> That is if you trust the rpm, the security is there for a reason.
>
> man rpm

Thanks I tried a few different parameter combinations from the man page but
didn't quite hit the right one. That one did it. I'll keep it in my bag
of tricks for the future.

--
[Reverse the parts of the e-mail address to reply.]

Marty adjusted his/her tinfoil beanie to post:


>
> Thanks I tried a few different parameter combinations from the man
> page but
> didn't quite hit the right one. That one did it. I'll keep it in my
> bag of tricks for the future.
>

Glad to help Marty,

This though was just a stop-gap till I found the right article for you,
have posted it in your other thread.

HTH
--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp