Bug 18292

Summary:	Always no key
Product:	Mageia	Reporter:	Jan Pihlgren <jan>
Component:	Backports	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	google-chrome-stable-50.0.2661.94-1.x86_64.rpm	CVE:
Status comment:

Description Jan Pihlgren 2016-04-29 03:01:32 CEST

Description of problem:
Always when I get an update about google-chrome-stable I get an error message
that there is no key for the media and asked if I whish to continue.

This is the message translated from Swedish:
google-chrome-stable-50.0.2661.94-1.x86_64.rpm: Mediawithout key(OK(DSA/SHA1, wensday 27 april 2016 23:26:00, Key ID a040830f7fac5991))
Do you want to continue?

The following package has wrong signature


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Comment 1 James Kerr 2016-04-29 07:42:58 CEST

See this forum post, especially the final sections which explain how to install the google key and associate it with the google-chrome repo:

https://forums.mageia.org/en/viewtopic.php?f=36&t=2053

Marking as invalid, since google-chrome is not a Mageia package.

Status: NEW => RESOLVED
Resolution: (none) => INVALID