Bug 18292 - Always no key
Summary: Always no key
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: Backports (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-29 03:01 CEST by Jan Pihlgren
Modified: 2016-04-29 07:42 CEST (History)
0 users

See Also:
Source RPM: google-chrome-stable-50.0.2661.94-1.x86_64.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.