Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 2154270

Summary:	dnf now fails gpg check for almost all non-fedora RMPs
Product:	[Fedora] Fedora	Reporter:	David Hill <dhill>
Component:	rpm	Assignee:	rpm-software-management
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	daniel.mach, igor.raits, jmracek, jrohel, mblaha, mdomonko, packaging-team-maint, pkratoch, pmatilai, rpm-software-management, vmukhame
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-12-16 13:24:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Hill 2022-12-16 13:08:48 UTC

Description of problem:
dnf now fails gpg check for almost all  non-fedora RMPs:
Problem opening package google-chrome-stable-108.0.5359.124-1.x86_64.rpm
Problem opening package google-chrome-unstable-110.0.5464.2-1.x86_64.rpm
Problem opening package skypeforlinux_8.92.0.204-1.x86_64.rpm
Problem opening package teamviewer_15.37.3.x86_64.rpm
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'yum clean packages'.
Error: GPG check FAILED


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Panu Matilainen 2022-12-16 13:24:14 UTC


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