Bug 32405 - drakrpm cannot use GPG key
Summary: drakrpm cannot use GPG key
Status: RESOLVED DUPLICATE of bug 32177
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-18 10:34 CEST by Eric Petit
Modified: 2023-10-18 11:55 CEST (History)
0 users

See Also:
Source RPM: google-chrome-stable
CVE:
Status comment:

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

Description Eric Petit 2023-10-18 10:34:46 CEST 
Hi
Installing google repo from https://www.google.com/linuxrepositories/
Use Drakrpm or urpmi google-chrome-stable display GPG error "not signed".

But :
cd /tmp
sudo urpmi ./google-chrome-beta-119.0.6045.21-1.x86_64.rpm
sudo urpmi ./google-chrome-stable-118.0.5993.88-1.x86_64.rpm 


installation de google-chrome-stable-118.0.5993.88-1.x86_64.rpm depuis .
Préparation...                   ############################################
      1/1: google-chrome-stable  ############################################
Comment 1 Eric Petit 2023-10-18 10:36:28 CEST 
rpm -qi gpg-pubkey-d38b4796-*
Name        : gpg-pubkey
Version     : d38b4796
Release     : 570c8cd3
Architecture: (none)
Install Date: mer. 18 oct. 2023 10:20:21
Group       : Public Keys
Size        : 0
License     : pubkey
Signature   : (none)
Source RPM  : (none)
Build Date  : mar. 12 avril 2016 07:51:15
Build Host  : localhost
Packager    : Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>
Summary     : Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com> public key
Description :
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: rpm-4.16.1.3 (NSS-3)

mQINBFcMjN...........
Comment 2 sturmvogel 2023-10-18 11:55:58 CEST 
Duplicate

*** This bug has been marked as a duplicate of bug 32177 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.