Bug 1381004

Summary:	gpg sign public virtio-win rpms
Product:	[Community] Virtualization Tools	Reporter:	Frank Büttner <bugzilla>
Component:	virtio-win	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	crobinso, ghammer, lijin, michen, phou, virt-maint, vrozenfe, wyu, xiagao, yvugenfi
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-28 23:57:55 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:

Description Frank Büttner 2016-10-02 07:11:45 UTC

Description of problem:
The last version of it seem not to be digital signet.

Version-Release number of selected component (if applicable):
virtio-win-0.1.126-2 not signet

How reproducible:
every time

Steps to Reproduce:
1. dnf update


Actual results:
DNF error:
Error: Package virtio-win-0.1.126-2.noarch.rpm is not signed

Expected results:
working update

Additional info:

Comment 1 Vadim Rozenfeld 2016-10-02 12:28:13 UTC

Hi Cole,

I'm not sure how it works. Do we usually sign virtio-win RPMs available publicly?

Thanks,
Vadim.

Comment 2 Cole Robinson 2016-10-10 13:10:10 UTC

The signing referred to by dnf is about RPM gpg signatures, which have never been set up for the public virtio-win repo/RPMs. Not sure what changed here that dnf is suddenly warning about this. You can use the --nogpgcheck option to work around it.

Comment 3 Cole Robinson 2019-03-28 23:57:55 UTC


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