ellanios82 writes:

On 28/07/17 01:08, John Andersen wrote:

...

wgethttps://dl.google.com/linux/linux_signing_key.pub sudo rpm --import linux_signing_key.pub You can verify the key installation by running:

rpm -qi gpg-pubkey-7fac5991-*

- thanks . . . done that . . . but still get error :

File 'repomd.xml' from repository 'google-chrome' is signed with an unknown key '1397BC53640DB551'

I am getting this error too. I tried the rpm commands and I tried: gpg --recv-keys 1397BC53640DB551 Which says: gpg: requesting key 640DB551 from hkp server keys.gnupg.net gpg: key D38B4796: "Google Inc. (Linux Packages Signing Authority) " not changed gpg: Total number processed: 1 gpg: unchanged: 1 But then sudo zypper refresh says: File 'repomd.xml' from repository 'google' is signed with an unknown key '1397BC53640DB551'. Continue? [yes/no] (no): gpg -k gpg -k|grep -i google uid [ unknown] Google Inc. (Linux Packages Signing Authority) Shows it is unknown. So I changed the trust using gpg --key-edit gpg -k|grep -i google uid [ultimate] Google Inc. (Linux Packages Signing Authority) But I still get the error. This all seems wrong anyway, I need to verify the key somehow, not blindly trust it. -- ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Hi, This is a problem in libzypp. It will be addressed by an update of libzypp. Ciao, Marcus On Thu, Aug 10, 2017 at 03:58:17PM +0200, Carlos E. R. wrote:

On 2017-08-09 22:47, Richmond wrote:

...

I am getting this error too. I tried the rpm commands and I tried:

gpg --recv-keys 1397BC53640DB551

Which says:

gpg: requesting key 640DB551 from hkp server keys.gnupg.net gpg: key D38B4796: "Google Inc. (Linux Packages Signing Authority) " not changed gpg: Total number processed: 1 gpg: unchanged: 1

AFAIK rpm/zypper do not import the keys that way. It is also not stored in the same place for command gpg than for rpm.

-- Cheers / Saludos,

Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

-- Marcus Meissner,SUSE LINUX GmbH; Maxfeldstrasse 5; D-90409 Nuernberg; Zi. 3.1-33,+49-911-740 53-432,,serv=loki,mail=wotan,type=real -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 08/10/2017 10:00 PM, Marcus Meissner wrote:

Hi,

This is a problem in libzypp. It will be addressed by an update of libzypp.

Ciao, Marcus

Ok, good to know. I was wondering what progress had been made on the error. -- George Box: 42.2 | KDE Plasma 5.8 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.2 | KDE Plasma 5.8 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: 42.2 | KDE Plasma 5.8 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 20/08/17 17:02, ellanios82 wrote:
> On 10/08/17 17:00, Marcus Meissner wrote:
>> Hi,
>>
>> This is a problem in libzypp. It will be addressed by an update of
>> libzypp.
>>
>> Ciao, Marcus
>> On Thu, Aug 10, 2017 at 03:58:17PM +0200, Carlos E. R. wrote:
>>> On 2017-08-09 22:47, Richmond wrote:
>>>
>>>> I am getting this error too. I tried the rpm commands and I tried:
>>>>
>>>> gpg --recv-keys 1397BC53640DB551
>>>>
>>>> Which says:
>>>>
>>>> gpg: requesting key 640DB551 from hkp server keys.gnupg.net
>>>> gpg: key D38B4796: "Google Inc. (Linux Packages Signing Authority)
>>>> " not changed
>>>> gpg: Total number processed: 1
>>>> gpg:              unchanged: 1
>>> AFAIK rpm/zypper do not import the keys that way. It is also not stored
>>> in the same place for command gpg than for rpm.
>>>
>>> -- 
>>> Cheers / Saludos,
>  - thank you kindly Marcus : 

  - as yet , this  google-chrome problem with gpg signing key is still 
to be fixed

  regards
....



-- 
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse+owner@opensuse.org